[
https://issues.apache.org/jira/browse/CASSANDRA-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715133#action_12715133
]
Jun Rao commented on CASSANDRA-202:
-----------------------------------
I am not sure about this argument. By the same token, we should make all thrift
APIs getRow calls. Does that make it clear to the users? Probably not.
The only commonality among those methods is that they access a single row. The
fact that there is a key parameter already indicates that.
The problem with catching only at CFS level is that one can't get parameters
other than key and cf. Other parameters are useful for debugging purpose.
> 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.
