[ https://issues.apache.org/jira/browse/CASSANDRA-15435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Lerer updated CASSANDRA-15435: --------------------------------------- Test and Documentation Plan: Unit tests Status: Patch Available (was: In Progress) > SELECT JSON does not return the correct value for empty blobs > ------------------------------------------------------------- > > Key: CASSANDRA-15435 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15435 > Project: Cassandra > Issue Type: Bug > Components: CQL/Interpreter > Reporter: Benjamin Lerer > Assignee: Ekaterina Dimitrova > Priority: Normal > Attachments: 0001-Patch-applied-successfully.patch, Screen Shot > 2019-11-27 at 9.24.23 AM.png, Screen Shot 2019-11-27 at 9.25.09 AM.png, > Screen Shot 2019-11-27 at 9.25.37 AM.png, Screen Shot 2019-11-27 at 9.26.09 > AM.png, Screen Shot 2019-11-27 at 9.26.20 AM.png, Screen Shot 2019-11-27 at > 9.26.33 AM.png > > > In an attempt to fix the side effect of a problem CASSANDRA-13868 was > committed in 2.2.11, 3.0.15, 3.11.1 and trunk. > This patch introduced an issue on how empty values were rendered by {{SELECT > JSON}} queries. > Instead of returning the correct value for the type a null value was now > returned. > A user detected that problem for text column and opened CASSANDRA-14245 to > request a fix for that problem. Unfortunately, I misunderstood the problem > and the fix did not solve the real problem. It only made the code return 'an > empty string instead of null values. > The proper fix is to rollback the changes made for CASSANDRA-13868 and > CASSANDRA-14245. > Some unit tests also need to be added to test the behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org