[FLINK-1254] Fix compiler bug for pipeline breaker placement #216
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
StephanEwen
added a commit
to StephanEwen/flink
that referenced
this pull request
Nov 19, 2014
zhijiangW
pushed a commit
to zhijiangW/flink
that referenced
this pull request
Jul 23, 2019
Submitting the markup file for a blog post by Andrey and Fabian about state TTL. This closes apache#216
HuangZhenQiu
pushed a commit
to HuangZhenQiu/flink
that referenced
this pull request
Sep 20, 2022
tharvey5
added a commit
to tharvey5/flink
that referenced
this pull request
Jun 25, 2025
Enable's storage partitioned joined to work e2e with a DynamicTableSource such as Iceberg Table that Supports Partitioning - calls applyPartitionedRead from Flink Planner to notify any table source that implements `SupportsPartitioning` that SPJ can be used - Improve `isPartitionedBy` check which now can account for filter pushdown optimizations when determining whether SPJ can be applied **Following queries DO utilize SPJ** ``` select count(*) from iceberg.db.simple_bucketed as table1 join iceberg.db.simple_bucketed_2 as table2 on table1.user_id = table2.user_id2 ``` ``` select count(*) from iceberg.db.user_id_two_partition_cols t1 join iceberg.db.user_id_two_partition_cols_2 t2 on t1.dt = t2.dt and t1.user_id = t2.user_id ``` ``` select count(*) from iceberg.db.user_id_two_partition_cols t1 join iceberg.db.user_id_two_partition_cols_2 t2 on t1.dt = t2.dt and t1.user_id = t2.user_id where t1.dt = '\''2025-05-01'\'' and t2.dt = '\''2025-05-01'\'' ``` **The following Query DO NOT apply SPJ optimization** ``` select count(*) from iceberg.db.simple_bucketed as table1 join iceberg.db.simple_bucketed_32 as table2 on table1.user_id = table2.user_id2 ``` Results all came back as expected as compared with Spark/Presto - 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, Kubernetes/Yarn, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.