Hi,
I'd like to join the Prediction IO dev mailing list.
Thanks,
Vijay
Yes. Many of them are sources, docs, poms and signatures though.
On Sun, Sep 18, 2016 at 6:02 PM, Suneel Marthi
wrote:
> So all of these artifacts need to be verified and validated ?
>
> https://repository.apache.org/content/repositories/
>
So all of these artifacts need to be verified and validated ?
https://repository.apache.org/content/repositories/orgapachepredictionio-1003/org/apache/predictionio/
On Mon, Sep 19, 2016 at 2:59 AM, Donald Szeto wrote:
> I will start a new voting thread. The staging repo
This is the vote for 0.10.0 of Apache PredictionIO (incubating).
The only difference between RC1 and RC2 is adding the "apache-" prefix to
Maven artifacts.
The vote will run for at least 72 hours and will close on Sept 21st, 2016.
The artifacts can be downloaded here:
the MAven staging repo brings up whole load of artifacts, which ones r we
voting on again ?
On Mon, Sep 19, 2016 at 2:49 AM, Donald Szeto wrote:
> I have prepared a RC2. The artifacts can be downloaded here:
>
Yes u do have to vote fresh each time u create a new RC.
On Mon, Sep 19, 2016 at 2:49 AM, Donald Szeto wrote:
> I have prepared a RC2. The artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.10.0-
> incubating-rc2/
> or from the
This sounds like a good case for Donald’s suggestion.
What I was trying to add to the discussion is a way to make all commands rely
on state in the megastore, rather than any file on any machine in a cluster or
on ordering of execution or execution from a location in a directory structure.
Wojciech Indyk created PIO-38:
-
Summary: add Apache Parquet as a data source
Key: PIO-38
URL: https://issues.apache.org/jira/browse/PIO-38
Project: PredictionIO
Issue Type: New Feature