You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@paimon.apache.org by "tsreaper (via GitHub)" <gi...@apache.org> on 2023/03/27 03:24:25 UTC

[GitHub] [incubator-paimon] tsreaper commented on issue #699: [Feature] Some problems with stream reading

tsreaper commented on issue #699:
URL: https://github.com/apache/incubator-paimon/issues/699#issuecomment-1484426588

   Hi! Thanks for reporting this issue. However I'd like to discuss your questions a bit more.
   
   In Q1 you mentioned that
   
   > when the snapshot corresponding to the timestamp expires, an error will be reported
   
   What error is reported under what condition? Could you explain what you're doing in detail when the error occurs? Could you add a complete exception stack in the issue description?
   
   You also mentioned that
   
   > scan.timestamp-millis > snapshot latest timestamp, then scans-mode = 'latest'
   
   As far as I remember, our current implementation has exactly the same effect. Is the actual behavior different? If yes, what is the actual behavior?
   
   In Q2 you said that
   
   > The parallelism is greater than the number of buckets during stream read, and the excess slots are not used
   
   This is expected for Flink sources. Users should either decrease the source parallelism or change bucket number to a larger value. Or are you suggesting something different? What would you like to suggest for this scenario?


-- 
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: issues-unsubscribe@paimon.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org