-
Notifications
You must be signed in to change notification settings - Fork 26
feat: geodatafusion integration #222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
We can already include geodatafusion functions in datafusion-postgres. The next step is to check whether we can make the output format consistent with original postgis. Original postgis, it's WKB in hex encoding without postgres' bytea hex encoding prefix (\x) Current geodatafusion+datafusion-postgres: |
|
We can now get ewkb serialization: |
|
|
||
| [features] | ||
| default = ["arrow"] | ||
| default = ["arrow", "postgis"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will remove this before merging
| datafusion.workspace = true | ||
| datafusion-pg-catalog = { path = "../datafusion-pg-catalog", version = "0.14.0" } | ||
| #geodatafusion = { version = "0.1.1", optional = true } | ||
| geodatafusion = { git = "https://github.com/sunng87/geodatafusion", branch = "feature/datafusion-52", optional = true } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
switch to released version
|
|
Fixes #176
This patch is only for demo. By combining geodatafusion, we will have PostGIS experience or even compatibility in next future releases.
And I wish geodatafusion could provide an entrypoint API to install all UDFs to
SessionContext.