Skip to content

Conversation

@sashapolo
Copy link
Contributor

@sashapolo sashapolo force-pushed the ignite-16717 branch 11 times, most recently from 6f71818 to a286f6d Compare May 17, 2022 19:17
@sashapolo sashapolo force-pushed the ignite-16717 branch 2 times, most recently from c17e14a to 81715e2 Compare May 18, 2022 14:52
private final byte major;

/** Minor version number. */
private final byte minor;
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are we restricting version components with byte? Is it imposed by the semver spec? If not, let's make it int just in case.

Copy link
Contributor Author

@sashapolo sashapolo May 20, 2022

Choose a reason for hiding this comment

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

I copied this part from Ignite 2. I'd prefer to leave it as a byte for now

* Extracts the local state (if any) and starts the CMG.
*
* @return Future that resolves into the CMG Raft service or {@code null} if the local state is empty.
* @return Future, that resolves into the CMG Raft service, or {@code null} if the local state is empty.
Copy link
Contributor

Choose a reason for hiding this comment

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

Would they really put that comma after 'Future' in English?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've put these commas to emphasize the fact that the future itself can be null and it will not resolve to a null value

ValidationError validationError = NodeValidator.validateNode(state, validationInfo);

if (validationError != null) {
throw new IgniteInternalException(validationError.rejectReason());
Copy link
Contributor

Choose a reason for hiding this comment

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

Should a specific exception class be introduced for self-validation failures?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't know, why?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually this is also no longer valid, I've reworked self-validation to work in the same way as the other validation

Copy link
Contributor

@rpuch rpuch May 23, 2022

Choose a reason for hiding this comment

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

It could make diagnostics a bit easier by adding some context: not just 'why it failed', but also 'what failed'.

Collection<String> cmgNodeNames,
String clusterName
) {
if (metaStorageNodeNames.isEmpty()) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Please check my comment about params validation in IgnitionManager.

@sashapolo sashapolo force-pushed the ignite-16717 branch 3 times, most recently from 3d40358 to 993ee6d Compare May 22, 2022 12:11
@sashapolo sashapolo force-pushed the ignite-16717 branch 2 times, most recently from 98e23c5 to 6b996f8 Compare May 22, 2022 15:51
@sanpwc sanpwc merged commit a136422 into apache:main May 24, 2022
@sanpwc sanpwc deleted the ignite-16717 branch May 24, 2022 11:29
isapego pushed a commit to isapego/ignite-3 that referenced this pull request Dec 26, 2024
GG-39353 Handle VacuumTxStatesCommand

---------

Co-authored-by: Kirill Sizov <sizov.kirill.y@gmail.com>
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.

3 participants