Skip to content

Conversation

@W1y1r
Copy link
Collaborator

@W1y1r W1y1r commented Nov 7, 2024

No description provided.


1. **Topic(主题)**: Topic 是 IoTDB 订阅客户端中用于分类数据的逻辑概念,可以看作是数据的发布通道。生产者将数据发布到特定的主题,而消费者则订阅这些主题以接收相关数据。不同于 Kafka,在 IoTDB 订阅客户端中,主题对应了待订阅的序列和时间范围,输出格式(消息或 TsFile),及可选的自定义处理逻辑。

2. **Consumer(消费者)**: Consumer 是 IoTDB 订阅客户端有所在的应用程序或服务,负责接收和处理发布到特定 Topic 的数据。Consumer 从队列中获取数据并进行相应的处理。在 IoTDB 订阅客户端中提供了两种类型的 Consumers:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. **Consumer(消费者)**: Consumer 是 IoTDB 订阅客户端有所在的应用程序或服务,负责接收和处理发布到特定 Topic 的数据。Consumer 从队列中获取数据并进行相应的处理。在 IoTDB 订阅客户端中提供了两种类型的 Consumers:
2. **Consumer(消费者)**: Consumer 是 IoTDB 的订阅客户端,负责接收和处理发布到特定 Topic 的数据。Consumer 从队列中获取数据并进行相应的处理。在 IoTDB 订阅客户端中提供了两种类型的 Consumers:


1. **Topic**: A Topic is a logical concept used in the IoTDB Subscription Client to categorize data, which can be considered as a data publication channel. Producers publish data to specific topics, and consumers subscribe to these topics to receive relevant data. Unlike Kafka, in the IoTDB subscription client, topics correspond to the sequence and time range to be subscribed to, output format (message or TsFile), and optional custom processing logic.

2. **Consumer**: Consumer is the application or service where the IoTDB subscription client is located, responsible for receiving and processing data published to specific topics. Consumers retrieve data from the queue and process it accordingly. There are two types of Consumers available in the IoTDB subscription client:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. **Consumer**: Consumer is the application or service where the IoTDB subscription client is located, responsible for receiving and processing data published to specific topics. Consumers retrieve data from the queue and process it accordingly. There are two types of Consumers available in the IoTDB subscription client:
2. **Consumer**: Consumer is an IoTDB subscription client, responsible for receiving and processing data published to specific topics. Consumers retrieve data from the queue and process it accordingly. There are two types of Consumers available in the IoTDB subscription client:


在下面应用场景中,使用 IoTDB 订阅客户端消费数据会有显著的优势:

1. **替换大量数据的轮询查询**:避免查询频率高、测点多时,轮询查询对原有系统性能的较大影响;避免查询范围不好确定问题,可保证下游拿到准确全量的数据;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. **替换大量数据的轮询查询**避免查询频率高、测点多时,轮询查询对原有系统性能的较大影响;避免查询范围不好确定问题,可保证下游拿到准确全量的数据
1. **持续获取最新数据**使用订阅的方式,比定时查询更实时、应用编程更简单、系统负担更小

在下面应用场景中,使用 IoTDB 订阅客户端消费数据会有显著的优势:

1. **替换大量数据的轮询查询**:避免查询频率高、测点多时,轮询查询对原有系统性能的较大影响;避免查询范围不好确定问题,可保证下游拿到准确全量的数据;
2. **与下游系统快速集成**:更方便对接 Flink、Spark、Kafka / DataX、Camel / MySQL、PG 等系统组件。不需要为每一个大数据组件,单独定制开发 IoTDB 的变更捕获等逻辑,可简化集成组件设计,提升开发效率。
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. **与下游系统快速集成**更方便对接 Flink、Spark、Kafka / DataX、Camel / MySQL、PG 等系统组件。不需要为每一个大数据组件,单独定制开发 IoTDB 的变更捕获等逻辑,可简化集成组件设计,提升开发效率
2. **简化数据推送至第三方系统**无需在 IoTDB 内部开发不同系统的数据推送组件,可以在第三方系统内实现数据的流式获取,更方便将数据发送至 Flink、KafkaDataX、CamelMySQL、PG 等系统

<img src="https://alioss.timecho.com/docs/img/Data_sub_05.png" alt="" style="width: 60%;"/>
</div>

1. **Topic(主题)**: Topic 是 IoTDB 订阅客户端中用于分类数据的逻辑概念,可以看作是数据的发布通道。生产者将数据发布到特定的主题,而消费者则订阅这些主题以接收相关数据。不同于 Kafka,在 IoTDB 订阅客户端中,主题对应了待订阅的序列和时间范围,输出格式(消息或 TsFile),及可选的自定义处理逻辑。
Copy link
Member

@qiaojialin qiaojialin Nov 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. **Topic(主题)**: Topic 是 IoTDB 订阅客户端中用于分类数据的逻辑概念,可以看作是数据的发布通道。生产者将数据发布到特定的主题,而消费者则订阅这些主题以接收相关数据。不同于 Kafka,IoTDB 订阅客户端中,主题对应了待订阅的序列和时间范围,输出格式(消息或 TsFile),及可选的自定义处理逻辑
1. **Topic(主题)**: Topic 是 IoTDB 的数据空间,由路径和时间范围表示(如 root.** 的全时间范围)。消费者可以订阅这些主题的数据(当前已有的和未来写入的)。不同于 Kafka,IoTDB 可在数据入库后再创建 Topic,且输出格式可选择 Message 或 TsFile 两种
* 输出 Message:实时获取数据(与 Kafka 相同),适合流式处理场景
* 输出 TsFile:直接将 IoTDB 中的 TsFile 文件拷贝出来,适合数据备份、迁移场景

@W1y1r W1y1r closed this Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants