Github user pferrel commented on the issue:
https://github.com/apache/incubator-predictionio/pull/336
@marevol you might want to search for "plugins" in the PIO code I think it
may already put those jars in the SparkSubmit params
This does seem like a better solution than buil
Github user Abhilash-Chandran commented on the issue:
https://github.com/apache/incubator-predictionio/issues/317
**For Ubuntu 16.04:**
This helped me.
[PostgreSQL for Ubuntu](https://help.ubuntu.com/community/PostgreSQL
)
Check the section "Aternative server setup".
[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879615#comment-15879615
]
ASF GitHub Bot commented on PIO-49:
---
Github user pferrel commented on the issue:
https:
Github user pferrel commented on the issue:
https://github.com/apache/incubator-predictionio/pull/336
So you are using the old PIO plugins feature that basically puts any files
in `plugins` onto the SparkSubmit --files param? The plugins are, in effect,
jars outside the pio assembly
Github user marevol commented on the issue:
https://github.com/apache/incubator-predictionio/pull/336
Although I'm not sure about old plugin features, in my fix, I put plugin
jar files with --jars on spark-submit:
https://github.com/jpioug/incubator-predictionio/commit/70d117c1e35
Github user pferrel commented on the issue:
https://github.com/apache/incubator-predictionio/pull/336
This would imply too that a single assembly is not enough and you'd have to
deploy the entire pio directory structure to any machine that runs it, right?
This in turn means that it ma
[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879471#comment-15879471
]
ASF GitHub Bot commented on PIO-49:
---
Github user marevol commented on the issue:
https:
[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879452#comment-15879452
]
ASF GitHub Bot commented on PIO-49:
---
Github user pferrel commented on the issue:
https:
[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879449#comment-15879449
]
ASF GitHub Bot commented on PIO-49:
---
Github user pferrel commented on the issue:
https:
Github user marevol commented on the issue:
https://github.com/apache/incubator-predictionio/pull/336
Please see our snapshot build:
http://fess.codelibs.org/snapshot/apache-predictionio-0.11.0-v1-SNAPSHOT.zip
Storage implementations, such as hbase, were moved to plugins/data-*
pr
[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879255#comment-15879255
]
ASF GitHub Bot commented on PIO-49:
---
Github user marevol commented on the issue:
https:
[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878996#comment-15878996
]
ASF GitHub Bot commented on PIO-49:
---
Github user pferrel commented on the issue:
https:
Github user marevol commented on the issue:
https://github.com/apache/incubator-predictionio/pull/336
To solve this issue, how about using plugin directory?
In our branch(https://github.com/jpioug/incubator-predictionio), ES1/ES5
codes in data were extracted to data-elasticsearch a
GitHub user imraansarwar opened an issue:
https://github.com/apache/incubator-predictionio/issues/351
Low to no activity
The activity on the project is getting lower to lowest. Can you shed some
light on the future road-map of the project?
Regards,
Imran
-
[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877901#comment-15877901
]
ASF GitHub Bot commented on PIO-49:
---
Github user marevol commented on the issue:
https:
15 matches
Mail list logo