Skip to content

Fix incorrect delete version on update#7303

Merged
agourlay merged 1 commit intodevfrom
fix-delete-without-version
Sep 25, 2025
Merged

Fix incorrect delete version on update#7303
agourlay merged 1 commit intodevfrom
fix-delete-without-version

Conversation

@agourlay
Copy link
Member

@agourlay agourlay commented Sep 24, 2025

Removing the reverse proxy traversal introduced in https://github.com/qdrant/qdrant/pull/7248/files#r2344371758 happened to trigger one of the new assertion from #7300

"Overriding deleted flag ProxyDeletedPoint { local_version: 2443, operation_version: 2443 } with older op_num:0"

Tracking the version I found that it was synthetic to replace the absent value.

@agourlay agourlay force-pushed the fix-delete-without-version branch from 691a75f to facfe31 Compare September 24, 2025 15:43
@agourlay agourlay marked this pull request as ready for review September 25, 2025 08:59
@agourlay agourlay merged commit beaea63 into dev Sep 25, 2025
16 checks passed
@agourlay agourlay deleted the fix-delete-without-version branch September 25, 2025 09:02
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 25, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Changes in lib/shard/src/segment_holder/mod.rs adjust deletion and proxy-apply behavior. In apply_points, deletion of points now occurs only if a concrete version (Some(version)) is returned; deletions are skipped when no version exists. In proxy_all_segments_and_apply, the reversal of the proxies vector before iteration was removed, changing the order in which proxies are processed during the apply/unproxy phase.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • generall
✨ Finishing touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix-delete-without-version

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bf8e86f and facfe31.

📒 Files selected for processing (1)
  • lib/shard/src/segment_holder/mod.rs (2 hunks)

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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