Aside from the duckdb CI error, I noticed a few hard-coded GERS + beyond release references we may want to also fix:
|
FROM read_parquet('s3://overturemaps-us-west-2/release/2025-04-23.0/theme=places/type=place/*', filename=true, hive_partitioning=1), |
|
FROM read_parquet('s3://overturemaps-us-west-2/release/2025-04-23.0/theme=places/type=place/*', filename=true, hive_partitioning=1), |
|
"s3://overturemaps-us-west-2/release/2024-09-18.0/theme=base/type=infrastructure/*", |
|
read_parquet('s3://overturemaps-us-west-2/release/2024-09-18.0/theme=base/type=water/*', filename=true, hive_partitioning=1) |
|
" read_parquet('s3://overturemaps-us-west-2/release/2024-07-22.0/theme=base/type=water/*', filename=true, hive_partitioning=1)\n", |
Originally posted by John McCall (@lowlydba) in #524 (review)
Aside from the duckdb CI error, I noticed a few hard-coded GERS + beyond release references we may want to also fix:
docs/docs/gers/gers-tutorial.mdx
Line 185 in 9b90974
docs/docs/gers/gers-tutorial.mdx
Line 474 in 9b90974
docs/docs/examples/ibis.mdx
Line 37 in 9b90974
docs/docs/examples/pandas.mdx
Line 79 in 9b90974
docs/static/notebooks/overture-duckdb-pandas-example.ipynb
Line 128 in 9b90974
Originally posted by John McCall (@lowlydba) in #524 (review)