Re: [PIO 0.10.0][Universtal Recommender 0.5] Exception when using remote Elasticsearch while training

I tried to run the command curl -X GET http://engine-server:9200 and I'm getting a JSON response but when I'm running the command pio train I got org.elasticsearch.hadoop.rest.EsHadoopTransportException: java.net.NoRouteToHostException: No route to host (Host unreachable) exception 2017-04-0

Re: Adding a new application is slow

The patch is here https://github.com/apache/incubator-predictionio/pull/367 On Thursday, April 6, 2017 at 8:13:31 PM UTC+3, juha.s...@gmail.com wrote: > > I'll try make a patch for this to PredicitionIO during the weekend if I > have the time. > > On Thursday, April 6, 2017 at 8:07:31 PM UTC+3, p

Re: [PIO 0.10.0][Universtal Recommender 0.5] Exception when using remote Elasticsearch while training

I tried using these configurations in the sparkConf section of engine.json It has the same effect as the code I mentioned below but I still getting the same exception. 2017-04-07 5:03 GMT+04:00 Pat Ferrel : > BTW the docs for sparkConf are here: http://actionml.com/ > docs/ur_config#ur-spark-conf

Re: [PIO 0.10.0][Universtal Recommender 0.5] Exception when using remote Elasticsearch while training

BTW the docs for sparkConf are here: http://actionml.com/docs/ur_config#ur-spark-conf On Apr 6, 2017, at 4:52 PM, Pat Ferrel wrote: PIO in the past used the “transport client” of Elasticsearch, which is on port 9300 by default, The UR uses t

Re: [PIO 0.10.0][Universtal Recommender 0.5] Exception when using remote Elasticsearch while training

PIO in the past used the “transport client” of Elasticsearch, which is on port 9300 by default, The UR uses the REST client for some things like rapid writes to ES using Spark using a lib supplied by Elasticsearch. So, Spark needs to have config that the Elasticsearch library can read. This can

[PIO 0.10.0][Universtal Recommender 0.5] Exception when using remote Elasticsearch while training

Hello, I try to run training from a remote machine. It fails in later stage due to this exception : org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException: Connection error (check network and/or proxy settings)- all nodes failed; tried [[engine-server:9300]] According to the stack trace the

Re: Adding a new application is slow

I'll try make a patch for this to PredicitionIO during the weekend if I have the time. On Thursday, April 6, 2017 at 8:07:31 PM UTC+3, pat wrote: > > Hmm, interesting. I have heard of this being a problem in PredictionIO but > haven’t heard this explanation before IIRC. > > > On Apr 6, 2017, at

Re: Adding a new application is slow

Hmm, interesting. I have heard of this being a problem in PredictionIO but haven’t heard this explanation before IIRC. On Apr 6, 2017, at 9:47 AM, juha.syrj...@gmail.com wrote: Ah, I just found the problem: a fresh AWS instance takes a long time to generate enough entropy so that a random acce

Re: Cart/Complementary purchase recommendation with UR

Yes it can be done but support is not ideal so UR v0.6.0 coming just after the release of PIO-0.11.0 (in RC now) has some enhancements that give you better options and easier queries. To get truly complimentary purchases you need to train on shopping carts, not users purchases. So the primary i

Queries

Hi, I am very new to predictionIO. I have downloaded a template and ran a test of it with PostgreSQL as backend. I want to use Hadoop as my backEnd Please help me with my following queries. 1. How to connect predictionIO with single node Hadoop cluster? 2. What are the dependencies for the sam

Re: Items blacklisted in the query made to Elasticsearch by UR

*BTW I assume "user": "069d-8661-453f-8c89-ac50aea0c0d8” has those items in their “facet” history? Otherwise I’m not sure where they’d come from.* Yes I confirm that this user has those items in his facet history. 2017-04-05 18:18 GMT+02:00 Pat Ferrel : > Ok thanks for ruling out a couple th