[
https://issues.apache.org/jira/browse/PIO-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838220#comment-15838220
]
Donald Szeto commented on PIO-51:
---------------------------------
I would say so, because engine manifests are now removed, {{pio}} will need a
way to figure out where to find the engine template. By default, it will look
at the current directory, but in case it is run from other path locations, this
switch will allow us to point to any engine template directory to search for
JARs. This is intended to be a transitional step though, and should not be
needed once "run anywhere" goal is achieved.
> 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
>
> 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.4#6332)
