Source JDBC: Support for spatial data types

[cazitouni]

Tell us about the problem you're trying to solve

I would like to do import and export of spatial datas between different databases but actually spatial types are automaticaly casted into strings. ( at least for Oracle and Postgis)

Describe the solution you’d like

I would like to do the exact same thing I do actually for non spatial data in my postgres/oracle databases but with the support of the geometry type.

Describe the alternative you’ve considered or used

No clear alternative for me at this point

Are you willing to submit a PR?

Maybe, but I will have to get into the project first.

[mahic]

@cazitouni +1 Not quite the same case as you, but I'm working with massive amounts of spatial data stored in Oracle in columns of type SDO_GEOMETRY which we want to export to Parquet, or optimally geoparquet as our team is doing analytics on top of spatial data with Spark and Sedona.

What I've currently done as a workaround is to make views in Oracle with
SDO_UTIL.TO_WKTGEOMETRY(GEOM) that I connect Airbyte to in order to be able to export it to Parquet.

I guess one of the potential issues with Airbyte supporting this is that (at least for SDO_GEOMETRY ) you don't only have the actual data but might also have metadata such as SRID associated with the type/column.

[andrewshrout]

Hoping this gets done as well. +1

Also working with parquet and spatial data.

[octavia-squidington-iii]

At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 365 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.