Skip to content

Comments

[ENH] Delete version files in GC.#4068

Merged
rohitcpbot merged 3 commits intomainfrom
rcp/CleanupVersionFiles
Mar 31, 2025
Merged

[ENH] Delete version files in GC.#4068
rohitcpbot merged 3 commits intomainfrom
rcp/CleanupVersionFiles

Conversation

@rohitcpbot
Copy link
Contributor

Description of changes

Summarize the changes made by this PR.

  • Improvements & Bug fixes
    • Delete version files as part of GC. SysDb creates new version file at every compaction since version files are immutable. Clean up these extra version files.
  • New functionality
    • ...

Test plan

How are these changes tested?

  • Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

SysDb create new version file at every compaction since
version files are immutable.
Clean up the extra version files.
@github-actions
Copy link

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

@rohitcpbot rohitcpbot requested a review from codetheweb March 28, 2025 18:01
.iter()
.filter(|v| versions_to_delete.contains(&v.version))
.filter_map(|v| {
if !v.version_file_name.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.

should there be a check here to assert that the files have been marked for removal?

@rohitcpbot rohitcpbot merged commit d041d53 into main Mar 31, 2025
95 checks passed
@rohitcpbot rohitcpbot deleted the rcp/CleanupVersionFiles branch March 31, 2025 17:10
codetheweb added a commit that referenced this pull request Mar 31, 2025
…d for deletion (#4120)

## Description of changes

Does what it says on the tin.

Addresses the comment here:
#4068 (comment)

## Test plan
*How are these changes tested?*

- [x] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

Added a test to cover the change.

## Documentation Changes
*Are all docstrings for user-facing APIs updated if required? Do we need
to make documentation changes in the [docs
repository](https://github.com/chroma-core/docs)?*

n/a
Inventrohyder pushed a commit to Inventrohyder/chroma that referenced this pull request Aug 5, 2025
## Description of changes

*Summarize the changes made by this PR.*
 - Improvements & Bug fixes
- Delete version files as part of GC. SysDb creates new version file at
every compaction since version files are immutable. Clean up these extra
version files.
 - New functionality
   - ...

## Test plan
*How are these changes tested?*

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

## Documentation Changes
*Are all docstrings for user-facing APIs updated if required? Do we need
to make documentation changes in the [docs
repository](https://github.com/chroma-core/docs)?*
Inventrohyder pushed a commit to Inventrohyder/chroma that referenced this pull request Aug 5, 2025
…d for deletion (chroma-core#4120)

## Description of changes

Does what it says on the tin.

Addresses the comment here:
chroma-core#4068 (comment)

## Test plan
*How are these changes tested?*

- [x] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

Added a test to cover the change.

## Documentation Changes
*Are all docstrings for user-facing APIs updated if required? Do we need
to make documentation changes in the [docs
repository](https://github.com/chroma-core/docs)?*

n/a
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