imbajin opened a new issue, #3180:
URL: https://github.com/apache/hugegraph/issues/3180

   ### Problem
   
   The HStore core-test lane intermittently fails:
   
   ```text
   VertexCoreTest.testQueryByJointIndexesWithSearchAndTwoRangeIndexesAndWithin
   expected:<3> but was:<1>
   ```
   
   The query combines:
   
   - a range index on `type`;
   - a range index with `P.within(...)` on `confirmType`;
   - a search index with `Text.contains("诚信")` on `name`.
   
   Four vertices are inserted and three should match, but the HStore path 
sometimes returns only one.
   
   ### Repeated evidence
   
   The same assertion failed on multiple independent `master` pushes:
   
   - [run 
33256851831](https://github.com/apache/hugegraph/actions/runs/33256851831), 
head `321ba4dadad7bd37b8c659cdec34b056912d34b8`
   - [run 
33302137810](https://github.com/apache/hugegraph/actions/runs/33302137810), 
head `90035b6e6339572cca2fe1bafd5242b1c300e0ea`
   - [run 
33323387889](https://github.com/apache/hugegraph/actions/runs/33323387889), 
head `7bb624b99dc12c948cd62736ae26583a05195da1`
   - [run 
33324047387](https://github.com/apache/hugegraph/actions/runs/33324047387), 
head `8e167c7b1ac84194be3336426dea5a2448269016`
   
   It also failed identically on unrelated Compose-only PR #3149:
   
   - [run 
33361165253](https://github.com/apache/hugegraph/actions/runs/33361165253), 
head `a02886c688c33c1b114d8f21a3eac55aa83709d7`
   - [run 
33366079555](https://github.com/apache/hugegraph/actions/runs/33366079555), 
head `9cf8de7334db64743d9a21852077caf79734a040`
   
   Other runs on the same PR branch passed, including heads `aa3238821` and 
`6d56b0381`, so the failure is intermittent rather than tied to one Compose 
change.
   
   ### Why this is independent of PR #3149
   
   PR #3149 changes only Docker Compose, Hubble configuration/documentation, 
the Compose test script, the Server Docker entrypoint, and its focused 
entrypoint test. It does not change:
   
   - `VertexCoreTest`;
   - graph index query/intersection logic;
   - HStore scan, partition, merge, or ordering code.
   
   Most importantly, the exact PR base SHA `8e167c7b1` failed with the same 
method and result on a direct `master` push.
   
   ### History
   
   The failing test was introduced by PR #1803, commit 
`1f5d502e0e98bab6c8037cff9eeacc5dc2063715`, on 2022-04-19:
   
   - [PR #1803: fix query by within + 
Text.contains](https://github.com/apache/hugegraph/pull/1803)
   
   It was later moved with the repository/module restructuring; it was not 
added by PR #3149.
   
   A useful recent bisect boundary is PR #3140, merged as 
`2ae73704cdc5988127613c919ee7bb23d2568be7` on 2026-08-26:
   
   - [PR #3140: preserve range-index ordering across 
partitions](https://github.com/apache/hugegraph/pull/3140)
   
   PR #3140 changes related HStore multi-partition scan/merge/order code and 
adds coverage around it. Its own HStore CI passed, so this is investigation 
context only, not evidence that #3140 is the root cause. The first observed 
repeated failures above occur after that merge.
   
   ### Reproduction
   
   The CI lane runs:
   
   ```bash
   mvn test -pl hugegraph-server/hugegraph-test -am -P core-test,hstore
   ```
   
   A focused repeated run should target:
   
   ```text
   VertexCoreTest#testQueryByJointIndexesWithSearchAndTwoRangeIndexesAndWithin
   ```
   
   ### Suggested investigation
   
   1. Re-run the focused test repeatedly against HStore and record pass/fail 
frequency.
   2. Log the candidate IDs returned by each range/search index before 
intersection.
   3. Log per-partition scan results and the final ordered merge.
   4. Compare behavior immediately before and after `2ae73704c`.
   5. Confirm whether one partition/result stream is being dropped or 
terminated early.
   
   ### Expected behavior
   
   The first query consistently returns three vertices on every backend and 
every run.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to