Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/19635
Hive is interesting. In older versions, it behaves like current Spark. But
in its current master branch the behavior is like after the patch:
```
0: jdbc:hive2://localhost:10000> select 'a' where 1 in ('01');
INFO : Compiling
command(queryId=root_20171106045740_254a2d60-ae1f-4851-b304-dfa18551fff2):
select 'a' where 1 in ('01')
INFO : Concurrency mode is disabled, not creating a lock manager
INFO : Semantic Analysis Completed
INFO : Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:_c0,
type:string, comment:null)], properties:null)
INFO : Completed compiling
command(queryId=root_20171106045740_254a2d60-ae1f-4851-b304-dfa18551fff2); Time
taken: 5.794 seconds
INFO : Concurrency mode is disabled, not creating a lock manager
INFO : Executing
command(queryId=root_20171106045740_254a2d60-ae1f-4851-b304-dfa18551fff2):
select 'a' where 1 in ('01')
INFO : Completed executing
command(queryId=root_20171106045740_254a2d60-ae1f-4851-b304-dfa18551fff2); Time
taken: 0.008 seconds
INFO : OK
+------+
| _c0 |
+------+
| a |
+------+
1 row selected (6.321 seconds)
0: jdbc:hive2://localhost:10000> select 'a' where 1 in (select '01' from
(select 1) dual);
INFO : Compiling
command(queryId=root_20171106045757_48e04001-bfbd-4557-9dd5-4e97674708ff):
select 'a' where 1 in (select '01' from (select 1) dual)
INFO : Concurrency mode is disabled, not creating a lock manager
INFO : Semantic Analysis Completed
INFO : Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:_c0,
type:string, comment:null)], properties:null)
INFO : Completed compiling
command(queryId=root_20171106045757_48e04001-bfbd-4557-9dd5-4e97674708ff); Time
taken: 0.869 seconds
INFO : Concurrency mode is disabled, not creating a lock manager
INFO : Executing
command(queryId=root_20171106045757_48e04001-bfbd-4557-9dd5-4e97674708ff):
select 'a' where 1 in (select '01' from (select 1) dual)
WARN : Hive-on-MR is deprecated in Hive 2 and may not be available in the
future versions. Consider using a different execution engine (i.e. spark, tez)
or using Hive 1.X releases.
INFO : Query ID = root_20171106045757_48e04001-bfbd-4557-9dd5-4e97674708ff
INFO : Total jobs = 1
INFO : Starting task [Stage-4:MAPREDLOCAL] in serial mode
INFO : Execution completed successfully
INFO : MapredLocal task succeeded
INFO : Launching Job 1 out of 1
INFO : Starting task [Stage-3:MAPRED] in serial mode
INFO : Number of reduce tasks is set to 0 since there's no reduce operator
WARN : Hadoop command-line option parsing not performed. Implement the
Tool interface and execute your application with ToolRunner to remedy this.
INFO : number of splits:1
INFO : Submitting tokens for job: job_1509962180830_0001
INFO : The url to track the job:
http://6edb04432864:8088/proxy/application_1509962180830_0001/
INFO : Starting Job = job_1509962180830_0001, Tracking URL =
http://6edb04432864:8088/proxy/application_1509962180830_0001/
INFO : Kill Command = /usr/local/hadoop/bin/hadoop job -kill
job_1509962180830_0001
INFO : Hadoop job information for Stage-3: number of mappers: 0; number of
reducers: 0
INFO : 2017-11-06 04:58:27,891 Stage-3 map = 0%, reduce = 0%
INFO : 2017-11-06 04:58:35,774 Stage-3 map = 100%, reduce = 0%
INFO : Ended Job = job_1509962180830_0001
INFO : MapReduce Jobs Launched:
INFO : Stage-Stage-3: HDFS Read: 0 HDFS Write: 0 SUCCESS
INFO : Total MapReduce CPU Time Spent: 0 msec
INFO : Completed executing
command(queryId=root_20171106045757_48e04001-bfbd-4557-9dd5-4e97674708ff); Time
taken: 37.367 seconds
INFO : OK
+------+
| _c0 |
+------+
| a |
+------+
1 row selected (38.501 seconds)
```
It looks like it has been fixed but I have not been able to find the
relevant JIRA ticket so far.
@gatorsmile should I check other databases?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
