[Backlogmanager] [FIWARE-JIRA] (HELP-20540) [fiware-stackoverflow] FIWARE : QuantumpLeap fails to store subscribed data into TimeScaleDB though metadata are correctly inserted into TimeScaleDB

Fernando Lopez (JIRA) jira-help-desk at jira.fiware.org
Thu Jan 12 09:18:00 CET 2023


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

Fernando Lopez reassigned HELP-20540:
-------------------------------------

    Assignee: MARTEL

> [fiware-stackoverflow] FIWARE : QuantumpLeap fails to store subscribed data into TimeScaleDB though metadata are correctly inserted into TimeScaleDB
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HELP-20540
>                 URL: https://jira.fiware.org/browse/HELP-20540
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: MARTEL
>              Labels: fiware, fiware-orion, timescaledb
>
> Created question in FIWARE Q/A platform on 19-11-2022 at 11:11
> {color: red}Please, ANSWER this question AT{color} 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":{"timesSent":4,"lastNotification":"2022-11-18T17:29:41.535Z...}
> 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



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


More information about the Backlogmanager mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy