[Backlogmanager] [FIWARE-JIRA] (HELP-9325) [fiware-stackoverflow] How to fill Cygnus.conf

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-9325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez updated HELP-9325:
---------------------------------
     HD-Chapter: Data
    Description: 
Created question in FIWARE Q/A platform on 26-11-2014 at 14:11
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/27150093/how-to-fill-cygnus-conf


+Question:+
How to fill Cygnus.conf

+Description:+
Some days ago I was able to run cygnus, on my Context Broker vm, like that the documentation says. All suscriptions between cygnus and CB are done without problems, and the notifications that the CB sends, reach cygnus.

My doubt is when I have to configure cygnus.conf, I think that, the failures that I have, when Cygnus sends data to COSMOS are related with this archive's fields configuration. The next file is the template to fill, available in the documentation:

### ============================================
###OrionHDFSSink configuration
###channel name from where to read notification events
cygnusagent.sinks.hdfs-sink.channel = hdfs-channel
### sink class, must not be changed
cygnusagent.sinks.hdfs-sink.type = es.tid.fiware.fiwareconnectors.cygnus.sinks.OrionHDFSSink
### Comma-separated list of FQDN/IP address regarding the Cosmos Namenode endpoints
cygnusagent.sinks.hdfs-sink.cosmos_host = x1.y1.z1.w1,x2.y2.z2.w2
###port of the Cosmos service listening for persistence operations; 14000 for httpfs, 50070 for webhdfs and free choice for inifinty
cygnusagent.sinks.hdfs-sink.cosmos_port = 14000
###default username allowed to write in HDFS
cygnusagent.sinks.hdfs-sink.cosmos_default_username = default
###default password for the default username
cygnusagent.sinks.hdfs-sink.cosmos_default_password = xxxxxxxxxxxxx
###HDFS backend type (webhdfs, httpfs or infinity)
cygnusagent.sinks.hdfs-sink.hdfs_api = httpfs
### how the attributes are stored, either per row either per column (row, column)
cygnusagent.sinks.hdfs-sink.attr_persistence = column
###Hive FQDN/IP address of the Hive server
cygnusagent.sinks.hdfs-sink.hive_host = x.y.z.w
### Hive port for Hive external table provisioning
cygnusagent.sinks.hdfs-sink.hive_port = 10000

### ============================================


But for me is not clear what direction i have to put in the next field:

### Comma-separated list of FQDN/IP address regarding the Cosmos Namenode endpoints
cygnusagent.sinks.hdfs-sink.cosmos_host = x1.y1.z1.w1,x2.y2.z2.w2


and I also don't know if the hive server field, the direction that i need to write is the same that fiware COSMOS instance's ip address:

### Hive FQDN/IP address of the Hive server
cygnusagent.sinks.hdfs-sink.hive_host = x.y.z.w



  was:

Created question in FIWARE Q/A platform on 26-11-2014 at 14:11
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/27150093/how-to-fill-cygnus-conf


+Question:+
How to fill Cygnus.conf

+Description:+
Some days ago I was able to run cygnus, on my Context Broker vm, like that the documentation says. All suscriptions between cygnus and CB are done without problems, and the notifications that the CB sends, reach cygnus.

My doubt is when I have to configure cygnus.conf, I think that, the failures that I have, when Cygnus sends data to COSMOS are related with this archive's fields configuration. The next file is the template to fill, available in the documentation:

### ============================================
###OrionHDFSSink configuration
###channel name from where to read notification events
cygnusagent.sinks.hdfs-sink.channel = hdfs-channel
### sink class, must not be changed
cygnusagent.sinks.hdfs-sink.type = es.tid.fiware.fiwareconnectors.cygnus.sinks.OrionHDFSSink
### Comma-separated list of FQDN/IP address regarding the Cosmos Namenode endpoints
cygnusagent.sinks.hdfs-sink.cosmos_host = x1.y1.z1.w1,x2.y2.z2.w2
###port of the Cosmos service listening for persistence operations; 14000 for httpfs, 50070 for webhdfs and free choice for inifinty
cygnusagent.sinks.hdfs-sink.cosmos_port = 14000
###default username allowed to write in HDFS
cygnusagent.sinks.hdfs-sink.cosmos_default_username = default
###default password for the default username
cygnusagent.sinks.hdfs-sink.cosmos_default_password = xxxxxxxxxxxxx
###HDFS backend type (webhdfs, httpfs or infinity)
cygnusagent.sinks.hdfs-sink.hdfs_api = httpfs
### how the attributes are stored, either per row either per column (row, column)
cygnusagent.sinks.hdfs-sink.attr_persistence = column
###Hive FQDN/IP address of the Hive server
cygnusagent.sinks.hdfs-sink.hive_host = x.y.z.w
### Hive port for Hive external table provisioning
cygnusagent.sinks.hdfs-sink.hive_port = 10000

