We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As discussed in the ML (https://lists.apache.org/thread.html/r19aad8a34f63334d3fcd627106f69be13f689740b83930a4eecc17b3%40%3Cdev.arrow.apache.org%3E), the current implementation use hard-coded field names. This may cause some problems, for example, when reconstruct a usable schema from a list of FieldVectors.
So we resolve this problem by allowing NullVectors to have distinct field names.
This also makes the NullVector consistent with other types of vectors.
Reporter: Liya Fan / @liyafan82 Assignee: Liya Fan / @liyafan82
Note: This issue was originally created as ARROW-13645. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered:
Liya Fan / @liyafan82: Issue resolved by pull request 10949 #10949
Sorry, something went wrong.
liyafan82
No branches or pull requests
As discussed in the ML (https://lists.apache.org/thread.html/r19aad8a34f63334d3fcd627106f69be13f689740b83930a4eecc17b3%40%3Cdev.arrow.apache.org%3E), the current implementation use hard-coded field names. This may cause some problems, for example, when reconstruct a usable schema from a list of FieldVectors.
So we resolve this problem by allowing NullVectors to have distinct field names.
This also makes the NullVector consistent with other types of vectors.
Reporter: Liya Fan / @liyafan82
Assignee: Liya Fan / @liyafan82
PRs and other links:
Note: This issue was originally created as ARROW-13645. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: