We are using datstax java driver 1.5.0
Thank you.
On Saturday, 12 May 2018, 10:37:04 GMT-7, Jeff Jirsa
wrote:
I haven't seen this before, but I have a guess.
What client/driver are you using?
Are you using a prepared statement that has every column listed for the update,
and leaving
I haven't seen this before, but I have a guess.
What client/driver are you using?
Are you using a prepared statement that has every column listed for the
update, and leaving the un-set columns as null? If so, the null is being
translated into a delete, which is clearly not what you want.
The dif
After further analyzing the data. I see some pattern. The rows which were
updated in last 2-3 weeks, the column which were not part of this update have
the null values.
Has anyone encountered this issue during the upgrade?
Thank you,
On Thursday, 10 May 2018, 19:49:50 GMT-7, kooljava2
Hello Jeff,
2.1.19 to 3.0.15.
Thank you.
On Thursday, 10 May 2018, 17:43:58 GMT-7, Jeff Jirsa
wrote:
Which minor version of 3.0
-- Jeff Jirsa
On May 11, 2018, at 2:54 AM, kooljava2 wrote:
Hello,
Upgraded Cassandra 2.1 to 3.0. We see certain data in few columns being set to
"n
Which minor version of 3.0
--
Jeff Jirsa
> On May 11, 2018, at 2:54 AM, kooljava2 wrote:
>
>
> Hello,
>
> Upgraded Cassandra 2.1 to 3.0. We see certain data in few columns being set
> to "null". These null columns were created during the row creation time.
>
> After looking at the data s
Hello,
Upgraded Cassandra 2.1 to 3.0. We see certain data in few columns being set to
"null". These null columns were created during the row creation time.
After looking at the data see a pattern where update was done on these rows.
Rows which were updated has data but rows which were not par
