Github user pferrel commented on the issue:
https://github.com/apache/incubator-predictionio-template-java-ecom-recommender/pull/6
Making templates easier for users doing upgrades is extremely important IMO.
Getting them working with 0.12.0 is first priority and I for one
Github user pferrel commented on the issue:
https://github.com/apache/incubator-predictionio-template-java-ecom-recommender/pull/6
the PR is fine, but this can be solved partially with the current
templates. For instance why not support both the previous defaults (those used
in
Github user hareeshmu commented on the issue:
https://github.com/apache/incubator-predictionio-template-text-classifier/pull/14
How to make this compatible with **PredictionIO-0.12.0-incubating**
Able to build after adding `scalaVersion := "2.11.8"` in the build.sbt
But`
Github user takezoe commented on the issue:
https://github.com/apache/incubator-predictionio-template-java-ecom-recommender/pull/6
@pferrel It looks to be impossible to solve in the current template
mechanism. I believe that keeping templates for the latest and default stack is
the
Github user takezoe commented on the issue:
https://github.com/apache/incubator-predictionio-template-text-classifier/pull/14
@hareeshmu We are progressing updating templates just now, but this
template is not updated for PredictionIO 0.12.0 yet. Some code modifications
seem to be
PIO-0.12.0 by default, compiles and runs expecting ES5. If you are upgrading
(not installing from clean) you will have an issue because ES1 indexes are not
upgradable in any simple way. The simplest way to upgrade to pio-0.12.0 and ES5
is to do `pio export` to backup BEFORE upgrading—so export
