[
https://issues.apache.org/jira/browse/CASSANDRA-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199362#comment-15199362
]
Stefania commented on CASSANDRA-11244:
--------------------------------------
+1 with two nits:
* [this
line|https://github.com/krummas/cassandra/commit/d22c57f29e332e521e0d4a75bb3a4fb63e81c734#diff-f81aff38a15b1c42ba45d578a3790adfR114]
is a bit long
*
[{{map.append(",");}}|https://github.com/krummas/cassandra/commit/d22c57f29e332e521e0d4a75bb3a4fb63e81c734#diff-f81aff38a15b1c42ba45d578a3790adfR128]
can be replaced with {{map.append(',');}}
> Add repair options to repair_history table
> ------------------------------------------
>
> Key: CASSANDRA-11244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11244
> Project: Cassandra
> Issue Type: Improvement
> Components: Coordination
> Reporter: Paulo Motta
> Assignee: Marcus Eriksson
> Priority: Minor
> Labels: lhf
> Fix For: 3.x
>
>
> It would be nice if options to trigger a repair (-pr, -local, -parallelism,
> incremental, etc) are also included in the
> {{system_distributed.parent_repair_history}} and
> {{system_distributed.repair_history}} tables.
> The simplest way would be to add it as a map to allow for new options in the
> future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
