Re: [gdal-dev] Segfault with ogr2ogr and Parquet

2023-11-05 Thread Scott via gdal-dev
Thanks for the info Even! On 11/5/23 13:26, Even Rouault wrote: Scott, I don't reproduce anymore on master, and I strongly suspect this is the same issue as https://lists.osgeo.org/pipermail/gdal-dev/2023-November/057856.html which I fixed post-beta1 Even Le 05/11/2023 à 19:57, Scott via

Re: [gdal-dev] Segfault with ogr2ogr and Parquet

2023-11-05 Thread Even Rouault via gdal-dev
Scott, I don't reproduce anymore on master, and I strongly suspect this is the same issue as https://lists.osgeo.org/pipermail/gdal-dev/2023-November/057856.html which I fixed post-beta1 Even Le 05/11/2023 à 19:57, Scott via gdal-dev a écrit : ogr2ogr tst.gpkg PARQUET:"/vsicurl/https://ove

Re: [gdal-dev] Segfault with ogr2ogr and Parquet

2023-11-05 Thread Scott via gdal-dev
Check that. This is only on 3.8beta. Apologies. On 11/5/23 09:35, Scott via gdal-dev wrote: On debian 10 linux, using gdal 3.7.1 or 3.8beta, built with apache arrow 12.0, I get a segfault immediately after running either of these commands: ogr2ogr tst.gpkg PARQUET:"/vsicurl/https://overturema

[gdal-dev] Segfault with ogr2ogr and Parquet

2023-11-05 Thread Scott via gdal-dev
On debian 10 linux, using gdal 3.7.1 or 3.8beta, built with apache arrow 12.0, I get a segfault immediately after running either of these commands: ogr2ogr tst.gpkg PARQUET:"/vsicurl/https://overturemapswestus2.blob.core.windows.net/release/2023-10-19-alpha.0/theme=admins"; ogr2ogr tst.gpkg