[
https://issues.apache.org/jira/browse/CASSSIDECAR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004926#comment-18004926
]
n.v.harikrishna commented on CASSSIDECAR-268:
---------------------------------------------
Thanks for pasting the response format! Have couple of questions.
* Nodetool
[repair|https://cassandra.apache.org/doc/stable/cassandra/managing/tools/nodetool/repair.html]
command has more flags. I find few important flags like {{-{-}preview{-}}} and
{{{}-full{}}}. Can they be supported as part of this pr? Are there any plans to
support rest of them in future?
* Is there a way to get the details of the status of the operation, like the
output printed by repair command? I feel jobStatus is not enough to understand
what is going on.
* I am not familiar with long running job framework, just want to know if
there is any co-relation between the {{jobId}} and repair id. If there is no
co-relation, how can I retrieve the repair ID from the job ID? Having repair ID
helps to trace repair in Cassandra logs.
> Sidecar endpoint to support on-demand repair operation
> ------------------------------------------------------
>
> Key: CASSSIDECAR-268
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-268
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Rest API
> Reporter: Arjun Ashok
> Assignee: Arjun Ashok
> Priority: Normal
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This proposal is part of an effort to introduce bespoke Sidecar APIs to
> support key operational functionality currently managed through nodetool
> commands. Introducing these APIs offers several benefits:
>
> Strong Contract Definition: APIs provide a well-defined contract for both
> request and response structures, reducing errors in operational tooling by
> eliminating the need to parse command results.
> Error Handling: A clear response contract allows for meaningful error
> messages to be communicated to clients, without exposing internal
> implementation details.
> Input Validation: APIs can incorporate input validation to enhance security
> by protecting against command injection attacks.
> Version Compatibility: By exposing a standardized interface, APIs ensure
> compatibility across different Cassandra versions, through the sidecar's
> abstraction.
> Access Control: APIs enable fine-grained access control, leveraging
> permissions and roles associated with client identities for precise
> authorization.
>
> This specific task introduces an endpoint that performs the repair operation
> for a given keyspace with several options ranging from the set of tables,
> token-range to be repaired, type of repair (incremental vs full) etc.. Since
> repair is a long-running operation, this API will leverage the async job
> management framework tracked in CASSANDRASC-150.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
