[
https://issues.apache.org/jira/browse/AVRO-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523859#comment-17523859
]
Ten commented on AVRO-3493:
---------------------------
Unfortunately I have no time for this - I was just pointing it out.
I thought it would make sense to solve this issue once old still-relevant
issues are sorted out and moved here as part of the maintenance process - I'm
surprised this is already marked as resolved.
> Avro Rust - Follow-up on open issues of avro-rs
> -----------------------------------------------
>
> Key: AVRO-3493
> URL: https://issues.apache.org/jira/browse/AVRO-3493
> Project: Apache Avro
> Issue Type: Bug
> Components: rust
> Reporter: Ten
> Priority: Major
>
> First of all, thanks for taking over avro-rs.
> For workloads where high performance is required, Rust is typically a very
> adapted choice, and as Avro appears to be a format consistent whose goal is
> also performance, the use of both appears to be a very consistent framework.
> However, that crate had a number of open issues tracked via github issues
> (including bugs).
> As these appear to still be relevant, it seems to be necessary to move their
> tracking to here:
> [https://github.com/flavray/avro-rs/issues]
>
> Among the most important ones:
> [https://github.com/flavray/avro-rs/issues/47]
> [https://github.com/flavray/avro-rs/issues/195] (zero-allocation
> deserialization)
> [https://github.com/flavray/avro-rs/issues/70]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
