[
https://issues.apache.org/jira/browse/PIO-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902295#comment-15902295
]
ASF GitHub Bot commented on PIO-51:
-----------------------------------
GitHub user chanlee514 opened a pull request:
https://github.com/apache/incubator-predictionio/pull/357
[PIO-51] Properly locate engine directory
When --engine-dir is passed as CLI argument, use this instead of
user.dir
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chanlee514/incubator-predictionio
hotfix/engine-dir
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-predictionio/pull/357.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #357
----
commit 39ff8ac727723b3926b30bd19506fba2fba5e251
Author: Chan Lee <[email protected]>
Date: 2017-03-09T01:38:26Z
[PIO-51] Properly locate engine directory
When --engine-dir is passed as CLI argument, use this instead of
user.dir
----
> Enable `pio build/train/deploy` outside of engine directory
> -----------------------------------------------------------
>
> Key: PIO-51
> URL: https://issues.apache.org/jira/browse/PIO-51
> Project: PredictionIO
> Issue Type: Improvement
> Reporter: Chan
> Assignee: Chan
> Fix For: 0.11.0
>
>
> Users can now provide the engine directory path as —engine-dir or -ed, and
> call `pio build/train/deploy` from anywhere.
> The “engineVersion” used to identify a prediction engine is created using the
> hash of the engine directory path. As a result, the filepath of the engine
> had to be kept the same in a distributed setup, with multiple machines using
> the same trained model. This was a point of confusion for some users, which
> led to this change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
