feat: add backwards compatibility with 0.13.0 v2 datasets #2755
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.
A breaking change was made to the binary encoding in 0.14.0. v2 was still labeled as experimental at the time. However, a significant number of people have run into this issue and it can be difficult to migrate since it requires recreating the data. This PR adds support for reading the old style.
Note: this will only help reading lance datasets and not lance files. This is because the lance file reader uses the default projection (tries to infer which columns to read from the schema) and a lance dataset uses the field id -> column index mapping in the manifest. The default projection logic has changed and so that approach no longer works.