You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Rogan Carr (JIRA)" <ji...@apache.org> on 2017/11/05 03:52:00 UTC
[jira] [Assigned] (REEF-1826) REEF Must be Invoked in a Directory
that Contains Its DLLs
[ https://issues.apache.org/jira/browse/REEF-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rogan Carr reassigned REEF-1826:
--------------------------------
Assignee: Rogan Carr
> REEF Must be Invoked in a Directory that Contains Its DLLs
> ----------------------------------------------------------
>
> Key: REEF-1826
> URL: https://issues.apache.org/jira/browse/REEF-1826
> Project: REEF
> Issue Type: Bug
> Components: REEF Client
> Affects Versions: 0.15
> Reporter: Shouheng Yi
> Assignee: Rogan Carr
> Priority: Minor
> Labels: patch
>
> I have an executable file (let's say {{foo.exe}}) that invokes REEF's client. {{foo.exe}} will not run, if REEF's DLLs are not in the current running directory.
> This constraint is fine if I'm working locally. However when I'm working on a cluster and try to deploy {{foo.exe}}, I have to create a process to extract all the DLLs to the current directory. This process creates some unwanted overhead.
> I'm wondering if we have any plan to fix this. In the future, it would be great if we can call REEF in a different directory. Thanks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)