yunfengzhou-hub opened a new issue, #10696: URL: https://github.com/apache/paimon/issues/10696
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Motivation Part of #10690. PIP-39 describes lake-stream mode for Spark as well as Flink, and nothing in Paimon's Spark catalog or table layer implements it yet. ### Solution Required behaviour: - A Spark catalog configured with a Lakestream Store can reach that store's tables. Paimon must not gain a dependency on any store implementation: a store becomes available by putting its jar on the classpath and naming it in the catalog configuration, with its own options passed through to it. - Reading `<table>$rt` returns the freshest data for that table, served by the store. Reading the table by its own name keeps returning Paimon snapshots. - A regular write to a lake-stream table reaches the store rather than Paimon. Writes to tables that are not lake-stream tables are unchanged. - Reading a table by its own name, including resolving its metadata and capabilities, must not touch the store and must not require the store's catalog configuration. A user who has not turned lake-stream mode on sees no change and gains no new failure mode. - Misconfiguration is reported as an error that names the store, rather than as a lookup failure or a silent fallback. - The user-facing behaviour is documented. ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
