loserwang1024 commented on issue #547: URL: https://github.com/apache/fluss-rust/issues/547#issuecomment-4609700280
In the Java implementation, for compatibility reasons, each read operation involved truncating or appending fields based on the row schema at startup time. However, in the multi-table write interface described in [FIP-43 Fluss Multi-Table Subscription API](https://cwiki.apache.org/confluence/display/FLUSS/FIP-43++Fluss+Multi-Table+Subscription+API), I proposed returning the original row along with its type. Now, in fluss-rust, since we don’t have the same legacy constraints, could we go a step further and directly return the original row, schema ID, and type? This would allow users to handle schema resolution and field mapping on their own, enabling greater flexibility and avoiding unnecessary compatibility overhead from the start. @fresh-borzoni @luoyuxia ,WDYT? -- 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]
