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 2020/05/06 02:31:36 UTC
[GitHub] [pulsar] opera33 opened a new issue #6884: Pulsar SQL not returning latest row
opera33 opened a new issue #6884:
URL: https://github.com/apache/pulsar/issues/6884
**Describe the bug**
As titled, running query on Pulsar SQL, and it doesn't return the last row of the topic
**To Reproduce**
For example a topic has 0 row, then I add one row by publishing a message (aaa) to pulsar server. I query the table selecting *, it shows 0 rows. Then i publish another message (bbb), and try to query select * again, row "aaa" shows up, but not "bbb", if i publish another message (ccc), and then query, 2 rows returned: "aaa", "bbb"
**Expected behavior**
All the rows to show after the query
**Additional context**
Running on Pulsar 2.4.2
Also as someone is facing issue in 2.5.0
https://apache-pulsar.slack.com/archives/C5Z4T36F7/p1588064084428500
----------------------------------------------------------------
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
[GitHub] [pulsar] codelipenghui commented on issue #6884: Pulsar SQL not returning latest row
Posted by GitBox <gi...@apache.org>.
codelipenghui commented on issue #6884:
URL: https://github.com/apache/pulsar/issues/6884#issuecomment-625835520
close via #6908
----------------------------------------------------------------
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
[GitHub] [pulsar] codelipenghui edited a comment on issue #6884: Pulsar SQL not returning latest row
Posted by GitBox <gi...@apache.org>.
codelipenghui edited a comment on issue #6884:
URL: https://github.com/apache/pulsar/issues/6884#issuecomment-624480837
@opera33 You can upgrade to 2.5.1 and enable explicit LAC by setting bookkeeperExplicitLacIntervalInMills=10 in the broker.conf. This issue is fixed by https://github.com/apache/pulsar/pull/5822.
----------------------------------------------------------------
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
[GitHub] [pulsar] sijie commented on issue #6884: Pulsar SQL not returning latest row
Posted by GitBox <gi...@apache.org>.
sijie commented on issue #6884:
URL: https://github.com/apache/pulsar/issues/6884#issuecomment-624978156
@codelipenghui it is worth adding a note in the documentation about this setting.
----------------------------------------------------------------
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
[GitHub] [pulsar] codelipenghui commented on issue #6884: Pulsar SQL not returning latest row
Posted by GitBox <gi...@apache.org>.
codelipenghui commented on issue #6884:
URL: https://github.com/apache/pulsar/issues/6884#issuecomment-624480837
@opera33 You can upgrade to 2.5.1 and enable explicit LAC by setting bookkeeperExplicitLacIntervalInMills=10 in the broker.conf.
----------------------------------------------------------------
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