+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, [email protected] wrote: Hi Im have a template that works fine with command line pio train. however, when I try to debug with Intellij (based on https://predictionio.incubator.apache.org/resources/intellij/ <https://predictionio.incubator.apache.org/resources/intellij/>) 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. “org.apache.predictionio.data.storage.elasticsearch.StorageClient”. I looked up my pio-assembly-0.11.0-incubating. Jar the above class is not present. Any help regarding this would be appreciated. https://drive.google.com/open?id=0ByikS_JzUnoiR2VQS0pqVFhfUW8 <https://drive.google.com/open?id=0ByikS_JzUnoiR2VQS0pqVFhfUW8> above link has the .jar file got after running make-distribution.sh Med venlig hilsen/Best regards Hari Charan Solution Developer E [email protected] <mailto:[email protected]%20> M +45 50 38 65 83 Aldersrogade 8, 2100 Copenhagen, Denmark | T +45 88 81 80 00 | www.scalepoint.com <http://www.scalepoint.com/>
