JanusGraph / JanusGraph/janusgraph
hbase ttl does not take effect totally
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
by setting ttl as followed:
JanusgraphSchemaType user = mgmt.makeVertexLabel("user").setStatic().make();
mgmt.setTTL(user, Duration.ofMinutes(5));
After writing data into janusgraph continually about 10 minutes, i start to observe the data in hbase and find some data removed indeedly, but there is always some data that can not be removed automaticly after long time .
ps:
i add the item in my configure file: graph.timestamps=MILLI
Contributor 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.
Research direction
Start by tracing the TTL setup through mgmt.setTTL(user, Duration.ofMinutes(5)) and the graph.timestamps=MILLI configuration, then compare those settings with the HBase data observed after ten minutes. Reproduce the report that some data is removed while other data remains, and define done as identifying and correcting the cause of incomplete expiration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100