You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! In using duckdb 1.2.0, I just encountered the a crash when mixing a spatial predicate with with other columns in the where clause.
To reproduce:
CREATE TABLE land AS SELECT * FROM read_parquet('s3://overturemaps-us-west-2/release/2024-09-18.0/theme=base/type=land/*') WHERE bbox.xmin < -73.9654541015625 AND bbox.xmax > -73.970947265625 AND bbox.ymin < 40.772221877329024 AND bbox.ymax > 40.768061709366116;
SELECT id FROM land WHERE subtype = 'tree' AND ST_Intersects(geometry, ST_MakeEnvelope(-73.970947265625, 40.768061709366116, -73.9654541015625, 40.772221877329024));
will report 49 ids.
Now add a spatial index:
CREATE INDEX land_geom_idx ON land USING RTREE (geometry);
Hello! In using duckdb 1.2.0, I just encountered the a crash when mixing a spatial predicate with with other columns in the where clause.
To reproduce:
will report 49
id
s.Now add a spatial index:
and running the same
SELECT
will crash like so:If you return
subtype
in addition toid
, everything works as expected.The text was updated successfully, but these errors were encountered: