[ https://issues.apache.org/jira/browse/CASSANDRA-15883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yazal Ulloa updated CASSANDRA-15883: ------------------------------------ Description: I have a table like this: key1, key2, key3, column1, column2. When I delete a row with keys 1, 2, 3. and then insert a new row almost immediately with the same keys, cassandra does not store the new row even though the query executes successfully. How can I force Cassandra to store the new row, or do I have to change my data model? was: I have a table like this: key1, key2, key3, column1, column2. When I delete a row with keys 1, 2, 3. and then insert a new row with the same keys, cassandra does not store the new row even though the query executes successfully. How can I force Cassandra to store the new row, or do I have to change my data model? > Delete and save with same keys > ------------------------------ > > Key: CASSANDRA-15883 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15883 > Project: Cassandra > Issue Type: Bug > Reporter: Yazal Ulloa > Priority: Normal > > I have a table like this: key1, key2, key3, column1, column2. > > When I delete a row with keys 1, 2, 3. and then insert a new row almost > immediately with the same keys, cassandra does not store the new row even > though the query executes successfully. > > How can I force Cassandra to store the new row, or do I have to change my > data model? -- 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