I've deployed hive.execution.engine=tez as the default on my secondary HDP cluster I find that hive cli interactive sessions where I do
still execute with Tez as shown in the Resource Manager applications view. Now this may make sense since it's connected a Tez session by that point but it's also misleading because the job progress output in the cli changes to look like MapReduce rather than Tez and the query time is increased from 8 to to 15-16 secs but still less than the 25-30+ secs I usually see with MR. The Resource Manager shows both of these jobs as TEZ application type regardless of setting hive.execution.engine=mr. Is this a bug in the way Hive is submitting the job (Tez vs MR) or a bug in the way the RM is reporting it?
If I exit hive shell and restart it instead using
to set before session is established then it does a proper MapReduce job according to RM and it also takes the longer expected 25 secs instead of the 8 in Tez or 15 in trying to do MR instead Tez session.