You can create a 1-row dummy table like this:   select 1 id, 'a' d from (select 1) dual where 1 = 1   You also have to rewrite the query to avoid an uncorrelated not exists. You can do something like:   select 1 id, 'a' d from (select 1) dual where (select count(*) from employee where empid > 20000) = 0   Computing the count might be expensive so you could add a limit like   select 1 id, 'a' d from (select 1) dual where (select count(*) from (select id from employee where empid > 20000 limit 1) emp) = 0 ... View more

If the table is a large compressed text file, you're probably running into this issue: https://issues.cloudera.org/browse/IMPALA-2249 . We have a fix in newer versions of Impala to prevent the crash, but we don't support compressed text files of > 1GB for some compressed text file formats. ... View more

It would be helpful if you had the hs_err_pid*.log file that is mentioned in the error message.   What format is the auth table? Is there anything notable about the data? E.g. large strings. ... View more

The advice in this thread is out of date: memory usage for joins and aggregations has been improved a lot in CDH5.5.    Your issue is something different since the query doesn't have a join or group by (aggregation) in it.   The first step to understand this better is to look at the impalad logs: there is usually some information in there about why the memory limit was exceeded and what operators were consuming memory.   ... View more

It looks like your Impala's process memory limit is set to 1GB. Queries can't use more than the process memory limit, even if the query memory limit is set higher. To work around this you or your administrator need to restart impala with a higher process memory limit. 1GB is very low and you will run out of memory on many queries.   The process memory limit is set when impala is started with the -mem_limit option to impalad. The default is 80% of the machine's physical memory. The valid options are described in impalad --help   -mem_limit (Process memory limit specified as number of bytes ('<int>[bB]?'), megabytes ('<float>[mM]'), gigabytes ('<float>[gG]'), or percentage of the physical memory ('<int>%'). Defaults to bytes if no unit is given) type: string default: "80%"     ... View more

The table use the ORCFile format, which we don't support in Impala. We recommend using Parquet, which is supported by Hive, MapReduce, Impala and many other systems. ... View more