apache / apache/accumulo

Explore moving `Scanner.setBatchSize()` to `ScannerBase`

Open
#2,402 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
1.2k
Forks
487
Avg merge
4d 5h
Merged PRs (30d)
13

Description

**Is your feature request related to a problem? Please describe.**
BatchScanner has very few options for controlling the amount of data retrieved. Propose moving setBatchSize to ScannerBase to allow for this configuration option to be applied to BatchScanners as well as scanners.

**Describe the solution you'd like**
Move `Scanner.setBatchSize()` to `ScannerBase`

**Additional context**
This ticket is based off of Jira ticket [ACCUMULO-2001](https://issues.apache.org/jira/browse/ACCUMULO-2001). It was also mentioned on the ticket:

> Before moving to a common base class, the naming of this method should be reconsidered... as the "Batch" in "BatchScanner" (requests are batched, according to the hosting tserver) means something completely different than the "Batch" in "setBatchSize" (results are fetched in batches).

Contributor guide

Open the contributing guide

Research direction

Start by reading the Scanner.setBatchSize() API and the ScannerBase and BatchScanner abstractions mentioned in the issue. Trace how scanner configuration is represented and review the naming concern before deciding on the common API; done means the option is available to both scanner types with agreed terminology and relevant API behavior verified.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.