Hi All, I was facing the same issue where echo command was working but cat command was creating problem and locking the account due to extra $ character in password file. When you will cat the password file using -e option you will get an extra $ character at the end cat -e impala_passwd.pwd  = mypass1234$  extra $ is culprit. You need to remove it using tr command or create the file in windows using notepad put your password and tranfer it to the linux server and it shall work.   impala-shell -l --auth_creds_ok_in_clear --impalad=node2:21000 -u user1 --ldap_password_cmd='cat /home/user1/auto_impala.pwd' ... View more

Alex,   Thank you again.   Subquery approach has been recommended to our team as a long term solution. However, for short-tem solution to avoid regression impact, using view with limited partitions has been selected.   If I remember correctly, in MySQL `table A` data can be limited by `ON Clause` before joining so that cadidates for join can be reduced.   Thank you for your valuable comment. Gatsby ... View more

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

In that case, can you suggest a way to speed up the SSL communication with Impala ? Currently we are using Tableau to extract data from Impala. And with SSL activated, the data extraction is at least 30x to 100x slower than before. Did you see this behavior ? Do you have a remedy for it ? Thanks in advance. ... View more

That was it, thank you!   yum repo file was pointing to the old Cloudera Manager repo. After fixin the yum repo file and 'yum update' with refreshing CM on all nodes, problem was solved.   I am using packages not parcels. ... View more

Henry,   Thanks for the info.   Morgan ... View more

Hi I had the same issue , I have to make each statement in SQL file to be impala-shell -q *. Even it can work but I think it is so ugly and will be disaster when you have lots of statements !   I had raised the issue at this post before :   http://community.cloudera.com/t5/Interactive-Short-cycle-SQL/Impala-schedule-with-oozie-tutorial/m-p/24604#M727 ... View more

Hi Sreeman -    You're right, this is unrelated to Kerberos. The Impala shell is able to detect a Kerberos ticket in the cache, and tries to authenticate using that even though Kerberos isn't specified on the remote host. I think this is probably a bug if a separate kind of authentication (i.e. LDAP) is specified.   What's probably happening is that the password you are typing is not recognised for the user. The reason for that with LDAP is usually that the userid you're trying isn't actually the userid present in the LDAP database. For example, many deployments require usernames in the form user@DOMAIN.COM.   In Impala 1.4, there are options to map short userids onto the longer strings that an LDAP server requires. See http://www.cloudera.com/content/cloudera-content/cloudera-docs/Impala/latest/Installing-and-Using-Impala/ciiu_ldap.html, under "Support for custom bind strings".    Best, Henry ... View more