justinmclean opened a new issue, #4461: URL: https://github.com/apache/iggy/issues/4461
Split from #4446. ## Problem `iggy message poll` can start from `--offset`, `--first`, `--last` or `--next` (`core/cli/src/args/message.rs:180-226`), but not from a timestamp. The SDK already supports it with `PollingStrategy::timestamp` (`core/common/src/types/message/polling_strategy.rs:72`). ## Proposal - Add `--timestamp <TIME>` to the `polling_strategy` group in `PollMessagesArgs`, with no short form. - Accept an RFC 3339 time (`2026-10-08T10:00:00Z`), Unix microseconds, or a duration back from now (`15min`). - Map it to `PollingStrategy::timestamp` in `PollMessagesCmd::new` (`core/cli/src/commands/binary_message/poll_messages.rs:55`). ## Acceptance - `iggy message poll --timestamp <TIME> STREAM TOPIC PARTITION` returns the first messages at or after that time, for each of the three formats. - An invalid value fails with a clear clap error. - `--timestamp` conflicts with `--offset`, `--first`, `--last` and `--next`. - `--help` lists the new flag with an example of each format. - `core/integration/tests/cli/message/test_message_poll_command.rs` covers the new strategy and passes. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
