-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[CALCITE-1861] Spatial index, based on Hilbert space-filling curve
Add SQL function Hilbert. It uses Google's uzaygezen library, and our wraper code is copied from LocationTech's SFCurve project. Rewrite calls to ST_DWithin to use a range of on a Hilbert column, plus the call to ST_DWithin for safety. Implement function ST_MakeEnvelope. Use constant reduction to recognize constant geometry expressions before we apply SpatialRules. Move interface Geom, and other classes, from GeoFunctions into new utility class Geometries. Geometry literals (not in the SQL parser (yet), but in RexNode space). Make Geom implement Comparable, so that it can be a literal value. Move SqlStdOperatorTables to new package, and rename to SqlOperatorTables. Add RelOptTestBase.Sql.withCatalogReaderFactory and withConformance, to make it easier to run planner tests with a different schema or SQL dialect. Deprecate RelReferentialConstraint.getNumColumns(). In tests and examples, call ST_Point(longitude, latitude) because conventionally x is longitude and y is latitude. (Yes, there's a tension here. In map references and English sentences latitude comes before longitude, but in Cartesian geometry x comes before y.) Close #2111
- Loading branch information
1 parent
39cf82b
commit eab043f
Showing
43 changed files
with
1,900 additions
and
419 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.