Cross-check the child stats of string columns against vortex-jni
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Read NodeStatsInteropIntegrationTest and docs/compatibility.md, especially the vortex.fsst notes. Identify the child stats for string columns and compare stat presence and precision per node, plus values that do not depend on the trained FSST table; use a low-cardinality column for dict codes. Done means the test covers these cases without comparing FSST-dependent values byte-for-byte.
Written by the indexing model from the issue text.
Description
Split from #583. NodeStatsInteropIntegrationTest compares every flat root and the whole tree of the numeric columns against vortex-jni, but not the children of string columns (FSST lengths and codes, dict values).
Their stat values depend on the trained FSST symbol table, which cannot be byte-identical to Rust's: candidates of equal gain pop in hash-map iteration order, which depends on the CPU's SIMD width (see docs/compatibility.md, vortex.fsst). A plain comparison would be flaky.
To do: compare the stat set per node (which stats are present, precision) rather than values where the table matters, and values where they do not (e.g. vortex.sequence offsets, dict codes of a low-cardinality column).
Parity directive: this is a test gap, not a known divergence.
- Dominant language
- Java
- Stars
- 3
- Forks
- 2
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 154
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dfa1/vortex-java
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dfa1/vortex-java#738 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dfa1/vortex-java#737 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dfa1/vortex-java#736 ·
Maintainers usually reply within 1 day
-
help wanted project
Difficulty 5/5 Over a week Newbie friendliness 25/100
dfa1/vortex-java#729 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 72/100
dfa1/vortex-java#728 ·
Maintainers usually reply within 1 day
All issues in dfa1/vortex-java
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 Under an hour Newbie friendliness 84/100
cpp-best-practices/project_validator#251 ·
Maintainers usually reply within 1 day
-
backend enhancement
Difficulty 2/5 Half a day Newbie friendliness 70/100
damodharg6/payledger#16 ·
-
[Bug]: An initiative list with no current entry logs an error on every changePossibly taken @dwizard0 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day