[
https://issues.apache.org/jira/browse/CASSANDRA-10631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989365#comment-14989365
]
Sylvain Lebresne commented on CASSANDRA-10631:
----------------------------------------------
The changes to {{CQLTester}} actually exposed an unrelated bug: when a function
is replaced, we were not invalidating statement using that function. And since
we resolve functions at preparation time, this means the new function wasn't
taken into account for statements prepared prior to the change. While this
isn't really related to this issue, this does create unit test failure on this
branch and the fix is pretty simple, so I included it in my branch above.
Test results are here:
[utest|http://cassci.datastax.com/job/pcmanus-10631-testall/4/#showFailuresLink]
and
[dtesthttp://cassci.datastax.com/view/Dev/view/pcmanus/job/pcmanus-10631-dtest/lastCompletedBuild/testReport/|]
(the dtests have a few more failures than the last 2.2 run I've looked at.
Nothing seems related to this so I suspect it's just flapping tests, but I've
re-started the dtest to see).
> JSON Update not working with PreparedStatement
> ----------------------------------------------
>
> Key: CASSANDRA-10631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10631
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: Windows 7, Datastax Java Driver 2.2.0-rc2
> Reporter: Henrik Karlsson
> Assignee: Sylvain Lebresne
> Fix For: 2.2.x
>
> Attachments: test-json.zip
>
>
> When using PreparedStatement to insert and update a row with JSON the first
> "INSERT INTO {tablename} JSON ?" statement works OK. But when calling it a
> second time with a changed value on a field the field is not updated. If I
> use a SimpleStatement instead ("INSERT INTO {tablename} JSON '"+json+"'") the
> modified field is updated as expected.
> Attaching a test project that shows the problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
