[
https://issues.apache.org/jira/browse/CASSANDRA-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715152#action_12715152
]
Jonathan Ellis commented on CASSANDRA-202:
------------------------------------------
I'm skeptical that this would actually be useful in a real-world situation. If
you can't open a sstable because of a bug in cassandra then it's almost certain
the actual culprit was in the flush or compact code, so knowing the extra
parameters at the time of getRow helps not at all.
> Refactor different getRow calls in Table.java to more specific name and add
> more logging information
> ----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-202
> URL: https://issues.apache.org/jira/browse/CASSANDRA-202
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jun Rao
> Assignee: Jun Rao
> Attachments: issue202.patchv1, issue202.patchv2
>
>
> The Table class has five different getRow methods. We need to change them to
> more appropriate names. Also, when an IOException occurs, it would be useful
> to log the parameters of the request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
