AntiBit82 commented on issue #14378:
URL: https://github.com/apache/pulsar/issues/14378#issuecomment-1048822271
Yes I did that now, and the results are the same: The sql lags 1 record
behind, doesn't show the latest...
`./pulsar-client produce sqltest -m "hello" -k **"test_1"**`
`presto> select * from pulsar."public/default".sqltest;
__value__ | __partition__ | __event_time__ | __publish_time__ |
__message_id__ | __sequence_id__ | __producer_name__ | __key__ | __properties__
-----------+---------------+----------------+------------------+----------------+-----------------+-------------------+---------+----------------
**(0 rows)**`
` ./pulsar-client produce sqltest -m "hello" -k **"test_2"**`
`presto> select * from pulsar."public/default".sqltest;
__value__ | __partition__ | __event_time__ |
__publish_time__ | __message_id__ | __sequence_id__ | __producer_name__ |
__key__ | __properties__
----------------+---------------+-------------------------+-------------------------+----------------+-----------------+-------------------+---------+----------------
68 65 6c 6c 6f | -1 | 1970-01-01 00:00:00.000 | 2022-02-23
14:08:41.905 | (2409,0,0) | 0 | standalone-6-7 |
**test_1** | {}
(1 row)`
So I guess it has to be some configuration problem then?
Can I somehow check if the settings I've mentioned a post above are even in
effect?
--
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]
