docs(bq,sf,rs|processing): update voronoi doc #492
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request has been linked to Shortcut Story #397997: [internal] ST Voronoi running into memory limitations. |
vdelacruzb
changed the title
Jesus89
approved these changes
Apr 4, 2024
vdelacruzb
deleted the
bug/sc-397997/internal-st-voronoi-running-into-memory-limitations
branch
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Shortcut
Added the doc described in the ticked about Voronoi limitation for Bigquery, Snowflake and Redshift.
In Redshift for now it doesn't make a lot of sense because users will face first the VARCHAR size limitation. But for consistency and in case Redshift upgrades the size I've included it there too.
Type of change