Numerical VPack Sorting test#511
Closed
MDAlFattah wants to merge 15 commits intomainfrom
Closed
Conversation
7 tasks
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope & Purpose
This PR adds a test for validating VPack numerical sorting in ArangoDB, specifically addressing sorting behavior for large numeric values across different versions.
Problem
Large numeric values were previously cast to doubles for comparison, leading to incorrect sorting and potential data corruption in RocksDB. The issue is fixed in versions 3.12.2 and 3.11.11, introducing a new comparator that requires migration for proper sorting.
Test Script
Insert Test Data: Add documents with large numeric values to test collections.
Initial Sorting Check:
We now compare against both 3.11.11 and 3.12.2.
For versions older than 3.11.11: Use the incorrect sorting order (z, x, y).
For versions between 3.11.11 and 3.12.2: Still use the incorrect sorting order (z, x, y).
For versions 3.12.2 and newer: Use the correct sorting order (y, z, x).
Upgrade & Migration: Upgrade ArangoDB, run the migration, and verify sorting changes.
Final Check: Ensure correct sorting and data integrity after migration.
Checklist