spring-projects / spring-projects/spring-data-mongodb

BulkOperations should add sharding keys to query

Open
#4,361 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: enhancement
Dominant language
Java
Stars
1.7k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

MonoTemplate replace/update operations add sharding information if possible to avoid unnecessary broadcasting to all shards and so should DefaultBulkOperations.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing MonoTemplate's replace/update operations with DefaultBulkOperations to identify how sharding information is added to queries. Confirm that bulk replace/update operations include available sharding keys and avoid broadcasting to all shards; the issue names no files or tests, so locating the relevant implementation and verification coverage is part of the work.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, mongodb, spring
Domain
databases, distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.