JanusGraph / JanusGraph/janusgraph
Refactor schema and index management to have unique interface
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
**Describe the feature:**
Currently, our schema and management has no clean interface. It would be good clean up the interface. We see a lot of users that having problems with our schema management or index management.
**Describe a specific use case for the feature:**
* unique interface
* index status (enable of a index)
* manage from a driver
---
Current state:
- [x] Get Vertices #2527 and #2560
- [ ] ttl
- [x] static
- [x] partition
- [x] Get Vertex Properties #2940
- [ ] ttl
- [x] Get Edge #2548 and #2560
- [ ] ttl
- [x] Get Edge Properties #2995
- [ ] ttl
- [ ] Get Composite Index
- [ ] vertex #3011
- [ ] Get Mixed Index
- [ ] Get Vertex centric index
---
Start with writing
- [ ] Create Vertex
- [ ] Create Vertex Properties
- [ ] Create Edge
- [ ] Create Edge Properties
- [ ] Create Composite Index
- [ ] Create Mixed Index
- [ ] Create Vertex centric index
- [ ] Update Vertex
- [ ] Update Vertex Properties
- [ ] Update Edge
- [ ] Update Edge Properties
- [ ] Update Composite Index
- [ ] Update Mixed Index
- [ ] Update Vertex centric index
---
Other funcs:
- [ ] reindex
- [ ] config management
- [ ] multi graph management
Contributor guide
Research direction
Start by auditing the existing schema, index, driver, configuration, and multi-graph management interfaces against the checklist in this issue. No files or tests are named, so first locate the relevant APIs and determine the intended common operations; done requires an agreed scope and consistent interfaces for the selected schema and index management tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100