Skip to content

[Issue #1319] Fix RocksDB prefix seek for versioned index keys#1320

Open
AntiO2 wants to merge 2 commits intopixelsdb:masterfrom
AntiO2:codex/rocksdb-prefix-fix
Open

[Issue #1319] Fix RocksDB prefix seek for versioned index keys#1320
AntiO2 wants to merge 2 commits intopixelsdb:masterfrom
AntiO2:codex/rocksdb-prefix-fix

Conversation

@AntiO2
Copy link
Copy Markdown
Collaborator

@AntiO2 AntiO2 commented Apr 28, 2026

No description provided.

bianhq
bianhq previously approved these changes Apr 29, 2026
Copy link
Copy Markdown
Contributor

@bianhq bianhq left a comment

Choose a reason for hiding this comment

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

LGTM.

@bianhq bianhq added the bug Something isn't working label Apr 29, 2026
@bianhq bianhq added this to the Real-time CRUD milestone Apr 29, 2026
@bianhq bianhq linked an issue Apr 29, 2026 that may be closed by this pull request
Validate prefix seek correctly lands on the closest stored version across
multiple timestamp scenarios. Tune prefix length and enable multiCF to
support multi-column-family index lookup.
@AntiO2
Copy link
Copy Markdown
Collaborator Author

AntiO2 commented May 1, 2026

@bianhq Confirmed seek correctness when the prefix covers only the index key (excluding the encoded timestamp suffix).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[pixels-index] Fix RocksDB prefix seek

2 participants