predictionio-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject RE: Intellij Pio Train
Date Mon, 24 Jul 2017 09:06:53 GMT
Adding, the following fixed it. Thanks for the heads up.

  "org.apache.predictionio" % "apache-predictionio-data-elasticsearch1_2.10" % "0.11.0-incubating",
  "org.apache.predictionio" % "apache-predictionio-data-localfs_2.10" % "0.11.0-incubating",
  "org.apache.predictionio" % "apache-predictionio-data-hbase_2.10" % "0.11.0-incubating",

Further for “Intellij sbt refresh, is another problem altogether”:

 I instead added the project SBT dependencies to “pio-runtime-jars” and added pio-runtime-jars
as the class path. This does not result in dependencies missing every time SBT refreshes.

From: Pat Ferrel []
Sent: Thursday, July 20, 2017 8:30 PM
Subject: Re: Intellij Pio Train is what I said might need
to be hand added. Find the right one for ES 1.7.5 and add it to the project as “provided”.
 It is not in the main jar, the client for the correct version of ES is put on the classpath
and loaded with PIO’s CLI and call to spark-submit. So when using a debugger it may have
no way to find its classes since the debugger bypasses the CLI. Mind that the client is the
PIO client that talks to ES 1.7.5, nothing in the ES namespace.

This is just a guess but the above is true IIRC.

On Jul 20, 2017, at 8:54 AM,<> wrote:

Thanks Pat,

I’m on ES 1.7.5.

  1.  Adding Elasticsearch client jar will not help
  2.  Intellij is not to be blamed for this instance
  3.  Intellij sbt refresh, is another problem altogether

class. “”. does not get
merged on running ./

in fact ./ fails to merge the classes
to PredictionIO-0.11.0-incubating.Jar<>

From: Pat Ferrel []
Sent: Thursday, July 20, 2017 5:27 PM
Subject: Re: Intellij Pio Train

+1 This has been a constant problem with PIO due to several non-standard build and execution
paths in the code. In this case the version of Elasticsearch you use determines which version
of PIO client classes are used. I have given up on using a debugger with PIO after having
contributed a fair bit to that how-to. You may find that adding the Elasticsearch client jar
you are using to the IntelliJ project by hand will help. I don’t know for sure.

If you do find a way to get it working please consider updating that how-to. I have found
IntelliJ to be part of the problem, forgetting some hand config when sbt refreshes for instance,
but that may have been fixed. Longer term I think the idea is to make this easier by smoothing
out some things that give debuggers problems.

On Jul 20, 2017, at 5:13 AM,<> wrote:


Im have  a template that works fine with command line pio train.

however, when I try to debug with Intellij (based on

I get an error “Error initializing storage client for source ELASTICSEARCH”.

On in depth inspection I find that it throws an error as it not able to find the class. “”.

I looked up my pio-assembly-0.11.0-incubating. Jar the above class is not present.

Any help regarding this would be appreciated.

above link has the .jar file got after running

Med venlig hilsen/Best regards
Hari Charan
Solution Developer

M  +45 50 38 65 83

Aldersrogade 8, 2100 Copenhagen, Denmark  | T +45 88 81 80 00 |<>

View raw message