[
https://issues.apache.org/jira/browse/TUBEMQ-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guocheng Zhang updated TUBEMQ-56:
---------------------------------
Description: Initially, in order to reduce business interference to the
system, we did not provide an offset query interface. Later we provided a
client-based offset reset API to implement the extractive-once consume
function. Now the offset query API should be necessary for client to let the
business clearly understand the offset situation of a topic, and through this
API, the business can do more features to achieve. (was: Initially, in order
to reduce business interference to the system, we did not provide an offset
query interface. Later we provided a client-based offset reset API to Implement
the extractive-once consume function. Now the offset query API should be
necessary for client to let the business clearly understand the offset
situation of a topic, and through this API, the business can do more features
to achieve.)
> Is it easier to use by adding a offset query API?
> -------------------------------------------------
>
> Key: TUBEMQ-56
> URL: https://issues.apache.org/jira/browse/TUBEMQ-56
> Project: Apache TubeMQ
> Issue Type: Improvement
> Reporter: Guocheng Zhang
> Priority: Major
>
> Initially, in order to reduce business interference to the system, we did not
> provide an offset query interface. Later we provided a client-based offset
> reset API to implement the extractive-once consume function. Now the offset
> query API should be necessary for client to let the business clearly
> understand the offset situation of a topic, and through this API, the
> business can do more features to achieve.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
