JanusGraph / JanusGraph/janusgraph
Add property value nullable constraint
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
We are allowed to add schema constraint that a property key must belong to the vertex that has specific vertex labels, can we add a new constraint that a property key must be present(cannot be null)? This will help to increase the data robust without adding extra detect in some cases(like User vertex must have a username). I think the rule of property key that is not nullable should be:
- If a property key belong to specific vertex labels or edge labels, all vertices and edes of those labels must be provided the property.
- If a property key doesn't belong to any specific vertex/edge labels, all vertices/edges in the graph must be provided the property.
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
No files, tests, or entry points are named. Start by reviewing the existing schema-constraint implementation and its tests to understand how label-specific and graph-wide property rules are represented. Done means enforcing non-null properties for the specified vertex or edge labels, or across the graph when no labels are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100