Github user dszeto commented on the issue:
https://github.com/apache/incubator-predictionio/pull/328
@pferrel For `pio build` we probably can enhance it such that it can take a
working directory for compilation to run. If we look at some other build tools,
they also rely on having
[
https://issues.apache.org/jira/browse/PIO-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15713541#comment-15713541
]
ASF GitHub Bot commented on PIO-47:
---
Github user dszeto commented on the issue:
Github user chanlee514 commented on the issue:
https://github.com/apache/incubator-predictionio/pull/328
@pferrel: I agree, and that would be possible with a general metadata
registry server which would be the next step. The reason I started by removing
manifest.json is because the
I’d like to propose a Google Hangout for any interested parties to discuss the
PIO roadmap.
It may be a very chaotic meeting since it’s our first so please visit this page
and add your throughts ahead of time or see what other people are thinking:
Yes. I was suggesting to use 0.10.1-incubating. The upside of this is that
our end users know which one has included all the latest fix instead of
tracking different JIRA ticket numbered suffices. We can limit real
releases to touch only major and minor version parts.
On Mon, Nov 28, 2016 at
Github user chanlee514 commented on the issue:
https://github.com/apache/incubator-predictionio/pull/328
Right now, the commands throw java.io.FileNotFoundException regarding
engine.json. May be better if we throw an error message saying the commands
should be executed inside engine
Hi,
when i tried to run *PIO TRAIN* Command It is giving below exception
-
*[INFO] [Engine$] Using existing engine manifest JSON at
${json.getCanonicalPath}[INFO] [Runner$] Submission command:
/home/vinod/PredictionIO/vendors/spark-1.6.2/bin/spark-submit --class
