After debugging a scans missing data issue while migrating to 0.98 (thanks Andrew, Jonathon, Josh, and Lars for the help), I'm left wondering why we have both caching and maxResultSize for scans. It seems to be more client api complexity than it's worth. Why would someone need to set caching when maxResultSize is available? Indeed, the first patch proposed by some fellow in HBASE-1996 simply replaced caching with maxResultSize. Can we deprecate and eventually remove caching? Is there a good case for keeping it in the client API surface?
Dave
