imbajin opened a new pull request, #3342:
URL: https://github.com/apache/hugegraph/pull/3342

   ## Purpose of the PR
   
   Concurrent Kout traversal can return fewer vertices than were read from 
storage. Workers share a non-thread-safe IdSet: a two-hop request that should 
include `peter`, `ripple` and `josh` returned only two results in the HStore 
API job.
   
   ## Main Changes
   
   Serialize each consumer's result insertion, distinct-result limit check and 
count update. Storage reads retain their existing parallelism. Add regressions 
for numeric/string IDs, duplicates, limits and nearest-layer behavior.
   
   Related failure: [HStore API 
job](https://github.com/hugegraph/hugegraph/actions/runs/38495465848/job/115630518111).
   
   ## Verifying these changes
   
   - [ ] Trivial rework / code cleanup without any test coverage. (No Need)
   - [ ] Already covered by existing tests.
   - [x] Need tests and can be verified as follows:
     - Actual consumer regressions reproduce lost/corrupt results before the 
fix and pass afterward; related traversal, collection and worker tests pass.
     - Java 17 clean compilation and source formatting pass.
     - The controlled Kout fixture exercises layer semantics; real HStore API 
validation is still pending the current-head CI run.
   
   ## Does this PR potentially affect the following parts?
   
   - [ ] Dependencies
   - [ ] Modify configurations
   - [ ] The public API
   - [x] Other affects: internal traversal result synchronization
   - [ ] Nope
   
   ## Documentation Status
   
   - [ ] `Doc - TODO`: required documentation is pending; complete it before 
merging.
   - [ ] `Doc - Done`: documentation is included here or linked below.
   - [x] `Doc - No Need`: internal correctness fix; no public API, 
configuration or persistence-format change.
   
   Documentation files in this PR or paired hugegraph-doc PR:
   
   Paired source PR: https://github.com/hugegraph/hugegraph/pull/313
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to