spring-projects / spring-projects/spring-data-elasticsearch
BulkProcessor feature in Spring Data Elasticsearch
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 1.3k
- Avg merge
- 1m
- Merged PRs (30d)
- 4
Description
From the discussion in thread 2067, there is no BulkProcessor equivalent implementation in Spring data elastic search.
The BulkProcessor simplifies the usage of the Bulk API by providing a utility class that allows index/update/delete operations to be transparently executed as they are added to the processor and this feature helps anyone who wants to bulk index documents efficiently.
Please consider this issue as feature request.
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 discussion in issue 2067 and the Elasticsearch BulkProcessor documentation linked in this issue. Determine how a BulkProcessor equivalent should fit Spring Data Elasticsearch and which index, update, and delete operations it must support. Done means a reviewed feature design and implementation that provides transparent bulk execution for queued operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, java
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100