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/03/15 03:40:26 UTC

[GitHub] [pulsar] sijie opened a new issue #3828: Pulsar SQL is not able to read the latest message

sijie opened a new issue #3828: Pulsar SQL is not able to read the latest message
URL: https://github.com/apache/pulsar/issues/3828
 
 
   **Describe the bug**
   
   Pulsar SQL is always lacking one message when querying pulsar topics.
   
   **Expected behavior**
   
   "read-my-write" semantic.
   
   if I write a bunch of messages to pulsar topics, and issue a query after "my-write", I should be able to query all the messages I written.
   
   **Reason**
   
   The problem is due to broker doesn't advance LAC, so when pulsar sql bypasses broker to query the data, it can only read entries up to the LAC that all the bookies learned. 
   
   **Fixes**
   
   Enable periodically write lac on broker.
   

----------------------------------------------------------------
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