[
https://issues.apache.org/jira/browse/AVRO-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523873#comment-17523873
]
Martin Tzvetanov Grigorov commented on AVRO-3493:
-------------------------------------------------
It is resolved as "Incomplete" because you just threw at us some links and said
"take a look over there".
My reasoning is: if the reporter has no time to properly report an issue then
why should I waste mine to do it for him/her ?
Thank you! I am already aware of the old issues! I just didn't have time to
work on all of them yet.
> 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)
