Skip to content

DM-54401: Fixed an algorithm that sets the "dominant" database of a query#1009

Merged
iagaponenko merged 1 commit intomainfrom
tickets/DM-54401
Mar 16, 2026
Merged

DM-54401: Fixed an algorithm that sets the "dominant" database of a query#1009
iagaponenko merged 1 commit intomainfrom
tickets/DM-54401

Conversation

@iagaponenko
Copy link
Copy Markdown
Contributor

@iagaponenko iagaponenko commented Mar 14, 2026

The "dominant" database in a user query is the one whose partitioning parameters are used to determine which chunks are used during query analysis and dispatch. The previous implementation was sensitive to the order of tables in a query. This caused the query analysis to incorrectly determine a collection of chunks used when processing certain classes of queries.

The "dominant" database in a user query is the one whose partitioning
parameters are used to dermine which chunks wuld be used during
query processing.
@iagaponenko iagaponenko changed the title DM-DM-54401: Fixed an algorithm that sets the "dominant" database of a query DM-54401: Fixed an algorithm that sets the "dominant" database of a query Mar 15, 2026
Copy link
Copy Markdown
Contributor

@fritzm fritzm left a comment

Choose a reason for hiding this comment

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

LGTM -- nice find

@iagaponenko iagaponenko merged commit 9cfa74f into main Mar 16, 2026
7 checks passed
@iagaponenko iagaponenko deleted the tickets/DM-54401 branch March 16, 2026 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants