You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2012/11/08 09:42:11 UTC
[jira] [Created] (CASSANDRA-4931) Better printing of AbstractBound
in tracing
Sylvain Lebresne created CASSANDRA-4931:
-------------------------------------------
Summary: Better printing of AbstractBound in tracing
Key: CASSANDRA-4931
URL: https://issues.apache.org/jira/browse/CASSANDRA-4931
Project: Cassandra
Issue Type: Improvement
Affects Versions: 1.2.0 beta 1
Reporter: Sylvain Lebresne
Assignee: Sylvain Lebresne
Priority: Trivial
Fix For: 1.2.0 rc1
Attachments: 0001-Better-AbstractBound-printing-in-tracing.txt
We currently trace messages like:
{noformat}
Tracing.trace("Executing seq scan across {} sstables for {}..{}", new Object[]{view.sstables.size(), startWith, stopAt});
{noformat}
This lack a little bit of precision in the sense that it doesn't say if the start/end are inclusive or exclusive (all of which we do support). Also, for order preserving partitioner, we allow startWith and stopAt to be actual keys, and in that case the output will be 'DecoratedKey(<token>, <key_in_hex))' which unnecessarily obscure. Attaching patch to switch to a nicer representation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4931) Better printing of AbstractBound
in tracing
Posted by "Sylvain Lebresne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-4931:
----------------------------------------
Attachment: 0001-Better-AbstractBound-printing-in-tracing.txt
> Better printing of AbstractBound in tracing
> -------------------------------------------
>
> Key: CASSANDRA-4931
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4931
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.2.0 beta 1
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Trivial
> Fix For: 1.2.0 rc1
>
> Attachments: 0001-Better-AbstractBound-printing-in-tracing.txt
>
>
> We currently trace messages like:
> {noformat}
> Tracing.trace("Executing seq scan across {} sstables for {}..{}", new Object[]{view.sstables.size(), startWith, stopAt});
> {noformat}
> This lack a little bit of precision in the sense that it doesn't say if the start/end are inclusive or exclusive (all of which we do support). Also, for order preserving partitioner, we allow startWith and stopAt to be actual keys, and in that case the output will be 'DecoratedKey(<token>, <key_in_hex))' which unnecessarily obscure. Attaching patch to switch to a nicer representation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4931) Better printing of
AbstractBound in tracing
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493202#comment-13493202 ]
Jonathan Ellis commented on CASSANDRA-4931:
-------------------------------------------
+1
> Better printing of AbstractBound in tracing
> -------------------------------------------
>
> Key: CASSANDRA-4931
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4931
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.2.0 beta 1
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Trivial
> Fix For: 1.2.0 rc1
>
> Attachments: 0001-Better-AbstractBound-printing-in-tracing.txt
>
>
> We currently trace messages like:
> {noformat}
> Tracing.trace("Executing seq scan across {} sstables for {}..{}", new Object[]{view.sstables.size(), startWith, stopAt});
> {noformat}
> This lack a little bit of precision in the sense that it doesn't say if the start/end are inclusive or exclusive (all of which we do support). Also, for order preserving partitioner, we allow startWith and stopAt to be actual keys, and in that case the output will be 'DecoratedKey(<token>, <key_in_hex))' which unnecessarily obscure. Attaching patch to switch to a nicer representation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira