SebastianGruza commented on PR #2994: URL: https://github.com/apache/hugegraph/pull/2994#issuecomment-5598355540
**Correction to my comment of 2026-09-08**: the observation about `HasStep(lambda)` on rocksdb "with the same build" was my mistake, not a property of the PR. The rocksdb server in that run was still on the `fefe3ca` core jar (my dist-assembly script died before copying the rocksdb dist). The hstore columns and the master baseline of that report stand, the rocksdb columns do not; the report now carries an erratum and the cycle script refuses to run on a jar mismatch. Sorry for the noise. **`2d53a55` measured with verified dists**, report under [tag `pr-2994-2026-09-09`](https://github.com/SebastianGruza/hugegraph-validation/blob/pr-2994-2026-09-09/reports/pr-2994/2d53a55/README.md). `explain()` plans are now identical on hstore and rocksdb for all 27 shapes, the result sets of all 133 J8 shapes as well; the suite is unchanged. On the two notes of @bitflicker64 from 2026-09-08: - Positive label before an unsafe child, 1 M vertices: `g.V().hasLabel('firm').where(__.out('deal').hasLabel(neq('person'))).count()` hstore 14 ms, rocksdb 6 ms (master 16 and 7 ms), plan `HugeGraphStep(Vertex,[~label.eq(firm)]), TraversalFilterStep([HugeVertexStep(OUT,[deal],vertex), HasStep([~label.neq(person)])])`; the `within('firm','robot')` and `has('type',gte(2))` variants (the property stays local next to the pushed label) are in the same range. The label-index lookup is back on both backends. - SEARCH analyzer in an unbound child: `g.V().hasLabel('firm').where(__.out('deal').has('fname',Text.contains('(gold)')).hasLabel(neq('person')))` returns 0 on master (literal substring, parentheses included) and 1 on this head; same for `Text.contains('(gold|silver)')`. On the source step both return 80, so the difference is exactly the path the document describes. From my side unchanged: nothing left to close before merging. -- 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]
