Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Abandoned
-
None
-
None
-
None
-
None
Description
The Scan API exposes a maxResultSize to the application. The max result size is used to determine how large the chunks sent back per RPC request should be. This seems like a configuration that should not be present in the public API used by the application but rather a detail that the server should control instead. In a situation where there are multiple concurrent scans being issued against a single region server, it would seem more appropriate to give the server control over this parameter so that it could be optimized against the current load. This issue proposes that the max result size be deprecated in 2.0.0 so that future optimizations could be made to the way that Scan RPC requests are handled by the server. Of course if there are any concerns please raise them here.