pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [pulsar] sijie commented on issue #3828: Pulsar SQL is not able to read the latest message
Date Fri, 15 Mar 2019 06:45:42 GMT
sijie commented on issue #3828: Pulsar SQL is not able to read the latest message
URL: https://github.com/apache/pulsar/issues/3828#issuecomment-473177000
   @jerrypeng this is not just about not being able to read the event, but also about the
latency (how fast it can query the data). current assumption is assuming there are are events
"eventually" arrive and advance the LAC, which will significantly delay the messages being
visible to users if the events are delayed. so I think we still need to enable explicit write
lac on broker, so the lac will be advanced within a SLA. 
   The feature is already in bookkeeper. It is just a matter to enable it and make sure it
is working as expected. If pulsar broker doesn't want this feature to be turned on by default,
we can make it configurable and turned off by default. If people want this feature, they can
turn it on. I don't think we should just ignore this fact and try to explain to people who
don't really understand how the underlying stuff works.

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:

With regards,
Apache Git Services

View raw message