You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2016/03/11 18:11:39 UTC
[jira] [Resolved] (CASSANDRA-6339) Provide mechanism for probing
specific endpoints for a row key and/or column
[ https://issues.apache.org/jira/browse/CASSANDRA-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko resolved CASSANDRA-6339.
------------------------------------------
Resolution: Not A Problem
Agree with Jonathan here. Closing as Not A Problem.
> Provide mechanism for probing specific endpoints for a row key and/or column
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-6339
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6339
> Project: Cassandra
> Issue Type: Improvement
> Environment: Production
> Reporter: Ahmed Bashir
>
> In order to facilitate problem diagnosis, there should be a mechanism for retrieving row/column information from a specific node as opposed to having the said node request data from replicas with some CL and reconciling the data. This mechanism should also avoid read repair and so forth; just a simple way to probe an endpoint to see what it knows about a row and/or column(s).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)