[
https://issues.apache.org/jira/browse/IMPALA-8317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798226#comment-16798226
]
Fredy Wijaya commented on IMPALA-8317:
--------------------------------------
[~arodoni_cloudera] Yes, I don't think we have a doc for the config_file file
format. It's a good idea to also incorporate the changes in
https://issues.apache.org/jira/browse/IMPALA-8330.
> impala-shell's config_file should be parsed correctly for 'keyval'
> ------------------------------------------------------------------
>
> Key: IMPALA-8317
> URL: https://issues.apache.org/jira/browse/IMPALA-8317
> Project: IMPALA
> Issue Type: Bug
> Components: Clients
> Affects Versions: Impala 2.12.0, Impala 3.1.0
> Reporter: Vincent Tran
> Assignee: Fredy Wijaya
> Priority: Minor
> Fix For: Impala 3.3.0
>
>
> [root@kiwi-2 ~]# cat ~/.impalarc
> [impala]
> keyval=foo=customers
> [root@kiwi-2 ~]# impala-shell --ssl -q 'set'
> Starting Impala Shell without Kerberos authentication
> SSL is enabled. Impala server certificates will NOT be verified (set
> --ca_cert to change)
> {color:red}for keyval in keyvals:
> Tokenized keyval: "f"
> keyvals: "foo=customers"{color}
> Error: Could not parse key-value "f". It must follow the pattern "KEY=VALUE".
> Usage: impala_shell.py [options]
> It's apparent that the "KEY=VAL" string passed in is tokenized by characters
> here:
> https://github.com/apache/impala/blob/969dea84f41cfccf863b14904958a5d2be91983f/shell/impala_shell.py#L1512
> An immediate fix might be to cast options.keyval to an array
> ([options.keyval]):
> https://github.com/apache/impala/blob/969dea84f41cfccf863b14904958a5d2be91983f/shell/impala_shell.py#L1719
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
