Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
Impala 4.0.0
-
ghx-label-5
Description
When Ranger is enabled with no further authentication method configured and no user specified Impala throws IllegalArgumentException (see bellow).
Meanwhile, Hive JDBC replaces empty user with 'anonymous'. Although, without authentication any user can be impersonated and it is a rare use-case, we should consider substitute empty username for 'anonymous' as well for interoperability.
$ impala-shell --protocol='hs2-http' -i <hostname> --user '' -q 'describe tarmstrong.test' Starting Impala Shell without Kerberos authentication Warning: live_progress only applies to interactive shell sessions, and is being skipped for now. Warning: --connect_timeout_ms is currently ignored with HTTP transport. Opened TCP connection to coordinator-IBM-Think1.env-hg4zgx.apps.os4demo.cloudera.com:80 Connected to coordinator-IBM-Think1.env-hg4zgx.apps.os4demo.cloudera.com:80 Server version: impalad version 4.0.0-SNAPSHOT RELEASE (build e21fdec10f2f90d1ff6dab619d4dcb5626f458a8) Query: describe tarmstrong.test ERROR: IllegalArgumentException: Null user Could not execute command: describe tarmstrong.test Traceback (most recent call last): File "/home/tarmstrong/.local/bin/impala-shell", line 11, in <module> sys.exit(impala_shell_main()) File "/home/tarmstrong/.local/lib/python2.7/site-packages/impala_shell/impala_shell.py", line 1874, in impala_shell_main raise FatalShellException() impala_shell.impala_shell.FatalShellException
Attachments
Issue Links
- is related to
-
IMPALA-9486 Creating a Kudu table via JDBC fails with "IllegalArgumentException"
- Open