[
https://issues.apache.org/jira/browse/CASSANDRA-16851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411462#comment-17411462
]
Ekaterina Dimitrova commented on CASSANDRA-16851:
-------------------------------------------------
On a second reading I think the upgrade in 3.0 probably didn't happen
intentionally as we actually have there Jackson-core-asl and Jackson-mapper-asl
which migrated in Jackson 2. So I opted out of touching those for now. CC
[~tatu-at-datastax] if he wants to add something on this.
Then I started the update for 3.11 and here it becomes interesting. It seems
there we use _BufferRecyclers.getJsonStringEncoder()_ which change has happened
in CASSANDRA-14427(Bump jackson version to >= 2.9.5). Initially the method used
was _JsonStringEncoder.getInstance(),_ added in __ CASSANDRA-11048 (Make SELECT
JSON and toJson() threadsafe)
Not sure now which method is more correct to use at this point. Thoughts?
> Update from Jackson 2.9 to 2.12
> -------------------------------
>
> Key: CASSANDRA-16851
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16851
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Tatu Saloranta
> Assignee: Tatu Saloranta
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Given that Jackson 2.9 support has ended, it would be good to move at least
> to the next minor version (2.10, patch 2.10.5) or later – latest stable being
> 2.12.4.
> I can test to see if anything breaks, but looking at existing Jackson usage
> there shouldn't be many issues.
> Assuming upgrade is acceptable there's the question of which branches to
> apply it to; I will first test it against 4.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
