orientechnologies / orientechnologies/orientdb
Make Lucene indexes durable
Open
@wolf4ood is already working on this.
Since Oct 1, 2019.
enhancement
- Dominant language
- Java
- Stars
- 5k
- Forks
- 868
- Avg merge
- 15h 6m
- Merged PRs (30d)
- 18
Description
- Each Lucene operation has a sequential number.
- Once Lucene commit is called commit method returns sequential number which indicates latest committed operation.
We should map those data and implement mechanics to restore data in Lucene after a server crash. Especially taking into account that if we implement data structures which are "durable without WAL" they probably will use similar mechanics.
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.
Assessment
This issue has not been assessed yet.