Skip to content
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

Document spatial_partitioning_table_name system property #6768

Open
findepi opened this issue Jan 30, 2021 · 3 comments
Open

Document spatial_partitioning_table_name system property #6768

findepi opened this issue Jan 30, 2021 · 3 comments
Labels

Comments

@findepi
Copy link
Member

findepi commented Jan 30, 2021

Document spatial_partitioning_table_name

  • what's for
  • how it works
  • what should be the schema of that table
  • how is the table accessed (what user, access control checks, if any)
@findepi findepi added the docs label Jan 30, 2021
@findepi
Copy link
Member Author

findepi commented Jan 30, 2021

It seems that spatial_partitioning_table_name was necessary to trigger #6587, so i guess @JamesRTaylor you know all the things that need to be documented.
I will assign you, if you do not mind.

@JamesRTaylor
Copy link

@mosabua - probably makes sense to either add a new section under Connectors for Geospatial or add documentation here for spatial joins. Best source of information I've found is this issue. Also found this blog that has a lot of good information. Would be prudent to confirm with @martint that this functionality is all available in Trino. Other background information on spatial joins include these issues:

@JamesRTaylor JamesRTaylor assigned mosabua and unassigned JamesRTaylor Feb 1, 2021
@mosabua mosabua removed their assignment Apr 9, 2021
@palmerj
Copy link

palmerj commented Nov 1, 2021

Anyone still planning to document this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

4 participants