fiware-orion

问题 In Orion 1.4.0 I used the following JSON to subscribe for all entities : { "description": "Update average rating", "subject": { "entities": [ { "idPattern": ".*", "type": "" } ], "condition": { "attrs": [] } }, "notification": { "http": { "url": "http://URL:1026/v2" } }, "expires": "2020-01-01T00:00:00.00Z", "throttling": 5 } Today I tried this JSON with an Orion 1.7.0 and this doesn't work anymore. It returns the following error: ERROR 400 {"error":"BadRequest","description":"entity type

问题 Recently I start working with NGSIV2 but cygnus start crashing. May I have something not cofigurated right? With the v1 works flawless. My startup trace with the error is in here: http://pastebin.com/nP2am8GW The error said: Error appending event to channel. Channel might be full. Consider increasing the channel capacity or make sure the sinks perform faster. time=2016-05-09T05:58:28.866CDT | lvl=WARN | trans=1462791485-602-0000000000 | srv=papel-club | subsrv=events | function=intercept |

问题 Click here for problem description This question derives from this other one. 来源： https://stackoverflow.com/questions/33732290/cosmos-does-not-respond-to-a-request-from-cygnus-located-on-a-fiware-private-ins

问题 I'm using Cygnus to send Orion Context Broker notifications to Cosmos via httpfs. Where are stored the data sent to Cosmos in the Hive history? What's the name of the table where Cygnus data are stored? 回答1: The Orion context data persisted by Cygnus in Cosmos is stored in plain text HDFS files. The content of this files, if properly structured, can be loaded into Hive tables which can be queried by using HiveQL, a SQL-like language. The way the Hive tables are created depends on the Cygnus

问题 Context Broker Orion crashes in my Cloud + CoreOS + Docker architecture, by using a centos6 based dockerfile definition and the latest rpm compilation provided. Any thoughts on crashes like the one I paste here? After 20/30 ContextUpdates it stops. Actually, cygnus and proton are subscribed. DEBUG@11:34:05 httpRequestSend.cpp[409]: Sending message 114 to HTTP server: sending message of 649 bytes to HTTP server INFO@11:34:05 MongoCommonUpdate.cpp[960]: Database Operation Successful (update: {

问题 I've installed Orion 0.24 on a server, alongside with Apache Tomcat 7, where I deployed ProtonCEP GE (4x WAR files deployed). The issue is that Orion unswers only to half of the requests it gets (independent of request) in an alternate fashion, like so: $ curl http://localhost:1026/version -H "Content-Type: application/json" <orion> <version>0.24.0</version> <uptime>0 d, 0 h, 8 m, 39 s</uptime> <git_hash>ed11a3307c7050857ef398ee3e4cd04042a0cc01</git_hash> <compile_time>Mon Sep 14 17:52:44

问题 I'm working with an Orion context broker version 1.2.0. I have subscribed in it two different cygnus (0.11 and 0.13) using NGSIv2, as follows: (curl 172.21.0.23:1026/v2/subscriptions -s -S --header 'Fiware-Service: prueba_015_adapter' --header 'Fiware-ServicePath: /Prueba/Planta_3' --header 'Content-Type: application/json' -d @- ) <<EOF { "description": "Cygnus subscription", "subject": { "entities": [ { "idPattern": ".*", "type": "density_algorithm" } ], "condition": { "attrs": [] } },

问题 When trying to persist an entity from Cygnus to Cosmos global instance it fails. Looking at the log file I see something like that: 2015 15:31:50,006 DEBUG [SinkRunner-PollingRunner-DefaultSinkProcessor] (org.apache.http.impl.conn.DefaultClientConnection.sendRequestHeader:273) - >> GET /webhdfs/v1/user/ms/def_serv/def_servpath/6_registervalues/6_registervalues.txt?op=getfilestatus&user.name=ms HTTP/1.1 12 Nov 2015 15:31:50,006 DEBUG [SinkRunner-PollingRunner-DefaultSinkProcessor] (org.apache

问题 So i have read all the documentation and followed the tutorial on MySQL persistence but i can't still presist any kind of data on MySQL database. Even though i'm puting the presistence mode = row it doesn't create any database nor table. What am i doing wrong? My Subscription: python2.7 SetSubscription.py bustest4 http://localhost:5050/notify Output: * Asking to http://localhost:1026/v1/subscribeContext * Headers: {'Fiware-Service': 'fiwaretestapi', 'content-type': 'application/json ',

问题 I have deployed an Orion instance in FILAB and I have configured the Cygnus inyector in order to store information in Cosmos. But...let us imagine a scenario in which the number of entities increases drastically. In this hypothetical scenario one instance of Orion GE wouldn't be enough so it would be necessary to deploy more instances. What would be the scale procedure? Taking into account the maximum quotas are: VM Instances: 5 VCPUs: 10 Hard Disk: 100 GB Memory: 10240 MB Public IP: 1 I