fiware - Store in Cosmos data coming from Orion to Cygnus -


i have 1 doubt how persist data in architecture cygnus subscribed orion context broker , cygnus must persist data in cosmos. necessary implement custom webhdfs client persisting data cygnus cosmos or can automatically stored if configure cosmos via cli? after reading documentation don't know if "last step" can done through configuration using cli or if custom client needed. when not necessary custom webhdfs client?

as said, cygnus subscribes orion in order receive notifications desired entities, when of attributes changes.

what happens then? cygnus uses webhdfs rest api writting data cosmos hdfs, typically file per notified entity. initially, if file not exits, "create" operation rest api used; if exists, "append" operation used.

where above files created? cygnus hdfs files path as:

/user/<your_cosmos_username>/<notified_fiware_service>/<notified_fiware_servicepath>/<built_destination>/<built_destination>.txt 

the notified_fiware_service , notified_fiware_servicepath http headers sent orion in notification; how organize data. built_destination result of concatenating notified entityid , entitytype.

finally, your_cosmos_username linux , hdfs username in fiware lab cosmos deployment. obtained login fiware lab credentials @ http://cosmos.lab.fi-ware.org/cosmos-gui/. have once in life; is, let's say, provisioning step creates unix username , hdfs userspace.


Comments

Popular posts from this blog

java - Spring Data JPA: Why findOne(id) executing delete query internally? -

python - Mongodb How to add addtional information when aggregating? -

java - Incorrect order of records in M-M relationship in hibernate -