lhotari commented on issue #10488: URL: https://github.com/apache/pulsar/issues/10488#issuecomment-833430949
There are other ways to solve the use case without having support in Pulsar to seek backwards. One possibility is to have some component consume the messages from the topic and publish index type of messages in another topic. Since the component could keep state while building the index messages, it can add message ids to previous index messages. The application can be build to use these application specific index messages to achieve what you are describing. If it wants to read the last n log messages, it would go the the "index topic" and read the index message and which would contain the message id of the message where to start reading from. A variation of this pattern would be to enhance the original messages to contain such "indexing information" instead of having a separate topic and messages for the purpose. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