### ============================================


But for me is not clear what direction i have to put in the next field:

### Comma-separated list of FQDN/IP address regarding the Cosmos Namenode endpoints
cygnusagent.sinks.hdfs-sink.cosmos_host = x1.y1.z1.w1,x2.y2.z2.w2


and I also don't know if the hive server field, the direction that i need to write is the same that fiware COSMOS instance's ip address:

### Hive FQDN/IP address of the Hive server
cygnusagent.sinks.hdfs-sink.hive_host = x.y.z.w



     HD-Enabler: Cosmos

> [fiware-stackoverflow] How to fill Cygnus.conf
> ----------------------------------------------
>
>                 Key: HELP-9325
>                 URL: https://jira.fiware.org/browse/HELP-9325
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Fermín Galán
>              Labels: fiware, fiware-cygnus
>
> Created question in FIWARE Q/A platform on 26-11-2014 at 14:11
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/27150093/how-to-fill-cygnus-conf
> +Question:+
> How to fill Cygnus.conf
> +Description:+
> Some days ago I was able to run cygnus, on my Context Broker vm, like that the documentation says. All suscriptions between cygnus and CB are done without problems, and the notifications that the CB sends, reach cygnus.
> My doubt is when I have to configure cygnus.conf, I think that, the failures that I have, when Cygnus sends data to COSMOS are related with this archive's fields configuration. The next file is the template to fill, available in the documentation:
> ### ============================================
> ###OrionHDFSSink configuration
> ###channel name from where to read notification events
> cygnusagent.sinks.hdfs-sink.channel = hdfs-channel
> ### sink class, must not be changed
> cygnusagent.sinks.hdfs-sink.type = es.tid.fiware.fiwareconnectors.cygnus.sinks.OrionHDFSSink
> ### Comma-separated list of FQDN/IP address regarding the Cosmos Namenode endpoints
> cygnusagent.sinks.hdfs-sink.cosmos_host = x1.y1.z1.w1,x2.y2.z2.w2
> ###port of the Cosmos service listening for persistence operations; 14000 for httpfs, 50070 for webhdfs and free choice for inifinty
> cygnusagent.sinks.hdfs-sink.cosmos_port = 14000
> ###default username allowed to write in HDFS
> cygnusagent.sinks.hdfs-sink.cosmos_default_username = default
> ###default password for the default username
> cygnusagent.sinks.hdfs-sink.cosmos_default_password = xxxxxxxxxxxxx
> ###HDFS backend type (webhdfs, httpfs or infinity)
> cygnusagent.sinks.hdfs-sink.hdfs_api = httpfs
> ### how the attributes are stored, either per row either per column (row, column)
> cygnusagent.sinks.hdfs-sink.attr_persistence = column
> ###Hive FQDN/IP address of the Hive server
> cygnusagent.sinks.hdfs-sink.hive_host = x.y.z.w
> ### Hive port for Hive external table provisioning
> cygnusagent.sinks.hdfs-sink.hive_port = 10000
> ### ============================================
> But for me is not clear what direction i have to put in the next field:
> ### Comma-separated list of FQDN/IP address regarding the Cosmos Namenode endpoints
> cygnusagent.sinks.hdfs-sink.cosmos_host = x1.y1.z1.w1,x2.y2.z2.w2
> and I also don't know if the hive server field, the direction that i need to write is the same that fiware COSMOS instance's ip address:
> ### Hive FQDN/IP address of the Hive server
> cygnusagent.sinks.hdfs-sink.hive_host = x.y.z.w



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)