read parquet from s3 failing with 'GeoArrowEngine' has no attribute 'extract_filesystem' about dask-geopandas HOT 3 OPEN

Thanks @raybellwaves. I wonder if this is a duplicate of #241?

This started failing with the release of dask 2023.4.0 three days ago

I'm not aware of any related changes in this release. The extract_filesystem method in the traceback was added several releases ago (xref dask/dask#9699).

Also, as Joris mentioned here #241 (comment), I would expect GeoArrowEngine to have an extract_filesystem method regardless since it subclasses the arrow parquet engine in dask

from dask-geopandas.

Cross posting from the other thread #241 (comment)

=======
hi! i was able to look into this! if pyarrow is not installed then the inheritances falls apart because of the fallback import.

I think some envs default to have pyarrow so you really need a clean env to test this. A solution to this is to throw an import error/warning when instantiating GeoArrowEngine if pyarrow was not properly imported.

To reiterate

this fails

pip install dask dask-geopandas 

this works

pip install dask dask-geopandas  pyarrow
# or 
pip install dask[complete] dask-geopandas

from dask-geopandas.

might want to do something similar to how geopandas check if pygeos is installed

https://github.com/geopandas/geopandas/blob/04c2dee547777d9e87f9df4c85cc372a03b29f93/geopandas/_compat.py#L51-L67

from dask-geopandas.