godfreyhe opened a new pull request #9035: [FLINK-13168] [table] clarify isBatch/isStreaming/isBounded flag in flink planner and blink planner URL: https://github.com/apache/flink/pull/9035 ## What is the purpose of the change *clarify isBatch/isStreaming/isBounded flag in flink planner and blink planner 1. isBatch in ConnectorCatalogTable, which tells if the tableSource/tableSink is BatchTableSource/BatchTableSink 2. isBatch in TableSourceQueryOperation, which tells if the tableSource is BatchTableSource 3. isStreaming in TableSourceTable, which tells if if the current table is on stream planner 4. bounded StreamTableSource could be used for both batch and stream, while unbounded StreamTableSource could only be used for stream. * ## Brief change log - *Add comments for `isBatch` in ConnectorCatalogTable&TableSourceQueryOperation, and where to use it* - *Add isBatchMode flag into XXXSchema to tell if the current planner should work in a batch or streaming mode in blink planner* - *rename isStreaming to isStreamMode to distinguish isBatch flag in (TableSourceTable)* ## Verifying this change all existing test should be passed, and add several tests to validate bounded & unbounded table source in blink planner ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (not applicable / docs / JavaDocs / **not documented**)
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
