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

Storage mover port (#2039) #2127

Merged
merged 2 commits into from
Jan 17, 2025

Conversation

vasil-pashov
Copy link
Collaborator

Add the StorageMover class from arcticc. Some changes in the implementation of the StorageMover were needed as
batch_read_compressed used to return not only the keys but the segments as well. In the current ArcticDB version the segment is passed as continuation and that required keeping additional vector where the segments themselves are stored.
Make sure all unit tests are passing.
No changes to the API are done.
Note in arcticc it was in the tools module while here it's in the toolbox module.

Checklist for code changes...
  • Have you updated the relevant docstrings, documentation and copyright notice?
  • Is this contribution tested against all ArcticDB's features?
  • Do all exceptions introduced raise appropriate error messages?
  • Are API changes highlighted in the PR description?
  • Is the PR labelled as enhancement or bug so it appears in autogenerated release notes?

Reference Issues/PRs

What does this implement or fix?

Any other comments?

Checklist

Checklist for code changes...
  • Have you updated the relevant docstrings, documentation and copyright notice?
  • Is this contribution tested against all ArcticDB's features?
  • Do all exceptions introduced raise appropriate error messages?
  • Are API changes highlighted in the PR description?
  • Is the PR labelled as enhancement or bug so it appears in autogenerated release notes?

<!--Example: Fixes #1234. See also #3456.-->
Add the StorageMover class from arcticc. Some changes in the
implementation of the StorageMover were needed as
`batch_read_compressed` used to return not only the keys but the
segments as well. In the current ArcticDB version the segment is passed
as continuation and that required keeping additional vector where the
segments themselves are stored.
Make sure all unit tests are passing.
No changes to the API are done.
Note in arcticc it was in the tools module while here it's in the
toolbox module.

<details>
  <summary>
   Checklist for code changes...
  </summary>

- [ ] Have you updated the relevant docstrings, documentation and
copyright notice?
- [ ] Is this contribution tested against [all ArcticDB's
features](../docs/mkdocs/docs/technical/contributing.md)?
- [ ] Do all exceptions introduced raise appropriate [error
messages](https://docs.arcticdb.io/error_messages/)?
 - [ ] Are API changes highlighted in the PR description?
- [ ] Is the PR labelled as enhancement or bug so it appears in
autogenerated release notes?
</details>

<!--
Thanks for contributing a Pull Request to ArcticDB! Please ensure you
have taken a look at:
- ArcticDB's Code of Conduct:
https://github.com/man-group/ArcticDB/blob/master/CODE_OF_CONDUCT.md
- ArcticDB's Contribution Licensing:
https://github.com/man-group/ArcticDB/blob/master/docs/mkdocs/docs/technical/contributing.md#contribution-licensing
-->
@vasil-pashov vasil-pashov merged commit 41c373c into 5.1.x Jan 17, 2025
119 of 120 checks passed
@vasil-pashov vasil-pashov deleted the vasil.pashov/storage-mover-5.1.x-cherry-pick branch January 17, 2025 15:14
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