Skip to content

IGNITE-22800 Make field BplusTree#globalRmvId monotonically increasing to avoid errors after node recovery#4131

Merged
tkalkirill merged 3 commits intoapache:mainfrom
gridgain:ignite-22800
Jul 24, 2024
Merged

IGNITE-22800 Make field BplusTree#globalRmvId monotonically increasing to avoid errors after node recovery#4131
tkalkirill merged 3 commits intoapache:mainfrom
gridgain:ignite-22800

Conversation

@tkalkirill
Copy link
Copy Markdown
Contributor

https://issues.apache.org/jira/browse/IGNITE-22800

Thank you for submitting the pull request.

To streamline the review process of the patch and ensure better code quality
we ask both an author and a reviewer to verify the following:

The Review Checklist

  • Formal criteria: TC status, codestyle, mandatory documentation. Also make sure to complete the following:
    - 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 description of the JIRA ticket explains WHAT was made, WHY and 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.
  • Design: new code conforms with the design principles of the components it is added to.
  • Patch quality: patch cannot be split into smaller pieces, its size must be reasonable.
  • Code quality: code is clean and readable, necessary developer documentation is added if needed.
  • Tests code quality: test set covers positive/negative scenarios, happy/edge cases. Tests are effective in terms of execution time and resources.

Notes

Copy link
Copy Markdown
Contributor

@ibessonov ibessonov left a comment

Choose a reason for hiding this comment

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

Looks good to me. Too many unnecessary renames, but I don't want to argue about that anymore

public abstract DataRegion<?> dataRegion();

/** Returns storage engine for the table. */
public abstract AbstractPageMemoryStorageEngine engine();
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

protected maybe? Why would it be public.
Whatever you decide

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This method is used for example in package org.apache.ignite.internal.storage.pagememory.mv.

PersistentPageMemoryStorageEngineConfiguration engineConfig,
@InjectConfiguration("mock.profiles.default = {engine = \"aipersist\"}")
StorageConfiguration storageConfiguration
StorageConfiguration storageConfig
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It's strange that you've shortened this name. What motivated you?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

For consistency in fields configuration naming, previously there was only engineConfig, then they brought storageConfiguration, it confused me a little, I can do it in a separate task.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm fine with it being here

@tkalkirill tkalkirill merged commit 00467d1 into apache:main Jul 24, 2024
@tkalkirill tkalkirill deleted the ignite-22800 branch July 24, 2024 14:04
isapego pushed a commit to isapego/ignite-3 that referenced this pull request Aug 5, 2024
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.

2 participants