You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Konstantin Usachev (JIRA)" <ji...@apache.org> on 2016/03/10 17:15:40 UTC
[jira] [Created] (AVRO-1809) I wish to remove optimization from
GenericDatumReader.getResolver
Konstantin Usachev created AVRO-1809:
----------------------------------------
Summary: I wish to remove optimization from GenericDatumReader.getResolver
Key: AVRO-1809
URL: https://issues.apache.org/jira/browse/AVRO-1809
Project: Avro
Issue Type: Wish
Components: java
Reporter: Konstantin Usachev
Priority: Minor
There is an optimization at org.apache.avro.generic.GenericDatumReader.getResolver, when we cache creator thread and it's first returned value. At first, It looks redundant, because it saves three calls to Map.get, which is unmeasurable, especially after Schema's hashcode calculation optimization, made by the same author [~cutting], it's not obvious and adds additional complexity. Also caching of current thread whould be a source of bugs in case of different green threads libraries integration (which, actually, occurred during integration with Quasar).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)