Hi Benjamin,

Le 14/08/2025 à 20:17, Benjamin Philip a écrit :

serialization/deserialization features but arrow-rs provides
more features such as computation features.

This reminds me. What features will I have to support out of
(de)serialization
for an implementation to be considered complete?

You're probably aware of https://arrow.apache.org/docs/dev/status.html , otherwise it will give you an idea of the variety of features that *can* be implemented.

There isn't an official criterion for declaring an implementation "complete" (and we don't really use that term, either).

What is important is to address the most common needs that your users may have (such as OpenTelemetry data payloads). I would personally suggest:

- support the most common data types (all primitive types + at least list and struct + dictionary + basic support for extension types)
- support either the C Data Interface or the IPC format (preferably both)

In the IPC format, you don't need to support everything (tensors are rarely used, for example; endianness conversion is only useful if you plan to exchange data with big-endian systems...).

Regards

Antoine.

Reply via email to