Uses LargeString to help avoid offset overflow errors #147
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.
Pyarrow's string array can only handle memory locations with an offset that uses 32 bits. This limits not just individual strings, but string arrays to 2GB in size. Since we frequently use datasets that can breach that limit, we move to LargeStringArrays. The additional memory overhead is modest in a table (string columns X 4 bits X num rows extra).