[CASSANDRA-11048] JSON queries are not thread safe

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 2.2.6, 3.0.4, 3.4
• Component/s: Legacy/Coordination
• Labels: easyfix newbie patch
• Severity: Critical
• Assignee: Tom Hobbs
• Reporter: Sergio Bossa

Authors

Tom Hobbs

Reviewers

Sergio Bossa

• Created: 20/Jan/16 17:41
• Updated: 16/Apr/19 09:30
• Resolved: 11/Feb/16 16:34

Description

org.apache.cassandra.cql3.Json uses a shared instance of JsonStringEncoder which is not thread safe (see 1), while JsonStringEncoder#getInstance() should be used (see 2).

As a consequence, concurrent select JSON queries often produce wrong (sometimes unreadable) results.

1. http://grepcode.com/file/repo1.maven.org/maven2/org.codehaus.jackson/jackson-core-asl/1.9.2/org/codehaus/jackson/io/JsonStringEncoder.java
2. http://grepcode.com/file/repo1.maven.org/maven2/org.codehaus.jackson/jackson-core-asl/1.9.2/org/codehaus/jackson/io/JsonStringEncoder.java#JsonStringEncoder.getInstance%28%29

Issue Links

• is duplicated by: CASSANDRA-11570 Concurrent execution of prepared statement returns invalid JSON as result
• is duplicated by: CASSANDRA-11923 select json not stable, sometimes wrong data mapping returned from cassandra.