Skip to content

DM-52781: Allow joining across catalogs that have non-exact spatial coverage#1010

Merged
iagaponenko merged 2 commits intomainfrom
tickets/DM-52781
Mar 18, 2026
Merged

DM-52781: Allow joining across catalogs that have non-exact spatial coverage#1010
iagaponenko merged 2 commits intomainfrom
tickets/DM-52781

Conversation

@iagaponenko
Copy link
Copy Markdown
Contributor

The new implementation extends a concept of the "dominant database" to a collection of the "dominant databases". If more than one such database is found in the user query then a scope of the query is restricted to an intersection of chunks present in all such databases.

Other changes:

  • Improved error checking
  • Eliminated useless code
  • Refactoring the unit tests accordingly

The new implementation extends a concept of the "dominant database"
to a collection of the "dominant databases". If more than one such
database is found in the user query then a scope of the query is
restricted to an intersection of chunks present in all such databases.

Other changes:
- Improved error checking
- Eliminated useless code
- Refactoring the unit tests accordingly
Improvemens in the core query processing engine allows
joining the dependent and director tables sitting in
different databases, where the databases may have different spatial
coverage. The dependent user tables is exactly this case.
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 -- thanks!

@iagaponenko iagaponenko merged commit d7f0db5 into main Mar 18, 2026
7 checks passed
@iagaponenko iagaponenko deleted the tickets/DM-52781 branch March 18, 2026 03:55
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