Add ability to seek offsets

[onobc]

No description provided.

[onobc]

Consider support for SeekAware and/or PulsarReader

[cbornet]

NB: Pulsar Reader is available in reactive mode.

[onobc]

Users can manually seek offsets via the seek API on the Consumer or Reader.

For @PulsarListener the consumer can be accessed directly (described here. Once obtained, the seek API can be invoked.

Long term, something like SeekAware (Spring Kafka) is desired. Moving this out of 1.0.0 based on the above.

[KartikShrivastava]

Hey @onobc, can I work on this?

[onobc]

Hi @KartikShrivastava ,

Sure!. I have only looked at this "on the surface" though. I would suggest first coming up w/ a high level design (either discuss here or via a draft PR). It may be helpful to understand how we do this in Spring Kafka. Not that we will do exactly what is done there but it may help w/ ideas.

Thanks

[KartikShrivastava]

Cool, thanks for the info. I'll start with documenting my thoughts, will share it here for further discussion

[KartikShrivastava]

Hey @onobc, an update on this, currently to gain more context for this issue I'm learning more about spring-pulsar and spring ecosystem in general (since I'm from django background). Thus, this is taking more time than expected.

[onobc]

No worries @KartikShrivastava ! No rush at all. Also, if you ever have any questions on your journey about anything at all, don't hesitate to ping me directly. One way would be on the Pulsar community Slack channel.