You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@avro.apache.org by "Martin Tzvetanov Grigorov (Jira)" <ji...@apache.org> on 2023/01/01 20:45: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=17653460#comment-17653460 ] 

Martin Tzvetanov Grigorov commented on AVRO-3098:
-------------------------------------------------

No one worked on this ticket so far.

[~iroh]  is a member of Apache Infra team. I guess he did some batch issue editing at the time that was not directly related to this particular issue.

> 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)