[jira] [Created] (CASSANDRA-14642) Document lock handling in CompactionStrategyManager

Marcus Eriksson created CASSANDRA-14642: --- Summary: Document lock handling in CompactionStrategyManager Key: CASSANDRA-14642 URL: https://issues.apache.org/jira/browse/CASSANDRA-14642 Project:

[jira] [Commented] (CASSANDRA-14395) C* Management process

[ https://issues.apache.org/jira/browse/CASSANDRA-14395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580875#comment-16580875 ] Dinesh Joshi commented on CASSANDRA-14395: -- Hi [~jolynch] thanks for the patch. I can take

[jira] [Commented] (CASSANDRA-14574) Incomplete handling of exceptions when decoding incoming messages

[ https://issues.apache.org/jira/browse/CASSANDRA-14574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580871#comment-16580871 ] Dinesh Joshi commented on CASSANDRA-14574: -- Hi [~jasobrown], overall the changes look good.

[jira] [Updated] (CASSANDRA-14388) Fix setting min/max compaction threshold with LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-14388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hanna updated CASSANDRA-14388: - Component/s: Compaction > Fix setting min/max compaction threshold with LCS >

[jira] [Updated] (CASSANDRA-14643) Performance overhead with COPY command while bulk data loading

[ https://issues.apache.org/jira/browse/CASSANDRA-14643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] NIKHIL THALLAPALLI updated CASSANDRA-14643: --- Description: Hello Team, We are facing performance overhead with COPY

[jira] [Updated] (CASSANDRA-14388) Fix setting min/max compaction threshold with LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-14388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hanna updated CASSANDRA-14388: - Labels: lcs (was: ) > Fix setting min/max compaction threshold with LCS >

[jira] [Comment Edited] (CASSANDRA-14574) Incomplete handling of exceptions when decoding incoming messages

[ https://issues.apache.org/jira/browse/CASSANDRA-14574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581223#comment-16581223 ] Jason Brown edited comment on CASSANDRA-14574 at 8/15/18 3:21 PM: --

[jira] [Commented] (CASSANDRA-10726) Read repair inserts should not be blocking

[ https://issues.apache.org/jira/browse/CASSANDRA-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581234#comment-16581234 ] Blake Eggleston commented on CASSANDRA-10726: - Review changes pushed to branch with a

[jira] [Created] (CASSANDRA-14643) Performance overhead with COPY command while bulk data loading

NIKHIL THALLAPALLI created CASSANDRA-14643: -- Summary: Performance overhead with COPY command while bulk data loading Key: CASSANDRA-14643 URL: https://issues.apache.org/jira/browse/CASSANDRA-14643

[jira] [Reopened] (CASSANDRA-14568) Static collection deletions are corrupted in 3.0 -> 2.{1,2} messages

[ https://issues.apache.org/jira/browse/CASSANDRA-14568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne reopened CASSANDRA-14568: -- Sorry I'm a bit slow to check this one, but I don't think the fix here is

[jira] [Updated] (CASSANDRA-14643) Performance overhead with COPY command while bulk data loading

[ https://issues.apache.org/jira/browse/CASSANDRA-14643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] NIKHIL THALLAPALLI updated CASSANDRA-14643: --- Description: Hello Team, We are facing performance overhead with COPY

[jira] [Commented] (CASSANDRA-14574) Incomplete handling of exceptions when decoding incoming messages

[ https://issues.apache.org/jira/browse/CASSANDRA-14574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581223#comment-16581223 ] Jason Brown commented on CASSANDRA-14574: - [~djoshi3] Thanks for reviewing. I agree with the

[jira] [Commented] (CASSANDRA-14635) Support table level configuration of monotonic reads

[ https://issues.apache.org/jira/browse/CASSANDRA-14635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581291#comment-16581291 ] Ariel Weisberg commented on CASSANDRA-14635: There was some discussion about supporting

[jira] [Updated] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static col

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-14638: -- Fix Version/s: 3.11.x 3.0.x > Column result order can

[jira] [Updated] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static col

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-14638: -- Reviewer: Benedict > Column result order can change in 'SELECT *' results

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581304#comment-16581304 ] Aleksey Yeschenko commented on CASSANDRA-14638: --- bq. Unfortunately I don't think there

[jira] [Updated] (CASSANDRA-14397) Stop compactions quicker when compacting wide partitions

[ https://issues.apache.org/jira/browse/CASSANDRA-14397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hanna updated CASSANDRA-14397: - Component/s: Compaction > Stop compactions quicker when compacting wide partitions

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581299#comment-16581299 ] Aleksey Yeschenko commented on CASSANDRA-14638: --- Proposed work-in-progress fix (test

[jira] [Updated] (CASSANDRA-13639) SSTableLoader always uses hostname to stream files from

[ https://issues.apache.org/jira/browse/CASSANDRA-13639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Karlsson updated CASSANDRA-13639: - Reproduced In: 3.0.15, 2.2.9 (was: 2.2.9, 4.0) Fix Version/s: (was: 4.x) >

[jira] [Commented] (CASSANDRA-13639) SSTableLoader always uses hostname to stream files from

[ https://issues.apache.org/jira/browse/CASSANDRA-13639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581085#comment-16581085 ] Jan Karlsson commented on CASSANDRA-13639: -- I tried running it with both 3.0.15 and trunk.

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581293#comment-16581293 ] Aleksey Yeschenko commented on CASSANDRA-14638: --- Unfortunately this is an accidental,

[jira] [Commented] (CASSANDRA-14644) CircleCI Builds should optional run in-tree tests other than test/unit

[ https://issues.apache.org/jira/browse/CASSANDRA-14644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581613#comment-16581613 ] Vinay Chella commented on CASSANDRA-14644: -- We faced this same issue while working on

[jira] [Commented] (CASSANDRA-14644) CircleCI Builds should optional run in-tree tests other than test/unit

[ https://issues.apache.org/jira/browse/CASSANDRA-14644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581636#comment-16581636 ] Jordan West commented on CASSANDRA-14644: - [~vinaykumarcse] done. Thanks! I will be happy to

[jira] [Created] (CASSANDRA-14644) CircleCI Builds should optional run in-tree tests other than test/unit

Jordan West created CASSANDRA-14644: --- Summary: CircleCI Builds should optional run in-tree tests other than test/unit Key: CASSANDRA-14644 URL: https://issues.apache.org/jira/browse/CASSANDRA-14644

[jira] [Assigned] (CASSANDRA-14644) CircleCI Builds should optional run in-tree tests other than test/unit

[ https://issues.apache.org/jira/browse/CASSANDRA-14644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West reassigned CASSANDRA-14644: --- Assignee: Vinay Chella > CircleCI Builds should optional run in-tree tests

[jira] [Updated] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static col

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-14638: -- Fix Version/s: 4.0.x Status: Patch Available (was: In

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581383#comment-16581383 ] Benedict commented on CASSANDRA-14638: -- [~jjordan]: there is no well defined behaviour for a

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581411#comment-16581411 ] Jeremiah Jordan commented on CASSANDRA-14638: - I was just thinking for the internode

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581459#comment-16581459 ] Aleksey Yeschenko commented on CASSANDRA-14638: --- bq. I was just thinking for the

[jira] [Commented] (CASSANDRA-14289) Document sstable tools

[ https://issues.apache.org/jira/browse/CASSANDRA-14289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581468#comment-16581468 ] Valerie Parham-Thompson commented on CASSANDRA-14289: - Thanks, [~hkroger]. I

[jira] [Comment Edited] (CASSANDRA-14289) Document sstable tools

[ https://issues.apache.org/jira/browse/CASSANDRA-14289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581468#comment-16581468 ] Valerie Parham-Thompson edited comment on CASSANDRA-14289 at 8/15/18 6:45 PM:

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581355#comment-16581355 ] Andy Tolbert commented on CASSANDRA-14638: -- {quote} What 3.0 does incorrectly is ordering

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581394#comment-16581394 ] Benedict commented on CASSANDRA-14638: -- Very true, and they're basically a lost cause. The

[jira] [Commented] (CASSANDRA-14568) Static collection deletions are corrupted in 3.0 -> 2.{1,2} messages

[ https://issues.apache.org/jira/browse/CASSANDRA-14568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581429#comment-16581429 ] Benedict commented on CASSANDRA-14568: -- Thanks for the input, when fixing this I had indeed

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581351#comment-16581351 ] Jeremiah Jordan commented on CASSANDRA-14638: - I would think we should be able to do a

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581386#comment-16581386 ] Jeff Jirsa commented on CASSANDRA-14638: We're talking about this in the context of prepared

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581500#comment-16581500 ] Aleksey Yeschenko commented on CASSANDRA-14638: --- Branches with the fix for

[jira] [Commented] (CASSANDRA-14638) Column result order can change in 'SELECT *' results when upgrading from 2.1 to 3.0 causing response corruption for queries using prepared statements when static c

[ https://issues.apache.org/jira/browse/CASSANDRA-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581341#comment-16581341 ] Aleksey Yeschenko commented on CASSANDRA-14638: --- [~slebresne] I assume you may have an

[jira] [Created] (CASSANDRA-14645) Clean up some dead code post CASSANDRA-13910

Aleksey Yeschenko created CASSANDRA-14645: - Summary: Clean up some dead code post CASSANDRA-13910 Key: CASSANDRA-14645 URL: https://issues.apache.org/jira/browse/CASSANDRA-14645 Project:

[jira] [Updated] (CASSANDRA-14645) Clean up some dead code post CASSANDRA-13910

[ https://issues.apache.org/jira/browse/CASSANDRA-14645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-14645: -- Status: Open (was: Patch Available) > Clean up some dead code post

[jira] [Comment Edited] (CASSANDRA-14645) Clean up some dead code post CASSANDRA-13910

[ https://issues.apache.org/jira/browse/CASSANDRA-14645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581798#comment-16581798 ] Aleksey Yeschenko edited comment on CASSANDRA-14645 at 8/16/18 12:49 AM:

[jira] [Commented] (CASSANDRA-14645) Clean up some dead code post CASSANDRA-13910

[ https://issues.apache.org/jira/browse/CASSANDRA-14645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581798#comment-16581798 ] Aleksey Yeschenko commented on CASSANDRA-14645: --- Code

[jira] [Updated] (CASSANDRA-14645) Clean up some dead code post CASSANDRA-13910

[ https://issues.apache.org/jira/browse/CASSANDRA-14645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-14645: -- Status: Patch Available (was: In Progress) > Clean up some dead code