yjshen opened a new pull request #1782: URL: https://github.com/apache/arrow-datafusion/pull/1782
# Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123. --> Closes #1708 . # What changes are included in this PR? <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> A row format backed by raw bytes: Each tuple consists of up to three parts: [null bit set] [values] [var length data] The null bit set is used for null tracking and is aligned to 1-byte. It stores one bit per field. In the region of the values, we store the fields in the order they are defined in the schema. - For fixed-length, sequential access fields, we store them directly. E.g., 4 bytes for int and 1 byte for bool. - For fixed-length, update often fields, we store one 8-byte word per field. - For fields of non-primitive or variable-length types, we append their actual content to the end of the var length region and store their offset relative to row base and their length, packed into an 8-byte word. # Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> No. <!-- If there are any breaking changes to public APIs, please add the `api change` label. --> # TODOs: - [ ] JIT the tuple field get/set with schema, avoid branching for each field in each row. - [ ] Null-bit free code path if the schema has no nullable fields. - [ ] Support more types. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
