Content Comparison

...

• Maybe approach Cassandra team about also replacing Jackson?
• Share this with PTLs and aim for implementation in Dublin release?

Cassandra Usage of Jackson

• Mailing list archives for Cassandra: http://cassandra.apache.org/community/#mailing
• Suggested upgrade of Jackson major version (1.4 to 2+): https://issues.apache.org/jira/browse/CASSANDRA-4102
• Key feature of JSON support: https://issues.apache.org/jira/browse/CASSANDRA-7970
  • Comment asking for JSON abstraction: https://issues.apache.org/jira/browse/CASSANDRA-7970?focusedCommentId=14333620&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14333620
    
    • "Maybe we could abstract slighty our use of jackson (put the helpers we need in Json.java maybe?), so that 1) we have only one place to change if we upgrade jackson and the API change (or we want to change of library) and 2) we save creating multiple ObjectMapper or JsonStringEncoder objects."
• Suggested move from json-simple to Jackson: https://issues.apache.org/jira/browse/CASSANDRA-8785
• Upgrade of Jackson minor version due to vulnerabilities (1.9.x): https://issues.apache.org/jira/browse/CASSANDRA-8974
• Upgrade of Jackson major version due to vulnerabilities (1.9.x to 2.9.5): https://issues.apache.org/jira/browse/CASSANDRA-14427
  • Similar analysis of the databind problems and gave themselves a similar waiver: https://issues.apache.org/jira/browse/CASSANDRA-14427?focusedCommentId=16479994&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16479994
    • "Assuming that condition is met, ObjectMapper also needs to be able to be able to handle polymorphic types.This can be done in 2 ways: 
      • ObjectMapper.enableDefaultTyping(). We don't do this in the code base. 
      • Explicitly defining polymorphic types using annotations JsonSubType or JsonTypeInfo. We don't do this either."

Conclusion So Far

For AAI project:

...