[jira] [Commented] (CASSANDRA-16160) Regression in cqlsh with regard to row id display
[
https://issues.apache.org/jira/browse/CASSANDRA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250684#comment-17250684
]
Brandon Williams commented on CASSANDRA-16160:
--
+1 from me too
> Regression in cqlsh with regard to row id display
> -
>
> Key: CASSANDRA-16160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16160
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> When you run a query such as
> {code}
> expand on;
> select * from table_with_clustering_keys where token(partition_key) =
> 1192326969048244361;
> {code}
> We print out a header for each row that looks like the following
> @ Row 1
> In 3.0 all values printed were uniq, but in 4.0 they are no longer unique
> {code}
> $ grep Row 3.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 1 @ Row 999
> 1 @ Row 998
> 1 @ Row 997
> 1 @ Row 996
> 1 @ Row 995
> 1 @ Row 994
> 1 @ Row 993
> 1 @ Row 992
> 1 @ Row 991
> 1 @ Row 990
> {code}
> {code}
> $ grep Row 4.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 10 @ Row 9
> 10 @ Row 8
> 10 @ Row 7
> 10 @ Row 6
> 10 @ Row 5
> 10 @ Row 48
> 10 @ Row 47
> 10 @ Row 46
> 10 @ Row 45
> 10 @ Row 44
> {code}
--
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
[jira] [Commented] (CASSANDRA-16160) Regression in cqlsh with regard to row id display
[
https://issues.apache.org/jira/browse/CASSANDRA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250526#comment-17250526
]
David Capwell commented on CASSANDRA-16160:
---
[~brandon.williams] mind reviewing as well?
> Regression in cqlsh with regard to row id display
> -
>
> Key: CASSANDRA-16160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16160
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> When you run a query such as
> {code}
> expand on;
> select * from table_with_clustering_keys where token(partition_key) =
> 1192326969048244361;
> {code}
> We print out a header for each row that looks like the following
> @ Row 1
> In 3.0 all values printed were uniq, but in 4.0 they are no longer unique
> {code}
> $ grep Row 3.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 1 @ Row 999
> 1 @ Row 998
> 1 @ Row 997
> 1 @ Row 996
> 1 @ Row 995
> 1 @ Row 994
> 1 @ Row 993
> 1 @ Row 992
> 1 @ Row 991
> 1 @ Row 990
> {code}
> {code}
> $ grep Row 4.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 10 @ Row 9
> 10 @ Row 8
> 10 @ Row 7
> 10 @ Row 6
> 10 @ Row 5
> 10 @ Row 48
> 10 @ Row 47
> 10 @ Row 46
> 10 @ Row 45
> 10 @ Row 44
> {code}
--
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
[jira] [Commented] (CASSANDRA-16160) Regression in cqlsh with regard to row id display
[
https://issues.apache.org/jira/browse/CASSANDRA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250524#comment-17250524
]
David Capwell commented on CASSANDRA-16160:
---
Thanks for looking into this [~aholmber]! Not sure if the default paging was
changed between the two clusters, it was not explicitly set.
patch LGTM +1
> Regression in cqlsh with regard to row id display
> -
>
> Key: CASSANDRA-16160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16160
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> When you run a query such as
> {code}
> expand on;
> select * from table_with_clustering_keys where token(partition_key) =
> 1192326969048244361;
> {code}
> We print out a header for each row that looks like the following
> @ Row 1
> In 3.0 all values printed were uniq, but in 4.0 they are no longer unique
> {code}
> $ grep Row 3.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 1 @ Row 999
> 1 @ Row 998
> 1 @ Row 997
> 1 @ Row 996
> 1 @ Row 995
> 1 @ Row 994
> 1 @ Row 993
> 1 @ Row 992
> 1 @ Row 991
> 1 @ Row 990
> {code}
> {code}
> $ grep Row 4.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 10 @ Row 9
> 10 @ Row 8
> 10 @ Row 7
> 10 @ Row 6
> 10 @ Row 5
> 10 @ Row 48
> 10 @ Row 47
> 10 @ Row 46
> 10 @ Row 45
> 10 @ Row 44
> {code}
--
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
[jira] [Commented] (CASSANDRA-16160) Regression in cqlsh with regard to row id display
[
https://issues.apache.org/jira/browse/CASSANDRA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17249985#comment-17249985
]
Adam Holmberg commented on CASSANDRA-16160:
---
Confirmed that it's the result of paging. Looking back a bit, I don't think
this behavior has ever been different. [~dcapwell] I'm wondering if
{{3.0-rows.results}} was just selected with page size set higher.
Anyway, here is a potential patch and test.
[patch|https://github.com/aholmberg/cassandra/pull/25]
[ci|https://app.circleci.com/pipelines/github/aholmberg/cassandra/122/workflows/0bc193fd-3256-4e53-8929-4a7725c682c8/jobs/1286/steps]
> Regression in cqlsh with regard to row id display
> -
>
> Key: CASSANDRA-16160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16160
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> When you run a query such as
> {code}
> expand on;
> select * from table_with_clustering_keys where token(partition_key) =
> 1192326969048244361;
> {code}
> We print out a header for each row that looks like the following
> @ Row 1
> In 3.0 all values printed were uniq, but in 4.0 they are no longer unique
> {code}
> $ grep Row 3.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 1 @ Row 999
> 1 @ Row 998
> 1 @ Row 997
> 1 @ Row 996
> 1 @ Row 995
> 1 @ Row 994
> 1 @ Row 993
> 1 @ Row 992
> 1 @ Row 991
> 1 @ Row 990
> {code}
> {code}
> $ grep Row 4.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 10 @ Row 9
> 10 @ Row 8
> 10 @ Row 7
> 10 @ Row 6
> 10 @ Row 5
> 10 @ Row 48
> 10 @ Row 47
> 10 @ Row 46
> 10 @ Row 45
> 10 @ Row 44
> {code}
--
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
[jira] [Commented] (CASSANDRA-16160) Regression in cqlsh with regard to row id display
[
https://issues.apache.org/jira/browse/CASSANDRA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17249917#comment-17249917
]
Adam Holmberg commented on CASSANDRA-16160:
---
I think it's not related to any schema in particular, but rather requires the
data to cross paging boundaries. I'm going to dig into it.
> Regression in cqlsh with regard to row id display
> -
>
> Key: CASSANDRA-16160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16160
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> When you run a query such as
> {code}
> expand on;
> select * from table_with_clustering_keys where token(partition_key) =
> 1192326969048244361;
> {code}
> We print out a header for each row that looks like the following
> @ Row 1
> In 3.0 all values printed were uniq, but in 4.0 they are no longer unique
> {code}
> $ grep Row 3.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 1 @ Row 999
> 1 @ Row 998
> 1 @ Row 997
> 1 @ Row 996
> 1 @ Row 995
> 1 @ Row 994
> 1 @ Row 993
> 1 @ Row 992
> 1 @ Row 991
> 1 @ Row 990
> {code}
> {code}
> $ grep Row 4.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 10 @ Row 9
> 10 @ Row 8
> 10 @ Row 7
> 10 @ Row 6
> 10 @ Row 5
> 10 @ Row 48
> 10 @ Row 47
> 10 @ Row 46
> 10 @ Row 45
> 10 @ Row 44
> {code}
--
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
[jira] [Commented] (CASSANDRA-16160) Regression in cqlsh with regard to row id display
[
https://issues.apache.org/jira/browse/CASSANDRA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226398#comment-17226398
]
David Capwell commented on CASSANDRA-16160:
---
we found the table
{code}
CREATE TABLE ks.tbl (
pk1 text,
pk2 text,
c1 timeuuid,
PRIMARY KEY ((pk1, pk2), c1)
) WITH CLUSTERING ORDER BY (c1 DESC)
{code}
> Regression in cqlsh with regard to row id display
> -
>
> Key: CASSANDRA-16160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16160
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: David Capwell
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-beta
>
>
> When you run a query such as
> {code}
> expand on;
> select * from table_with_clustering_keys where token(partition_key) =
> 1192326969048244361;
> {code}
> We print out a header for each row that looks like the following
> @ Row 1
> In 3.0 all values printed were uniq, but in 4.0 they are no longer unique
> {code}
> $ grep Row 3.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 1 @ Row 999
> 1 @ Row 998
> 1 @ Row 997
> 1 @ Row 996
> 1 @ Row 995
> 1 @ Row 994
> 1 @ Row 993
> 1 @ Row 992
> 1 @ Row 991
> 1 @ Row 990
> {code}
> {code}
> $ grep Row 4.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 10 @ Row 9
> 10 @ Row 8
> 10 @ Row 7
> 10 @ Row 6
> 10 @ Row 5
> 10 @ Row 48
> 10 @ Row 47
> 10 @ Row 46
> 10 @ Row 45
> 10 @ Row 44
> {code}
--
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
[jira] [Commented] (CASSANDRA-16160) Regression in cqlsh with regard to row id display
[
https://issues.apache.org/jira/browse/CASSANDRA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226382#comment-17226382
]
David Capwell commented on CASSANDRA-16160:
---
[~yifanc] do you remember the schema?
> Regression in cqlsh with regard to row id display
> -
>
> Key: CASSANDRA-16160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16160
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: David Capwell
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-beta
>
>
> When you run a query such as
> {code}
> expand on;
> select * from table_with_clustering_keys where token(partition_key) =
> 1192326969048244361;
> {code}
> We print out a header for each row that looks like the following
> @ Row 1
> In 3.0 all values printed were uniq, but in 4.0 they are no longer unique
> {code}
> $ grep Row 3.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 1 @ Row 999
> 1 @ Row 998
> 1 @ Row 997
> 1 @ Row 996
> 1 @ Row 995
> 1 @ Row 994
> 1 @ Row 993
> 1 @ Row 992
> 1 @ Row 991
> 1 @ Row 990
> {code}
> {code}
> $ grep Row 4.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 10 @ Row 9
> 10 @ Row 8
> 10 @ Row 7
> 10 @ Row 6
> 10 @ Row 5
> 10 @ Row 48
> 10 @ Row 47
> 10 @ Row 46
> 10 @ Row 45
> 10 @ Row 44
> {code}
--
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
[jira] [Commented] (CASSANDRA-16160) Regression in cqlsh with regard to row id display
[
https://issues.apache.org/jira/browse/CASSANDRA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225020#comment-17225020
]
Brandon Williams commented on CASSANDRA-16160:
--
I've been unable to reproduce this behavior, do you have an example schema?
> Regression in cqlsh with regard to row id display
> -
>
> Key: CASSANDRA-16160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16160
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: David Capwell
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-beta
>
>
> When you run a query such as
> {code}
> expand on;
> select * from table_with_clustering_keys where token(partition_key) =
> 1192326969048244361;
> {code}
> We print out a header for each row that looks like the following
> @ Row 1
> In 3.0 all values printed were uniq, but in 4.0 they are no longer unique
> {code}
> $ grep Row 3.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 1 @ Row 999
> 1 @ Row 998
> 1 @ Row 997
> 1 @ Row 996
> 1 @ Row 995
> 1 @ Row 994
> 1 @ Row 993
> 1 @ Row 992
> 1 @ Row 991
> 1 @ Row 990
> {code}
> {code}
> $ grep Row 4.0-rows.results | sort | uniq -c | sort -k1 -h -r | head -n 10
> 10 @ Row 9
> 10 @ Row 8
> 10 @ Row 7
> 10 @ Row 6
> 10 @ Row 5
> 10 @ Row 48
> 10 @ Row 47
> 10 @ Row 46
> 10 @ Row 45
> 10 @ Row 44
> {code}
--
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
