You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Hai Lu (Jira)" <ji...@apache.org> on 2019/11/07 00:06:03 UTC

[jira] [Updated] (SAMZA-2245) jar file not exists on JAVA_HOME/bin in some environment

     [ https://issues.apache.org/jira/browse/SAMZA-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hai Lu updated SAMZA-2245:
--------------------------
    Fix Version/s: 1.3

> jar file not exists on JAVA_HOME/bin in some environment
> --------------------------------------------------------
>
>                 Key: SAMZA-2245
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2245
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Hai Lu
>            Assignee: Hai Lu
>            Priority: Minor
>             Fix For: 1.3
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Samza 1.1.0 on AWS EMR (emr - 5.13.0, amazon 2.8.3, zookeeper 3.4.10) not working because run-class.sh assumes if JAVA_HOME is defined, jar exists under $JAVA_HOME/bin. This turns out not the case.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)