Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IGNITE-15629 Management API introduced #10581

Closed
wants to merge 106 commits into from

Conversation

nizhikov
Copy link
Contributor

@nizhikov nizhikov commented Mar 6, 2023

Thank you for submitting the pull request to the Apache Ignite.

In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:

The Contribution Checklist

  • There is a single JIRA ticket related to the pull request.
  • The web-link to the pull request is attached to the JIRA ticket.
  • The JIRA ticket has the Patch Available state.
  • The pull request body describes changes that have been made.
    The description explains WHAT and WHY was made instead of HOW.
  • The pull request title is treated as the final commit message.
    The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
  • A reviewer has been mentioned through the JIRA comments
    (see the Maintainers list)
  • The pull request has been checked by the Teamcity Bot and
    the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.

@nizhikov nizhikov changed the title IGNITE-15629 WIP IGNITE-15629 Management API introduced Mar 29, 2023
/**
* Management command interface.
* Implementations represents single action to manage Ignite cluster.
*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should use tags like <p> to define paragraphs and/or new lines in javadocs. Otherwise it's represented as single line. You can check how it looks like with:
Снимок экрана 2023-04-24 в 15 20 07

* <li>Subcommand: {@code StateSetCommand}, {@code StateGetCommand}, etc.</li>
* </ul>
*/
public interface ComplexCommand<A extends IgniteDataTransferObject, R>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually no need in ComplexCommand at all. Registry is enough. Registry should be available to handle another registry,

@sonarcloud
Copy link

sonarcloud bot commented Apr 27, 2023

SonarCloud Quality Gate failed.    Quality Gate failed

Bug C 1 Bug
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 123 Code Smells

0.0% 0.0% Coverage
0.8% 0.8% Duplication

@nizhikov nizhikov closed this Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants