Calling "peek" on a subscription with an offset of 0 results in a stacktrace

[zbentley]

Describe the bug
Calling "peek" on a subscription with an offset of 0 results in a stacktrace

To Reproduce

1. Create a non-partitioned topic.
2. Publish at least one message to it.
3. Create a subscription on it.
4. Using the management API, do $topic/subscription/$subscription/position/0

Expected behavior
A documented error code and message are returned to the user, indicating "zero is not a valid offset".

Actual behavior
A stacktrace and 500 error are returned.

Pulsar 2.9.1 on MacOS.

[zbentley]

The same (or very similar) behavior occurs if I perform a peek on a topic with a ledger ID that does not exist.

Either a 404 or something else obvious should be raised here, not a stacktrace.

[codelipenghui]

@zbentley It needs to create the subscription first, and then publish messages, to peek messages. The new subscription in Pulsar will use the latest position as the initial read position, so if you create the subscription after the message is published, the subscription will not have any backlogs, so you will not able to peek any messages from the subscription.

[github-actions]

The issue had no activity for 30 days, mark with Stale label.

[zbentley]

@codelipenghui that makes sense, I would expect it to error. But I'd expect a different error than a 500 and a stacktrace. The error should indicate what went wrong ("no backlog to peek at" or something).

[github-actions]

The issue had no activity for 30 days, mark with Stale label.

[github-actions]

The issue had no activity for 30 days, mark with Stale label.

[tisonkun]

Close as answered.