lhotari commented on PR #21920: URL: https://github.com/apache/pulsar/pull/21920#issuecomment-1900660348
> By reviewing the source code, I found that the broker had already made the conversion before returning the publish time, which means that the time string is related to the broker's timezone and it would be incorrect if the broker's timezone were incorrect.This bug may bring troubles in certain usage scenarios. @tikafu I noticed your in-depth investigation in https://github.com/apache/pulsar/issues/21891#issuecomment-1892970655 . Since we cannot break an existing interface, we should be understand exactly what the issue is by reproducing the issue in a unit test and fixing that particular actual issue. My assumption is that if the text formatted contains the timezone information, it should be possible to parse that into the timestamp later. Perhaps it is a bug in the org.apache.pulsar.common.util.DateFormatter after all? -- 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]
