[HIVE-11342] JDBC driver not using setMaxRows to avoid running job

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2.0
• Assignee: Unassigned
• Reporter: Adam Silberstein
• Created: 22/Jul/15 16:34
• Updated: 22/Jul/15 16:34

Description

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.