open_dataset() gains the ability to read spatial vector data formats (objects read by sf) using format="sf"to_sf() is now termed geom, to match the default used in duckdb’s st_read() function.open_dataset() now tries to guess the data format instead of defaulting to parquet when no format is explicitly provided.
spatial_join(), allows a variety of spatial joins.st_read_meta(), exposes the spatial metadata of remote spatial objects.new helper function, as_view(), creates a temporary view of a query.
write_dataset() now understands lazy queries, not just lazy tables.duckdbfs now has spatial data query support! Users can leverage spatial data operations like st_distance() and st_area() and request return values as sf objects. Supports network-based access too. See README.md
Added write_dataset() which can write to (potentially partitioned) parquet to local directories or remote (S3) buckets.
arrow-compatible URI notation:
s3://userid:secret_token@bucket-name?endpoint_override=data.ecoforecast.org* (match any file) or ** (recursive search) and just supply a path. Recursive search is then assumed automatically. Note: unlike arrow, this still supports the use of globs (*) elsewhere in the path, e.g. s3://bucket/*/pathduckdb_s3_config gains argument anonymous allowing users to ignore existing AWS keys that may be set in environmental variables or AWS configuration files. This can also be passed as the username position in URI notation, e.g. s3://anonymous@bucket_name.
open_dataset drops use of endpoint as an argument. Instead, alternative S3 endpoints can be set either by using the URI query notation or calling duckdb_s3_config() first. Additionally, any arguments to duckdb_s3_config(), including s3_endpoint, can now be passed to open_dataset through the .... Note these settings will override any set by the URI notation.