You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Janaa Sun (Jira)" <ji...@apache.org> on 2021/03/27 22:42:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Janaa Sun updated AVRO-3098:
----------------------------
Description: 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. (was: It is better to make the resolving decoder as optional in the avrogencpp generated header files. This can be a advantage for people looking for performance in the cpp code that does not go through this dynamic_cast check as a first step in the generated decode methods.)
> 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.3.4#803005)