Cleanup the batch size and caching scanner flags #56

Closed
wbolster opened this Issue Jan 26, 2014 · 1 comment

Projects

None yet

1 participant

@wbolster
Owner

The current implementation mixes up these options affecting scanner behaviour and performance:

  • batch size for fetching frows, used between the Python process and the Thrift server
  • batch size passed as a scanner option, used between the Thrift server and region servers
  • caching size passed as a scanner option, also used between the Thrift server and region servers
@wbolster wbolster added a commit that referenced this issue Feb 25, 2014
@wbolster Revert "Allow batch_size=None in Table.scan() to avoid filter incompa…
…tibilities"

This reverts commit 8481d31, since it
is not a correct fix. See issue #56.
da109ab
@wbolster wbolster added a commit that referenced this issue Feb 25, 2014
@wbolster No longer confuse batching/caching; add Table.scan(scan_batching=...)
For details, see the comments added in this commit, and issues #54 and
issue #56.
106dcf0
@wbolster wbolster closed this Feb 25, 2014
@wbolster
Owner

Should be fixed in 0.8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment