JanusGraph / JanusGraph/janusgraph
Mixed solr index sometimes removes multivalued property when it shouldn't.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
If I in one transaction on a vertex delete values in a property with cardinality SET and a property with cardinality SINGLE, I experience that the property with cardinality SET, get's incorrect/wiped out from the external solr index 20% of the time. The stored property in cassandra is correct. I made me a test to verify. In the discussion below there is test code to reproduce and @li-boxuan managed todo so.
- Version: 0.5.3
- Storage Backend: cassandra
- Mixed Index Backend: solr
- Link to discussed bug: https://github.com/JanusGraph/janusgraph/discussions/2422#discussioncomment-341060
- Expected Behavior: The multivalued property should be indexed correct
- Current Behavior: In about 20% of the cases, the multivalued property is removed from solr
- Steps to Reproduce: Se discussion
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 with the reproduction test code in the linked discussion and investigate the Cassandra-to-Solr mixed-index transaction path for updates involving SET and SINGLE properties. Run the reproduction repeatedly; done means the SET property remains correctly indexed in every case while Cassandra remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cassandra, java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100