codelipenghui commented on a change in pull request #12613:
URL: https://github.com/apache/pulsar/pull/12613#discussion_r742765329
##########
File path: site2/website-next/docs/sql-deployment-configurations.md
##########
@@ -44,6 +115,20 @@ pulsar.zookeeper-uri=localhost1,localhost2:2181
```
+A frequently asked question is why my latest message not showing up when
querying with Pulsar SQL.
+It's not a bug but controlled by a setting, by default bk LAC only advanced
when subsequent entries are added.
+If there is no subsequent entries added, the last entry written will not be
visible to readers until the ledger is closed.
+We can add following setting to change the behavior:
+In Broker config, set
+bookkeeperExplicitLacIntervalInMills > 0
+bookkeeperUseV2WireProtocol=false
+
+And in Presto config, set
+pulsar.bookkeeper-explicit-interval > 0
+pulsar.bookkeeper-use-v2-protocol=false
Review comment:
Format as a block
##########
File path: site2/website-next/docs/sql-deployment-configurations.md
##########
@@ -44,6 +115,20 @@ pulsar.zookeeper-uri=localhost1,localhost2:2181
```
+A frequently asked question is why my latest message not showing up when
querying with Pulsar SQL.
+It's not a bug but controlled by a setting, by default bk LAC only advanced
when subsequent entries are added.
+If there is no subsequent entries added, the last entry written will not be
visible to readers until the ledger is closed.
+We can add following setting to change the behavior:
+In Broker config, set
+bookkeeperExplicitLacIntervalInMills > 0
+bookkeeperUseV2WireProtocol=false
Review comment:
Format as a block
--
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]
