[
https://issues.apache.org/jira/browse/AVRO-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544956#comment-15544956
]
Tom White commented on AVRO-1605:
---------------------------------
I'm not sure how long the accessors would need to be there. In principle, they
could be removed if the internal code started using the Object overrides for
JSON values (e.g. {{Field(String, Schema, String, Object)}} rather than
{{Field(String, Schema, String, JsonNode)}}); however I don't know how feasible
(or performant) that would be.
It's more likely that we'd continue to use them even if we switched to a new
JSON API internally, since this would allow us to create new Field objects
(say), using a hidden {{Field(String, Schema, String, NewJsonRepresentation)}}
constructor. How would we remove the accessor for Field without exposing new
JSON APIs?
> Remove Jackson classes from public API
> --------------------------------------
>
> Key: AVRO-1605
> URL: https://issues.apache.org/jira/browse/AVRO-1605
> Project: Avro
> Issue Type: Sub-task
> Components: java
> Affects Versions: 1.7.8
> Reporter: Tom White
> Assignee: Gabor Szadovszky
> Fix For: 1.9.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
