Skip to content

Conversation

skyglass
Copy link
Member

@skyglass skyglass commented Sep 4, 2025

Description

Added Exasol Trino connector support for JOIN PUSHDOWN by implementing connectorExpressionRewriter and convertPredicate in ExasolClient

Additional context and related issues

  • enabled testJoinPushDown() test in BaseJdbcConnectorTest
  • had to additionally implement toWriteMapping() in ExasolClient, because even some read-only parameterized queries require it for some scenarios.

Release notes

## Exasol Connect
* Add support for `join pushdown`

@cla-bot cla-bot bot added the cla-signed label Sep 4, 2025
@github-actions github-actions bot added docs exasol Exasol connector vertica Vertica connector labels Sep 4, 2025
@skyglass skyglass force-pushed the feature/750_join_push_down branch 5 times, most recently from 9dce6bc to 98b0b7e Compare September 4, 2025 20:49
Copy link
Member

@ebyhr ebyhr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This commit includes various changes unrelated to join pushdown. Please separate them into different commits.

@skyglass skyglass force-pushed the feature/750_join_push_down branch 2 times, most recently from 49489e2 to 183d636 Compare September 9, 2025 17:25
Copy link
Member Author

@skyglass skyglass left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved some review comments by adding tests for toWriteMapping and some other changes.
Also, in this improved solution BaseJdbcConnectorTest is not changed at all!
All necessary changes are done in TestExasolConnectorTest

testJoinPushdown() from BaseJdbcConnectorTest is enabled with SUPPORTS_JOIN_PUSHDOWN -> true flag

@skyglass skyglass force-pushed the feature/750_join_push_down branch from 183d636 to 077acbe Compare September 9, 2025 18:51
Copy link
Member Author

@skyglass skyglass left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Added test coverage for toWriteMapping and convertPredicate
  • Removed all changes from BaseJdbcConnectorTest
  • Splited the changes to 4 commits

Implementation of methods toWriteMapping and convertPredicate are required to make testJoinPushDown work.

Is it ok to keep these changes in one PR, or should I create separate PRs for each of these changes?

@skyglass skyglass force-pushed the feature/750_join_push_down branch 3 times, most recently from d7b955c to a320fe4 Compare September 10, 2025 07:23
@skyglass skyglass force-pushed the feature/750_join_push_down branch from a320fe4 to d994c52 Compare September 10, 2025 07:25
@skyglass skyglass changed the title Add support for JOIN PUSHDOWN in Exasol connector [Draft] Add support for JOIN PUSHDOWN in Exasol connector Sep 10, 2025
@skyglass skyglass marked this pull request as draft September 10, 2025 17:52
@skyglass
Copy link
Member Author

Converted this PR to DRAFT, because it contains many changes, which should be splited into several PRs.
Here are the first 2 PRs, which are created based on this PR:

  1. Implement toWriteMapping in ExasolClient for DECIMAL type #26603
  2. [Draft] Implement Basic convertPredicate in ExasolClient #26606

Next PRs will be created later, after the first two merged.

@skyglass
Copy link
Member Author

Closed, and will be used as DRAFT for implementing JOIN_PUSHDOWN

@skyglass skyglass closed this Sep 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed docs exasol Exasol connector vertica Vertica connector
Development

Successfully merging this pull request may close these issues.

3 participants