We use proprietary and third party´s cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

AFAIK, the first option ("orion2cartodb") is a preliminary work done for a demo, which is not part of Cygnus.

Regarding Cygnus, first of all must be said from Cygnus 1.0.0 an important refactor was done: the code was split into cygnus-common, a suit of common classes and utilities for all kind of Cygnus agents; and cygnus-ngsi, containing the NGSI specific part of Cygnus, and known as "NGSI Cygnus agent". Other Cygnus agents can be added to Cygnus, such as "Twitter Cygnus agent", developed by Universidad Politécnica de Valencia; this Twitter agent uses cygnus-common as well.

Being said that, from Cygnus 1.0.0 a sink for CartoDB was included in cygnus-ngsi agent. This sink works as any other sink, i.e. it can be used in any cygnus-ngsi agent following the Apache Flume architecture. You can check for its documentation at: https://github.com/telefonicaid/fiware-cygnus/blob/master/doc/cygnus-ngsi/flumeextensionscatalogue/ngsicartodbsink.md

And within cygnus-common, you can find CartoDB backend classes, a set of utility classes available for all Cygnus agents; CartoDB sink within cygnus-ngsi uses it.

AFAIK, the first option ("orion2cartodb") is a preliminary work done for a demo, which is not part of Cygnus.

Regarding Cygnus, first of all must be said from Cygnus 1.0.0 an important refactor was done: the code was split into cygnus-common, a suit of common classes and utilities for all kind of Cygnus agents; and cygnus-ngsi, containing the NGSI specific part of Cygnus, and known as "NGSI Cygnus agent". Other Cygnus agents can be added to Cygnus, such as "Twitter Cygnus agent", developed by Universidad Politécnica de Valencia; this Twitter agent uses cygnus-common as well.

Being said that, from Cygnus 1.0.0 a sink for CartoDB was included in cygnus-ngsi agent. This sink works as any other sink, i.e. it can be used in any cygnus-ngsi agent following the Apache Flume architecture. You can check for its documentation at: https://github.com/telefonicaid/fiware-cygnus/blob/master/doc/cygnus-ngsi/flumeextensionscatalogue/ngsicartodbsink.mdhere.

And within cygnus-common, you can find CartoDB backend classes, a set of utility classes available for all Cygnus agents; CartoDB sink within cygnus-ngsi uses it.