Java subscriber consumed from oldest message rather than latest

[matt2e]

In Stuart's demo, his subscriber was configured to read from the latest message but ended up consuming from the oldest

[matt2e]

I can't repro this.
Tried the following

• ftl dev backend/runner/pubsub/testdata/java
• In console, call publisher.publishTen a few times. Confirm that subscribers consume the events that were published
• In backend/runner/pubsub/testdata/java/subscriber/src/main/java/xyz/block/ftl/java/test/subscriber/Subscriber.java:
  • Duplicate the function consumeFromLatest and rename it to something like consumeFromLatest2
  • Save
• FTL deploys the new code. consumeFromlatest2 does not consume any old events immediately.
• Call publisher.publishOne. consumeFromlatest2 consumes one event (as do other subs)

Alternative theory: Stuart had done a dry runthrough before the recording where he had created the same module + topic + subscription names. That meant that when he wrote the code in the recording there was already an existing consumer group with an existing offset in redpanda. So the LATEST option was never actually used.
@stuartwdouglas I know it'll been a while since you recorded when you come back from your break, but do you remember?

[matt2e]

Closing: Stuart confirmed that he made the same subscription before the video recording