Supporting the latest and requiring them are 2 different things. Requiring them (except for ES) means PIO won’t run unless the clusters for every user are upgraded to match the client because only backward compatibility is supported. Last time I checked if you require HDFS 2.7, PIO won’t run on 2.6. If you require 2.6 PIO will run on 2.6 or 2.7 so immediate upgrades have no benefit. The last I checked there was no forward compatibility guarantee. Has this changed?
If ES guarantees forward compatibility that is great. On Jun 7, 2017, at 11:08 AM, Mars Hall <[email protected]> wrote: These upgrades are very similar to the dependencies we support/provide for PredictionIO 0.11.0-incubating in the Heroku buildpack. If the framework is going to upgrade default dependencies, I wholeheartedly agree that moving to the most recent versions of everything is the way to go. Once PIO reaches 1.0 releases, I'd imagine that every major dependency upgrade would be taken together and increment the PredictionIO major version. *Mars ( <> .. <> ) > On Jun 4, 2017, at 22:25, Shinsuke Sugaya <[email protected]> wrote: > > Hi all, > > We have a plan to change default build targets in PIO-83 and PIO-84. > Current versions look too old, so it will be better to support > newer versions as default. > > Current: > - PIO_SCALA_VERSION=2.10.6 > - PIO_SPARK_VERSION=1.6.3 > - PIO_ELASTICSEARCH_VERSION=1.7.6 > - PIO_HADOOP_VERSION=2.6.5 > > They will be changed to: > > 0.12.0: > - PIO_SCALA_VERSION=2.11.8 > - PIO_SPARK_VERSION=2.1.1 > - PIO_ELASTICSEARCH_VERSION=5.4.1 > - PIO_HADOOP_VERSION=2.7.3 > > Note that this change does not discard old version supports. > If you want to use old versions, you can build PIO with them. > > Please let us know if you have any concerns. > > https://issues.apache.org/jira/browse/PIO-83 > https://issues.apache.org/jira/browse/PIO-84 > > Regards, > shinsuke
