polyzos commented on PR #1702: URL: https://github.com/apache/fluss/pull/1702#issuecomment-3306509226
@platinumhamburg Correct.. I want to check the best way to approach the initial design. Based on the convo here, I will craft an initial design that: 1. extends the current scanner API (instead of having these on the Lookuper) 2. takes buckets into account for API 3. keeps things simple by using the batch RPC (at least in the initial proposal version) However, since the goal was for small tables: 1. Do you think we should also consider multiple fetches? (this complicates thing a bit and im wondering if its indeed necessary) 2. Based on the above, if yes - I guess streaming RPC might make more sense in this scenario as well. Do you think it makes sense to differentiate between this two use cases and start with the first approach? and if there is demand and use case also work on the second for larger tables and streaming? Or do you think it will complicate the design/implementation so its better to consider both scenarios now? -- 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]
