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/08/19 07:47:08 UTC

[GitHub] [pulsar] frank-dkvan opened a new issue #4976: Pulsar SQL can not query the latest ingested event in a topic , but Pulsar Consumer/Read always can.

frank-dkvan opened a new issue #4976: Pulsar SQL can not query the latest ingested event in a topic , but  Pulsar Consumer/Read always can.   
URL: https://github.com/apache/pulsar/issues/4976
 
 
   **Describe the bug**
   Pulsar SQL can not query the latest ingested event in a topic , but  Pulsar Consumer/Read always can.   
   
   the testing Pulsar version is 2.4.0
   
   from the two screenshots below, we can see the latest event is always missed in Palsar SQL. but Pulsar reader client can fetch the latest one correctly.
   
   I am new to Pulsar but very interested in Pulsar. don't know this is a bug, or just a kind interesting feature which needs some hidden config I don't know yet?
   
   **Screenshots**
   this is the testing code and screenshot of Pulsar Reader:
   ![image](https://user-images.githubusercontent.com/17067653/63247250-29e16b80-c297-11e9-95be-b5ec5322a36e.png)
   this is the testing query SQL and  screenshot in Pulsar SQL CLI:
   ![image](https://user-images.githubusercontent.com/17067653/63247438-a116ff80-c297-11e9-8354-534b0fb52ddc.png)
   
   

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