[
https://issues.apache.org/jira/browse/IMPALA-14450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021490#comment-18021490
]
ASF subversion and git services commented on IMPALA-14450:
----------------------------------------------------------
Commit 8a80ede69b6bdcd10701f16cc014d028c3b3729e in impala's branch
refs/heads/master from Michael Smith
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=8a80ede69 ]
IMPALA-14450: (Addendum) Fix numeric comparison
Fix shell comparison to use string equality so it works for all POSIX
shells instead of just zsh.
Change-Id: If9b9ed7f59e71d024ec674bb30c57274567fb2a3
Reviewed-on: http://gerrit.cloudera.org:8080/23444
Reviewed-by: Joe McDonnell <[email protected]>
Tested-by: Michael Smith <[email protected]>
> Cannot manually set both JAVA_HOME and IMPALA_JAVA_TARGET
> ---------------------------------------------------------
>
> Key: IMPALA-14450
> URL: https://issues.apache.org/jira/browse/IMPALA-14450
> Project: IMPALA
> Issue Type: Task
> Components: Frontend
> Affects Versions: Impala 5.0.0
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> As we work to support Java 17, a problem that's come up is that when you set
> {{IMPALA_JAVA_HOME_OVERRIDE}} to specify your own {{JAVA_HOME}}, it overrides
> {{IMPALA_JDK_VERSION}}. If you happen to source bin/impala-config.sh in the
> same shell, then {{IMPALA_JAVA_TARGET=override}} and compilation fails.
> In more specific environments with subshells, this isn't necessarily a
> problem until you try to provide {{IMPALA_JDK_VERSION}} as an environment
> variable. By declaring the environment variable, the update
> {{IMPALA_JDK_VERSION=override}} escapes the subshell and breaks subsequent
> build steps.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
