简体   繁体   English

FIWARE 上下文提供程序可以用于 QuantumLeap 的历史数据吗?

[英]Can FIWARE context providers be used for historical data with QuantumLeap?

FIWARE offers using context providers to fetch data from external sources for entities that are queried through the context broker. FIWARE 提供使用上下文提供程序从外部源获取通过上下文代理查询的实体的数据。

With QuantumLeap, historical data can be stored in a time series database such as CrateDB.使用 QuantumLeap,历史数据可以存储在 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)?在 QuantumLeap 设置中查询历史数据时,是否可以通过注册的上下文提供程序(或类似的代理实现)从另一个数据库中获取一些数据? Preferably using out-of-the-box FIWARE components without too much custom magic.最好使用开箱即用的 FIWARE 组件,而无需太多自定义魔法。

You can always send the information to the QuantumLeap using the proper protocol.您始终可以使用适当的协议将信息发送到 QuantumLeap。 For this purpose, inside the FIWARE Ecosystem we have defined the IoT Agents to translate the common transport protocols and payload formats towards NGSI protocol.为此,在 FIWARE 生态系统中,我们定义了 IoT 代理,以将通用传输协议和有效负载格式转换为 NGSI 协议。 Additionally, there is other component, FIWARE Draco that could be used in order to translate the information from one DB to other.此外,还有其他组件 FIWARE Draco 可用于将信息从一个数据库转换到另一个数据库。 In case of QuantumLeap, and also any other FIWARE component, the normal way of working is through subscription to the source of data and this is the major reason why we put always in the architectures the FIWARE Orion Context Broker, whose purpose is to notify subscribers any update in the context information.在 QuantumLeap 以及任何其他 FIWARE 组件的情况下,正常的工作方式是通过订阅数据源,这是我们始终在架构中放置 FIWARE Orion Context Broker 的主要原因,其目的是通知订阅者上下文信息中的任何更新。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM