Enable Flink projection pushdown for PSC connector#131
Open
KevBrowne wants to merge 1 commit intopinterest:mainfrom
Open
Enable Flink projection pushdown for PSC connector#131KevBrowne wants to merge 1 commit intopinterest:mainfrom
KevBrowne wants to merge 1 commit intopinterest:mainfrom
Conversation
43f57d1 to
5f25ef7
Compare
5f25ef7 to
813dd37
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR implements SupportsProjectionPushDown for the PSC Flink connector, enabling Flink's optimizer to push column projections down to the source. This optimization reduces deserialization overhead by only deserializing the columns actually needed by queries, rather than deserializing the entire schema.
Key changes:
PscDynamicSource now implements SupportsProjectionPushDown
Added applyProjection() method to compute query-specific projections
Introduced format vs output projection separation (keyFormatProjection/valueFormatProjection for deserialization, keyOutputProjection/valueOutputProjection for row assembly)
Updated getScanRuntimeProvider() and createPscDeserializationSchema() to use the new projections
##Test plan
Unit Test
Internal Testing E2E w/ Flink
After submitting DDL with 42 columns
SELECT * FROM <Table> LIMIT 10; --> Produced RowType w/ all 42 columnsSELECT a, b, c FROM <Table> LIMIT 10;--> Produced RowType w/ 3 columns a,b,cSELECT a FROM <table> WHERE b = '<value>' LIMIT 10;Produced Rowtype w/ 2 columns a,b