-
Notifications
You must be signed in to change notification settings - Fork 76
feat: implement direct Avro encoder for performance #445
New issue
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
base: main
Are you sure you want to change the base?
Conversation
e9c1cbc to
2fec4dd
Compare
Implement direct Avro encoder to eliminate GenericDatum intermediate layer, matching the decoder approach for better performance. Implementation: - Add avro_direct_encoder_internal.h with EncodeArrowToAvro API - Add avro_direct_encoder.cc implementing direct Arrow→Avro encoding - All primitive types: bool, int, long, float, double, string, binary - Temporal types: date, time, timestamp - Logical types: uuid, decimal - Nested types: struct, list, map (both string and non-string keys) - Union type handling for optional fields - Modify avro_writer.cc to use DataFileWriterBase with direct encoder - Add EncodeContext to reuse scratch buffers and avoid allocations This matches Java Iceberg implementation using Encoder interface directly, avoiding intermediate object allocation overhead.
2fec4dd to
8128b17
Compare
wgtmac
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't finished my review yet, just post my findings so far.
| Status EncodeArrowToAvro(const ::avro::NodePtr& avro_node, ::avro::Encoder& encoder, | ||
| const Type& type, const ::arrow::Array& array, int64_t row_index, | ||
| EncodeContext* ctx) { | ||
| if (!ctx) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed that we haven't checked null for DecodeContext* ctx in the decoder implementation. Can we use DecodeContext& and EncodeContext& ctx so we don't need to bother with null check?
| const size_t num_fields = avro_node->leaves(); | ||
|
|
||
| for (size_t i = 0; i < num_fields; ++i) { | ||
| const auto& field_node = avro_node->leafAt(i); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to check if num of fields mismatch between arrow array and avro node?
Co-authored-by: Gang Wu <[email protected]>
Co-authored-by: Gang Wu <[email protected]>
a6d7298 to
cc007f7
Compare
…dation Change EncodeContext* and DecodeContext* parameters to references to avoid null pointer checks and make the API safer. - Update EncodeContext* ctx to EncodeContext& ctx in encoder - Update DecodeContext* ctx to DecodeContext& ctx in decoder - Remove null check in EncodeArrowToAvro - Update all ctx-> to ctx. in both encoder and decoder - Update call sites to pass by reference instead of pointer - Add field count validation in AVRO_RECORD encoding to prevent out-of-bounds access
32730a9 to
8ed3065
Compare
Implement direct Avro encoder to eliminate GenericDatum intermediate layer, matching the decoder approach for better performance.
Implementation:
This matches Java Iceberg implementation using Encoder interface directly, avoiding intermediate object allocation overhead.