Details
-
Type:
Monitor
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: FIWARE-TECH-HELP
-
Labels:
Description
Created question in FIWARE Q/A platform on 19-11-2022 at 11:11
Please, ANSWER this question AT https://stackoverflow.com/questions/74499540/fiware-quantumpleap-fails-to-store-subscribed-data-into-timescaledb-though-met
Question:
FIWARE : QuantumpLeap fails to store subscribed data into TimeScaleDB though metadata are correctly inserted into TimeScaleDB
Description:
I'm trying to setup a (classic) workflow to store historical data into TimescaleDB via QuantumLeap and Orion subscription.
The subscription is correctly setup; I'am seeing the timesSent value incrementing everytime I am updating the attributes values in Orion. Example :
notification":
On the TimeScaleDB side, the metadata tables (in md_ets_metadata) are correctly created, so the link between QuantumLeap and TimeScaleDb is correctly setup and is working properly.
However, the values are not stored into TimescaleDB.
If I try to query directly QuantumLeap, I get the following error message :
"Notification not processed or not updated:
{'S': 'ERROR', 'V': 'ERROR', 'C': '42P01', 'M': 'relation "etbikehiredockingstation" does not exist', 'P': '13', 'F': 'parse_relation.c', 'L': '1381', 'R': 'parserOpenTable'}"
I am a bit stuck in how to troubleshoot more this issue as I don't have any further messages, even on the TimeScaleDB side except saying that the table etbikehiredockingstation doesn't exist, which it's true.
Any clue ?
Thanks in advance for your assistance.
Laurent
(Fiware member)
Connect directly to QuantumLeap, but same error
Activity
- All
- Comments
- History
- Activity
- Transitions
2023-01-12 05:32|CREATED monitor | # answers= 0, accepted answer= False