You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@avro.apache.org by "Andrew Peter Marlow (Jira)" <ji...@apache.org> on 2022/12/31 13:28:00 UTC

[jira] [Commented] (AVRO-3098) Make the resolving decoder optional in the avrogencpp generated code

    [ https://issues.apache.org/jira/browse/AVRO-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653314#comment-17653314 ] 

Andrew Peter Marlow commented on AVRO-3098:
-------------------------------------------

When I click on "All" for this ticket it reveals that Chris Wells made changes on the 3rd March 2022 but I cannot see any details. I don't see a PR for this work either. I am very interested in this fix and would like to see it move forward.

> Make the resolving decoder optional in the avrogencpp generated code 
> ---------------------------------------------------------------------
>
>                 Key: AVRO-3098
>                 URL: https://issues.apache.org/jira/browse/AVRO-3098
>             Project: Apache Avro
>          Issue Type: Improvement
>          Components: c++
>    Affects Versions: 1.10.2
>            Reporter: Janaa Sun
>            Priority: Minor
>
> It is better to make the resolving decoder as optional in the avrogencpp generated header files. This can be an added benefit for people looking for performance in the c++ code that does not go through this dynamic_cast check as a first step in the generated decode methods.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)