JanusGraph / JanusGraph/janusgraph

JanusGraph query empty result restart

Open
#4,824 1 comment 0 reactions 0 assignees View on GitHub
kind/bug/possible
Dominant language
Java
Stars
5.8k
Forks
1.2k
Avg merge
13h 53m
Merged PRs (30d)
6

Description

Please include configurations and logs if available.

For confirmed bugs, please report:

- Version:
- Storage Backend:
- Mixed Index Backend:
- Link to discussed bug:
- Expected Behavior:
- Current Behavior:
- Steps to Reproduce:

### Stack Trace (if you have one)

```
我使用的0.5的版本,我现在用如下的语句去查询janusgraph数据,第二条、第三条、第四条都可以查到记录,但是第一条查询结果就为空,如果我把gremlin server重启一下,这四条语句的查询结果就符合预期,你觉得我应该从哪些方面着手定位?```
[g.V().hasLabel('card').has('msisdncard','13088888888').as('a').outE('usedby').has('capturetime](https://github.com/JanusGraph/janusgraph/g.V().hasLabel('card').has('msisdncard','13088888888').as('a').outE('usedby').has('capturetime)', gte(1751990400)).has('capturetime', lte(1752595199)).otherV().hasLabel('phone').as('b').tree()

[g.V().hasLabel('card').has('msisdncard','13088888888').as('a').outE('usedby').has('capturetime](https://github.com/JanusGraph/janusgraph/g.V().hasLabel('card').has('msisdncard','13088888888').as('a').outE('usedby').has('capturetime)', gte(1752508800)).has('capturetime', lte(1752595199)).otherV().hasLabel('phone').as('b').tree()

[g.V().hasLabel('card').has('msisdncard','13088888888').as('a').outE('usedby').has('capturetime](https://github.com/JanusGraph/janusgraph/g.V().hasLabel('card').has('msisdncard','13088888888').as('a').outE('usedby').has('capturetime)', gte(1751904000)).has('capturetime', lte(1752595199)).otherV().hasLabel('phone').as('b').tree()

[g.V().hasLabel('card').has('msisdncard','13088888888').as('a').outE('usedby').has('capturetime](https://github.com/JanusGraph/janusgraph/g.V().hasLabel('card').has('msisdncard','13088888888').as('a').outE('usedby').has('capturetime)', gte(1752076800)).has('capturetime', lte(1752595199)).otherV().hasLabel('phone').as('b').tree()```
```

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the reported version, storage backend, mixed-index backend, query examples, and the requested configuration and logs. Reproduce the empty first result before and after restarting the Gremlin server, then document confirmed expected and current behavior with complete steps and diagnostics; the issue names no repository files or tests.

Written by the indexing model from the issue text.

Assessment

Domain
databases, distributed-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.