fiware-orion

问题 I'm trying to use Orion CB as Contex Provider for an IoT Agent in which I have registred a device with lazy attributes only. On the IoT Agent I need to handle updateContext requests so I did a handler for these requests like this: iotAgentLib.setDataUpdateHandler(updateContextHandler); And in the updateContextHandler function I have only one instruction: console.log(attributes); In order to see if all the values I want to update have been received correctly. Now if I do an update on one of

问题 I'm trying to use Orion CB as Contex Provider for an IoT Agent in which I have registred a device with lazy attributes only. On the IoT Agent I need to handle updateContext requests so I did a handler for these requests like this: iotAgentLib.setDataUpdateHandler(updateContextHandler); And in the updateContextHandler function I have only one instruction: console.log(attributes); In order to see if all the values I want to update have been received correctly. Now if I do an update on one of

问题 I am interested in knowing more about the context history feature of Orion, which is mentioned here: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Data.PubSub#Context_history I cannot figure: whether context history is implemented and how in the current ORION if it is implemented, I cannot figure how to tap into it, that is, I don't see it covered by APIs etc. Thanks for any help! 回答1: By design, Orion doesn't store historic data itself: its

问题 I'm using Orion to store context information, and among all the entity attributes there are two that are time specific: updated_at created_at How can I store this? Is there a timestamp or datetime attribute type in Orion? 回答1: You can use attribute type date to store dates, as described in NGSIv2 specification section "Special attribute types". For example, you could create the following entity: POST /v2/entities { "id": "myEntity", "type": "myType", "updated_at": { "value": "2017-06-17T07:21

问题 I am willing to install the latest release of Orion Context Broker (ReleaseName: 4.3.2 / Version: 0.22.0) from https://forge.fiware.org/frs/?group_id=7#title_data-orioncontextbroker on Ubuntu 15.04.. I did some research on this issue already. To be precise it became a longer description. If that's to much text just reading the bold parts will probably do . I managed the absence of a native .deb-package (see this) by using converting (alien --scripts contextBroker-0.22.0-1.x86_64.rpm ) the

问题 I am having the same problem as here and try to solve it, but I do not know how to properly format the datastore so cygnus will not throw the persistence error. My orion suscription is this one: (curl localhost:1026/v1/subscribeContext -s -S --header 'Content-Type: application/json' \ --header 'Accept: application/json' -d @- | python -mjson.tool) <<EOF { "entities": [ { "type": "Event", "isPattern": "false", "id": "es-leon-0" }, { "type": "Event", "isPattern": "false", "id": "es-leon-1" } ],

问题 I'm using Fiware-Orion ContextBroker 0.28, the dockerized version in my localhost on ubuntu 15.10 64 bits. $ curl localhost:1026/version { "orion" : { "version" : "0.28.0-next", "uptime" : "0 d, 0 h, 0 m, 6 s", "git_hash" : "067e13618c247daa4af61f82d7831f3015d9eb5d", "compile_time" : "Mon Mar 14 13:04:02 UTC 2016", "compiled_by" : "root", "compiled_in" : "838a42ae8431" } } The docker configuration I'm using is: $ cat docker-compose.yml mongo: image: mongo:2.6 command: --smallfiles --nojournal

问题 Based on this answer about how to scale Orion Context Broker with load balancing https://stackoverflow.com/a/33068119/3706998 what should be the behavior of subscriptions and also notifications? Witch server should it come from? What is the workflow? Could it cause some disturbe or cloned subscriptions ? 回答1: Let's consider different cases, depending on subscription cache usage. Let's consider two Orion nodes (A and B) without loss of generality, both sharing the same MongoDB instance. Using

问题 I have a subscription made to an entity's attribute to a MySql sink. The problem is that while I was testing my rest service to do a subscription if the data was not yet persisted, i made a ton of subscriptions. Now every time I do an update on the entity's attribute what happens is that the value is persisted a lot of times. Is there anyway of deleting a subscription without the subscriptionID? 回答1: Yes, it is. First, you can list the existing subscriptions with the GET /v2/subscriptions

问题 I have a subscription made to an entity's attribute to a MySql sink. The problem is that while I was testing my rest service to do a subscription if the data was not yet persisted, i made a ton of subscriptions. Now every time I do an update on the entity's attribute what happens is that the value is persisted a lot of times. Is there anyway of deleting a subscription without the subscriptionID? 回答1: Yes, it is. First, you can list the existing subscriptions with the GET /v2/subscriptions