fiware-cygnus

问题 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

问题 Following the instructions on this link I only changed 2 config files. The first one is cygnus_instance_1.conf (actually I just renamed the example file): ##### # # Configuration file for apache-flume # ##### # Copyright 2014 Telefonica Investigación y Desarrollo, S.A.U # # This file is part of fiware-cygnus (FI-WARE project). # # fiware-cygnus is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General # Public License as published by the Free

问题 The problem is the following: After having created a table with Cygnus 0.2.1, I receive a MapReduce error when trying to select a column from Hive. If we see the files created in hadoop by Cygnus, we can see that the format used is JSON. This problem didn't appear in previous versions of Cygnus as it was creating hadoop files in CSV format. In order to test it, I left 2 tables created reading from each format. You can compare and see the error with the following queries: SELECT entitytype

问题 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

问题 I'm trying to configure Cygnus in order to persist Orion context data in a MySQL database. I have installed phpmyadmin, and I'm trying to use this database to save the data. The whole workflow is the following one: Orion recives some data, then it is sent to Cygnus, and finally Cygnus sends it to the SQL db. This is my configuration: # OrionMySQLSink configuration # channel name from where to read notification events cygnusagent.sinks.mysql-sink.channel = mysql-channel # sink class, must not

问题 I'm trying to run Cygnus but there might be an error in cygnus.conf file or the way the connector is executed because nothing appears neither in my HDFS space in Cosmos nor in my MySQL. I've made a suscription and this works well. Here is my .conf file 1 and what I get when executing cygnus 2. 回答1: This is a known issue with Cygnus 0.5 (the one you are ussing according to the logs you are citing): the path to the matching table and the matching table file itself (cygnusagent.sources.http