Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/839
The right approach is not to simply allow HBase to use more memory. The
right approach is to limit memory.
Fortunately, another project is underway to do just that. Let's
collaborate. In the next week or so I'll do a PR for the framework to limit
batch sizes in readers, along with an implementation for the "compliant" text
readers.
Maybe you can use that framework to retrofit the HBase reader to also limit
it's batch size. Basically, we limit the length of the longest vector to 16 MB.
The present patch, using unlimited memory, has all kinds of other problems
-- the very problems we are trying to solve, so it is not helpful to move
forward in one area, backward in another.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
