You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/11/02 10:13:25 UTC

[GitHub] [pulsar] candlerb opened a new issue #5540: reset-cursor to absolute time

candlerb opened a new issue #5540: reset-cursor to absolute time
URL: https://github.com/apache/pulsar/issues/5540
 
 
   **Is your feature request related to a problem? Please describe.**
   It would be handy to be able to [reset-cursor](https://pulsar.apache.org/docs/en/next/pulsar-admin/#reset-cursor) to an absolute time, e.g. "start consuming from midnight".  Otherwise you have to calculate the time offset, and stuff it into the command immediately.
   
   There is a [mention](https://pulsar.apache.org/docs/en/next/admin-api-persistent-topics/#reset-cursor) of the corresponding REST API call which appears to have a `:timestamp` parameter - if that's an absolute time, then this is just an issue with the CLI.
   
   **Describe the solution you'd like**
   [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601#Durations) includes unambiguous ways of representing absolute and relative times.
   
   * `PT30M` - 30 minutes (relative offset)
   * `P1D` - one day (relative offset)
   * `1981-04-05T12:00` - absolute date/time (extended format)
   * `19810405T1200` - absolute date/time (basic format)
   
   It should be straightforward to parse and distinguish these cases, whilst falling back to existing behaviour (`10` = 10 minute offset, `2h` = 2 hour offset etc)
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services