Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
The initial implementation of "custom coders" for SpecificRecord is incomplete (it didn't initially handle logical types) and hasn't been battle-tested. Thus, it includes a feature flag (org.apache.avro.specific.use_custom_coder) to toggle between the new code and the old code. The initial default for this feature flag is false – defaulting to the old code – but when the implementation of SpecificRecord is completed and it's seen more production use, we should switch the default to false, on the way to eliminating the flag altogether (AVRO-2091).
Attachments
Issue Links
- blocks
-
AVRO-2091 Eliminate org.apache.avro.specific.use_custom_coder feature flag
- Open
- is blocked by
-
AVRO-2093 Extend "custom coders" to fully support union types
- Open
-
AVRO-2094 Extend "custom coders" to support logical types
- Open
-
AVRO-2090 Improve encode/decode time for SpecificRecord using code generation
- Resolved
- is duplicated by
-
AVRO-3168 Enable custom coders by default
- Open