Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-16760

[fiware-stackoverflow] Can FIWARE context providers be used for historical data with QuantumLeap?

    Details

      Description

      Created question in FIWARE Q/A platform on 28-05-2020 at 13:05
      Please, ANSWER this question AT https://stackoverflow.com/questions/62063265/can-fiware-context-providers-be-used-for-historical-data-with-quantumleap

      Question:
      Can FIWARE context providers be used for historical data with QuantumLeap?

      Description:
      FIWARE offers using context providers to fetch data from external sources for entities that are queried through the context broker.

      With QuantumLeap, historical data can be stored in a time series database such as CrateDB.

      Is it possible to combine these two concepts? When querying for historical data in a QuantumLeap setup, could some data instead be fetched from another database via a registered context provider (or a similar proxy implementation)? Preferably using out-of-the-box FIWARE components without too much custom magic.

        Activity

        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        fla Fernando Lopez made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        fla Fernando Lopez made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        fla Fernando Lopez made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        fla Fernando Lopez made changes -
        HD-Enabler Quantum-Leap [ 11558 ]
        Description
        Created question in FIWARE Q/A platform on 28-05-2020 at 13:05
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/62063265/can-fiware-context-providers-be-used-for-historical-data-with-quantumleap


        +Question:+
        Can FIWARE context providers be used for historical data with QuantumLeap?

        +Description:+
        FIWARE offers using context providers to fetch data from external sources for entities that are queried through the context broker.

        With QuantumLeap, historical data can be stored in a time series database such as CrateDB.

        Is it possible to combine these two concepts? When querying for historical data in a QuantumLeap setup, could some data instead be fetched from another database via a registered context provider (or a similar proxy implementation)? Preferably using out-of-the-box FIWARE components without too much custom magic.
        Created question in FIWARE Q/A platform on 28-05-2020 at 13:05
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/62063265/can-fiware-context-providers-be-used-for-historical-data-with-quantumleap


        +Question:+
        Can FIWARE context providers be used for historical data with QuantumLeap?

        +Description:+
        FIWARE offers using context providers to fetch data from external sources for entities that are queried through the context broker.

        With QuantumLeap, historical data can be stored in a time series database such as CrateDB.

        Is it possible to combine these two concepts? When querying for historical data in a QuantumLeap setup, could some data instead be fetched from another database via a registered context provider (or a similar proxy implementation)? Preferably using out-of-the-box FIWARE components without too much custom magic.
        fla Fernando Lopez made changes -
        Assignee Fernando Lopez [ fla ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            fla Fernando Lopez
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: