Github user herval commented on the issue:
https://github.com/apache/zeppelin/pull/2428
@tinkoff-dwh it's not duplicate. The bug here is that if you don't do
`statement.setMaxRows`, some drivers (eg postgres) will try to load everything
when you issue a `select *`. Using `setFetchSize` won't affect that (I tested
it). So the solution I found is to set the limit to (fetch size + 1). There's a
function that will prune the results *after they're back from JDBC*
(`getResults`) - I'm guessing we could remove that, if all it did was checking
that limit, but don't think it's worth pursuing at this time.
TLDR - the current limit check is only applied _after_ you get results. If
you query a big enough table, you'll never get the results (and will kill
Zeppelin in the process)
---
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.
---
