Adam Silberstein created HIVE-11342:
---------------------------------------
Summary: JDBC driver not using setMaxRows to avoid running job
Key: HIVE-11342
URL: https://issues.apache.org/jira/browse/HIVE-11342
Project: Hive
Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Adam Silberstein
When using the Hive JDBC driver to run 'select *' and using setMaxRows() to set
a limit, Hive will still kick off a batch job (m/r in my case). Not sure if
the limit would eventually be applied post job, my application timed out before
checking that.
This is in contrast to running a query like 'select * limit 100000, which
avoids the job no matter what the limit.
The difference can be seen in the hive-server2 log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
