Upgrading to PredictionIO 0.12.0

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

Re: [DISCUSS] Proposed resolution to graduate the PredictionIO podling

oh, nm I found it. Pasted below, there were no dissenters to Donald’s detailed assessment. On Sep 29, 2017, at 3:27 PM, Pat Ferrel <p...@occamsmachete.com> wrote: Actually we did go over the maturity checklist ourselves. Donald, maybe you can forwards the thread here.

Re: [RESULT][VOTE] Resolution to create a TLP from graduating Incubator podling

gt;> * Donald Szeto <don...@apache.org> >> * Felipe Oliveira <fel...@apache.org> >> * James Taylor <jtay...@apache.org> >> * Justin Yip <yipjus...@apache.org> >> * Kenneth Chan <kenn...@apache.org> >>

[jira] [Closed] (PIO-32) create component upgrade releases

[ https://issues.apache.org/jira/browse/PIO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel closed PIO-32. - Resolution: Fixed > create component upgrade releases > - > >

Re: [VOTE] Apache PredictionIO (incubating) 0.12.0 Release (RC2)

The last release was hung up by the IPMC regarding content licensing issues and libraries used by the doc site, which we promised to address in this release. Have these been resolved, don’t recall the specifics? It would be great to fly through the IPMC vote without issue. On Sep 14, 2017, at

Re: Graduation to TLP

> wants to remove themselves. It may be good. In fact, most of committers carry out a task with limited time. Anyway I hope the project will progress in a good direction. 2017-09-06 3:43 GMT+09:00 Pat Ferrel <p...@occamsmachete.com>: > I personally don’t see much benefit in r

Re: Graduation to TLP

implicitly CS20, CS30, and CS40 from > main ASF doc) > - IN10, IN20 > > Let me know what you think. > > On Fri, Sep 1, 2017 at 10:32 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > >> The Chair, PMC, and Committers may be different after graduation. >> PM

Re: Graduation to TLP

se. +1 for graduation. I was away for a while due to family issues, but I'd be happy to volunteer for release management. On Wed, Aug 30, 2017 at 4:30 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > Along with the link Donald gave, check this out: > http://community.apache.org/apache-way/apach

Re: Graduation to TLP

. Would be great to understand what the VP vs Member responsibilities look like. Let's graduate. +1 *Mars On Wed, Aug 30, 2017 at 15:21 Pat Ferrel <p...@occamsmachete.com> wrote: > I have had several people tell me they want to wait until PIO is not > incubating before using it

Re: Graduation to TLP

I have had several people tell me they want to wait until PIO is not incubating before using it. This even after explaining that “incubating” has more to do with getting into the Apache Way of doing things and has no direct link to quality or community. I can only conclude from this that

[jira] [Commented] (PIO-96) Storage corrupted by sharing databases between engines with different storage configs

[ https://issues.apache.org/jira/browse/PIO-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070594#comment-16070594 ] Pat Ferrel commented on PIO-96: --- IMO this example is a non-issue. As the author of the UR I can state

Re: Host PIO on Github (not ASF Git)

https://issues.apache.org/jira/browse/INFRA-14191 <https://issues.apache.org/jira/browse/INFRA-14191> On May 18, 2017, at 4:56 PM, Pat Ferrel <p...@occamsmachete.com> wrote: Heard it from Mahout. I agree it’s not completely clear. Unless someone can illuminate us I’ll follow u

Re: Host PIO on Github (not ASF Git)

On Thu, May 18, 2017 at 3:26 PM Pat Ferrel <p...@occamsmachete.com> wrote: > BTW there seems now to be a way to host on Github (not ASF Git) by linking > our ASF accounts to our git accounts. This would make a bunch of things > much easier like PRs can be reviewed and merged dire

Host PIO on Github (not ASF Git)

BTW there seems now to be a way to host on Github (not ASF Git) by linking our ASF accounts to our git accounts. This would make a bunch of things much easier like PRs can be reviewed and merged directly, direct merging of doc changes by users, lots of nice stuff that is GUI related. This

PIO 0.12.0 and Graduation Time?

Should we apply for graduation to Apache TLP soon, like maybe the next release? I started a Google doc for features we want and any Mentors can add things we need to demonstrate for graduation since some may not be Jira-able. All user’s should feel free to input.

Re: [VOTE] Apache PredictionIO (incubating) 0.11.0 Release (RC2)

+1 binding was able to build and run integration tests on the UR, which has special needs for ES1 On Apr 11, 2017, at 2:41 PM, Chan Lee wrote: [+1] binding accept On Mon, Apr 10, 2017 at 1:22 PM, Donald Szeto wrote: > Thanks! Just a reminder that

[jira] [Commented] (PIO-49) Add support for Elasticsearch 5.x

[ https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945799#comment-15945799 ] Pat Ferrel commented on PIO-49: --- I've got the UR without any code changes working with ES1 but fails

[jira] [Commented] (PIO-49) Add support for Elasticsearch 5.x

[ https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906585#comment-15906585 ] Pat Ferrel commented on PIO-49: --- Going through the commit diff for clues, this should block release. >

[jira] [Assigned] (PIO-49) Add support for Elasticsearch 5.x

[ https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel reassigned PIO-49: - Assignee: Donald Szeto > Add support for Elasticsearch

[jira] [Reopened] (PIO-49) Add support for Elasticsearch 5.x

[ https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel reopened PIO-49: --- Does not work > Add support for Elasticsearch 5.x > - > >

[jira] [Resolved] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel resolved PIO-45. --- Resolution: Fixed now has an integration test in the DB-Cleaner template > SelfCleaningDatasource erases

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15886936#comment-15886936 ] Pat Ferrel commented on PIO-45: --- Passes my tests--woohoo Will automate the test in the new DB-Cleaner template

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15886010#comment-15886010 ] Pat Ferrel commented on PIO-45: --- I can automate the test in the DB-cleaner Template once we have an eyeball

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15885085#comment-15885085 ] Pat Ferrel commented on PIO-45: --- [~emergentorder] any movement on this? We want to release this week. I'll test

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876893#comment-15876893 ] Pat Ferrel commented on PIO-45: --- I've updated the Template here: https://github.com/actionml/db-cleaner.git

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875117#comment-15875117 ] Pat Ferrel commented on PIO-45: --- Yeah, sorry, it was a bad example but does follow the rules above. These rules

[jira] [Comment Edited] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875112#comment-15875112 ] Pat Ferrel edited comment on PIO-45 at 2/20/17 10:38 PM: - A db-cleaner Template

[jira] [Reopened] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel reopened PIO-45: --- property compression works incorrectly > SelfCleaningDatasource erases all d

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875107#comment-15875107 ] Pat Ferrel commented on PIO-45: --- The latest SelfCleaningDatasource still has some issues. I created a template

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15851751#comment-15851751 ] Pat Ferrel commented on PIO-45: --- $sets should never be dropped regardless of time-window, neither should $unset

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850875#comment-15850875 ] Pat Ferrel commented on PIO-45: --- Related commit, from a PR https://github.com/apache/incubator-predictionio

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850764#comment-15850764 ] Pat Ferrel commented on PIO-45: --- The time window duration seems to work on non-$set events but the Galaxy

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850749#comment-15850749 ] Pat Ferrel commented on PIO-45: --- You can use the UR from here; https://github.com/actionml/universal

[jira] [Updated] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated PIO-45: -- Attachment: import_handmade_simple.py import script for the data file > SelfCleaningDatasource erases all d

[jira] [Updated] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated PIO-45: -- Attachment: sample-time-window-and-downsample-data.txt simple set of data to test > SelfCleaningDatasource era

[jira] [Updated] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated PIO-45: -- Priority: Blocker (was: Critical) > SelfCleaningDatasource erases all d

[jira] [Commented] (PIO-45) SelfCleaningDatasource erases all data

[ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850734#comment-15850734 ] Pat Ferrel commented on PIO-45: --- [~emergentorder] This has gone through several fixes but still as of Feb 2 2017

[jira] [Closed] (PIO-33) Add support for Elasticsearch 2.x to upgrade release branch

[ https://issues.apache.org/jira/browse/PIO-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel closed PIO-33. - Resolution: Fixed Superceded by PIO-49 with Elasticsearch 5.x support, which gets us the upgrade and supports

[jira] [Commented] (PIO-33) Add support for Elasticsearch 2.x to upgrade release branch

[ https://issues.apache.org/jira/browse/PIO-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836982#comment-15836982 ] Pat Ferrel commented on PIO-33: --- This should be resolved, Elasticsearch 5.x does work with dot in property names

[jira] [Commented] (PIO-51) Enable `pio build/train/deploy` outside of engine directory

[ https://issues.apache.org/jira/browse/PIO-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836978#comment-15836978 ] Pat Ferrel commented on PIO-51: --- [~chanlee514] Is this needed since we are not using the path-to-dir? > Ena

Re: Stateless Builds

So to be clear no objections to the PR. I’m using it to talk about something that may be off topic to the PR and apologies if it is confusing the issue. On Jan 10, 2017, at 12:52 PM, Pat Ferrel <p...@occamsmachete.com> wrote: Great, I’m really glad you are picking this up

Re: Stateless Builds

usion I've seen from people trying to work >> with PIO is the multiple storage aspects (data, model, & metadata) combined >> with multiple services types (eventserver & engine) and how these all >> interconnect. Plus some engines have a requirement like Elasticsearch, but &g

State of PIO

The activity level has been pretty low lately. I hope this is just timing of holidays, work, etc. I know I’ve been too busy at work to do much until now. If we are going to graduate from the incubator we’ll have to start regular releases with substantial progress in each. We have several PRs

Search on docs not working

Not sure this is worth a Jira but search isn’t working on the PIO site.

Re: Micro-releases

10:25 AM Pat Ferrel <p...@occamsmachete.com> wrote: > But the downside is we never touch major, or haven’t in all the years of > PIO. So in effect all releases will be minor number changes and so far we > have only touched that 10 times in all the years of PIO. We could skip many >

Re: Virtual Kickoff Meeting

about Dec 13 2-4PM or Dec 15 11-1pm or suggest another time On Dec 7, 2016, at 4:11 PM, Pat Ferrel <p...@occamsmachete.com> wrote: Argh, both my computers were down, did we have this? if not how about Friday or next week M or Tu? On Dec 5, 2016, at 9:06 AM, Donald Szeto <don...@apache.o

Re: Stateless Builds

OK, so that was too much detail. My immediate question is how to train on one machine and deploy on several others—all referencing the same instance data (model)? Before it was by copying the manifest, now there is no manifest. On Dec 7, 2016, at 5:43 PM, Pat Ferrel <p...@occamsmachete.

Re: Stateless Builds

My first question is how to train on an ephemeral machine to swap models into an already deployed prediction server, because this is what i do all the time. The only way to do this now is train first on dummy data then deploy and re-train as data comes in, but there are other issues and

Re: Virtual Kickoff Meeting

Argh, both my computers were down, did we have this? if not how about Friday or next week M or Tu? On Dec 5, 2016, at 9:06 AM, Donald Szeto wrote: I can do Tuesday 11-12pm and 3-4pm PST. On Sun, Dec 4, 2016 at 10:34 AM Rafa Haro wrote: > I would join

Virtual Kickoff Meeting

I’d like to propose a Google Hangout for any interested parties to discuss the PIO roadmap. It may be a very chaotic meeting since it’s our first so please visit this page and add your throughts ahead of time or see what other people are thinking:

Re: Micro-releases

on we should update http://predictionio. > incubator.apache.org/community/contribute-code/ > > On Sat, Nov 26, 2016 at 10:00 AM, Pat Ferrel <p...@occamsmachete.com> > wrote: > >> This is a better description of how we should be managing code and git >> branches than

Re: Micro-releases

ent projects. > On 25 Nov 2016, at 18:57, Pat Ferrel <p...@actionml.com> wrote: > > Our dev process includes edge/snapshot code being kept in the develop branch > until release time. I like this process because it allows us to keep master > clean and stable. So imagine tha

Micro-releases

Our dev process includes edge/snapshot code being kept in the develop branch until release time. I like this process because it allows us to keep master clean and stable. So imagine that we have a major bug fix. To get this to users we could do a release but this can’t happen soon enough if a

Re: [jira] [Updated] (PIO-45) SelfCleaningDatasource erases all data

rote: Sure, I can try to reproduce this / take a look tomorrow. Alex On Nov 21, 2016 12:05 PM, "Pat Ferrel" <p...@occamsmachete.com <mailto:p...@occamsmachete.com>> wrote: Do you have time to look at this Alex? I may have made a mistake in merging this feature. At present an

Re: Introducing Myself

Welcome! The biggest problem I see today is helping older user (since before Apache) get up to speed with a doc on the docs site. I recently tried to explain this in a Github issue and gave up—it was getting too long and confusing. If you’ve used PIO for some time you might be able to help

Re: [jira] [Updated] (PIO-45) SelfCleaningDatasource erases all data

an try to reproduce this / take a look tomorrow. > > Alex > > On Nov 21, 2016 12:05 PM, "Pat Ferrel" <p...@occamsmachete.com> wrote: > >> Do you have time to look at this Alex? I may have made a mistake in >> merging this feature. At present any use of

Re: [jira] [Updated] (PIO-45) SelfCleaningDatasource erases all data

to see if the problem is reproducible? Or tell me how to run those? It’s included in one of the example templates, right? On Nov 20, 2016, at 5:30 PM, Pat Ferrel (JIRA) <j...@apache.org> wrote: [ https://issues.apache.org/jira/browse/PIO-4

[jira] [Created] (PIO-45) SelfCleaningDatasource erases all data

Pat Ferrel created PIO-45: - Summary: SelfCleaningDatasource erases all data Key: PIO-45 URL: https://issues.apache.org/jira/browse/PIO-45 Project: PredictionIO Issue Type: Bug Affects Versions

Trouble with HBase and PEventStore.aggregateProperties

The use of PEventStore.aggregateProperties as shown below causes errors when a large cluster is making the query. It seems to cause a full DB scan, which results in timeouts. This may be because nearly 400 (parallelism of the cluster) threads are making requests. But should this result in a

Re: The future of PIO

Oops, should have read Simon’s email. Anyway a GD is created if we want to use that. On Oct 25, 2016, at 10:46 AM, Pat Ferrel <p...@occamsmachete.com> wrote: Now that we have a release what do people think about a joint idea sharing doc like this: https://docs.google.com/docu

The future of PIO

Now that we have a release what do people think about a joint idea sharing doc like this: https://docs.google.com/document/d/1gxHeTHlAOfkuhO_g8DzbX4LOrTlLAtyWOIoi3qeqSc0/edit?usp=sharing Please

Re: Compilations errors in Similar-Product engine template

you are not using the right template code. It’s not io.prediction… anymore it’s org.apache.predicitionio… now The templates donated to Apache linked to on the web site are not updated to the build method yet. There are PRs for many of the repos that have versions that will build fine. For

Re: clashing hbase queries

created in a pathological manner. On Oct 15, 2016, at 3:14 PM, Pat Ferrel <p...@occamsmachete.com> wrote: I may have been on the wrong track with the 2 parallel task idea, which is a problem. The typical use with Spark is to get all data out of HBase and work on it as RDDs but getting

clashing hbase queries

The DAG for a template just happens to schedule 2 tasks that do something like this: val fieldsRDD: RDD[(ItemID, PropertyMap)] = PEventStore.aggregateProperties( appName = dsp.appName, entityType = "item")(sc) to execute in parallel The PEventStore calls from 2 separate closures start

Re: [VOTE] Apache PredictionIO (incubating) 0.10.0 Release (RC5)

+1 binding On Oct 1, 2016, at 10:20 AM, Suneel Marthi wrote: +1 binding On Sat, Oct 1, 2016 at 12:05 PM, Matthew Tovbin wrote: > +1 > > - Matthew > > On Oct 1, 2016 00:18, "Donald Szeto" wrote: > >> This is the vote for

Re: [VOTE]: Apache PredictionIO (incubating) 0.10.0 Release (RC4)

+1 binding On Sep 23, 2016, at 12:28 PM, Alex Merritt wrote: +1 (Binding) Extracted, built, installed manually (with HBase / ElasticSearch / local fs configured in pio-env.sh), start script works, status works, sbt tests pass. Had low system entropy which caused fail on

Re: Remove engine registration

nly as code being a dependency for > application related models/algorithms. So you would register an engine - as > a code once and run training for some domain specific data (app) and > algorithm parameters, what would result in a different identifier, that > would be later used f

Re: Batch import, Java

bution. Is that possible? Thanks Gustavo On Fri, Sep 16, 2016 at 2:25 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > Which brings up the next set of issues: What do we do for Salesforce owned > SDKs? Can the SDKs be donated? > > In any case I suggest we add to the “gallery” so it might

Re: [VOTE]: Apache PredictionIO (incubating) 0.10.0 Release

ictionio/0.10.0- >>>> incubating-rc2/ >>>> or from the Maven staging repo here: >>>> https://repository.apache.org/content/repositories/ >>>> orgapachepredictionio-1003/ >>>> . >>>> >>>> Do we need to vote on the RC2 again? &

Re: Remove engine registration

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.

Re: Remove engine registration

o/some-engine.json --instanceId some-REST-compatible-resource-id` ? Currently PIO also has a concept of engineInstanceId, which is output of train. I think you are referring to different thing, right? Kenneth On Fri, Sep 16, 2016 at 12:58 PM, Pat Ferrel <p...@occamsmachete.com <mailto:p...@occam

Re: Remove engine registration

This is a great discussion topic and a great idea. However the cons must also be addressed, we will need to do this before multi-tenant deploys can happen and the benefits are just as large as removing `pio build` It would be great to get rid of manifest.json and put all metadata in the store

Re: Batch import, Java

f849d3 <https://github.com/PredictionIO/PredictionIO-Java-SDK/commit/6691144ebf1382aa1d060770a4fb7c0268f849d3> On Fri, Sep 9, 2016 at 7:59 AM, Pat Ferrel <p...@occamsmachete.com <mailto:p...@occamsmachete.com>> wrote: The page is now live On Sep 8, 2016, at 11:

Re: [VOTE]: Apache PredictionIO (incubating) 0.10.0 Release

robberp...@outlook.com> wrote: >>> >>> +1 >>> >>>> On Sep 15, 2016, at 01:13, Matthew Tovbin <tovb...@apache.org> wrote: >>>> >>>> +1 >>>> >>>> On Wed, Sep 14, 2016 at 10:12 AM, Pat Ferrel <

Re: Release Manager

Thanks Donald! We still need to cleanup 2 things, 1) the LICENSE.txt and NOTICE.txt now has to reflect only sources included. I’ll update the license Jira and will do the editing (easy now). 2) the install.sh *needs testing*, please anyone who can try it, on different distros (Mac, Red

Re: Binary or Source release

it and the install.sh can be made to point to it. Not sure what the ASF rules are regarding this so maybe the mentors can comment—specifically do we have to use the Apache mirror system? On Sep 5, 2016, at 4:34 PM, Pat Ferrel <p...@occamsmachete.com> wrote: On Sep 5, 2016, at 1:25 PM, Alex M

Binary or Source release

This weekend I tracked down all out deps, which required a few scripts to process sbt output. This yielded 166 deps, so this implies we need to include 166 licenses and copyright notices in LICENSE.txt. As I read the Apache guidelines this should be the license that goes with the version we

[jira] [Commented] (PIO-27) Check release artifacts for licenses and the LICENSE.txt file

[ https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15461979#comment-15461979 ] Pat Ferrel commented on PIO-27: --- The current install script does a build from source. The old PIO one did

[jira] [Commented] (PIO-27) Check release artifacts for licenses and the LICENSE.txt file

[ https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15461706#comment-15461706 ] Pat Ferrel commented on PIO-27: --- just to document for the next person that does it, for transitive deps we need

[jira] [Commented] (PIO-27) Check release artifacts for licenses and the LICENSE.txt file

[ https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15461664#comment-15461664 ] Pat Ferrel commented on PIO-27: --- This seems to require us to go back to the source of the specific version

[jira] [Commented] (PIO-27) Check release artifacts for licenses and the LICENSE.txt file

[ https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456370#comment-15456370 ] Pat Ferrel commented on PIO-27: --- [~dszeto] Will start work on the text license part of this Friday Sept 2

Re: Apache PIO v0.10.0 release

later this week. I also hope to start the release candidate process in the 1st week of September. The community has been asking and we'd like to ship it to them. On Tue, Aug 30, 2016 at 10:05 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > It’s been over a week waiting for the template don

Re: Regarding PredictionIO templates

ioned, the best way to do this is via pull request to the template >>>> gallery. Below are the links to template gallery page and instructions. For >>>> both namespace updates and your new template, you can just specify the >>>> pio_min_version as 0.10.0 and it will work with

[jira] [Comment Edited] (PIO-30) Cross build for different versions of scala and spark

[ https://issues.apache.org/jira/browse/PIO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449714#comment-15449714 ] Pat Ferrel edited comment on PIO-30 at 8/30/16 6:18 PM: How does Spark do

[jira] [Comment Edited] (PIO-30) Cross build for different versions of scala and spark

[ https://issues.apache.org/jira/browse/PIO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449714#comment-15449714 ] Pat Ferrel edited comment on PIO-30 at 8/30/16 6:16 PM: How does Spark do

[jira] [Commented] (PIO-30) Cross build for different versions of scala and spark

[ https://issues.apache.org/jira/browse/PIO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449705#comment-15449705 ] Pat Ferrel commented on PIO-30: --- Fine with me if we can do with cross-build but it's not just different

[jira] [Commented] (PIO-32) Create component upgrade release branch

[ https://issues.apache.org/jira/browse/PIO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449615#comment-15449615 ] Pat Ferrel commented on PIO-32: --- Might as well add new ES 2.x compatibility since we will break backwards binary

[jira] [Created] (PIO-33) Add support for Elasticsearch 2.x to upgrade release branch

Pat Ferrel created PIO-33: - Summary: Add support for Elasticsearch 2.x to upgrade release branch Key: PIO-33 URL: https://issues.apache.org/jira/browse/PIO-33 Project: PredictionIO Issue Type: New

[jira] [Commented] (PIO-32) Create component upgrade release branch

[ https://issues.apache.org/jira/browse/PIO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449604#comment-15449604 ] Pat Ferrel commented on PIO-32: --- may be other things to add to this upgrade release branch > Create compon

Apache PIO v0.10.0 release

It’s been over a week waiting for the template donation paperwork, which I imagine will take a few weeks to go through repo creation, license validation and PR merging before they can be released. Since they can be on a separate release schedules I’d like to remove them from being blocking

Re: Regarding PredictionIO templates

6 at 2:21 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > Hi Bansari, > > Chan Lee has done this too, and added tests from the new integration test > framework. We are awaiting a donation from Saleforce and new repo creation > before anything can be pushed. > > If you wo

[jira] [Commented] (PIO-24) move templates to apache git repos

[ https://issues.apache.org/jira/browse/PIO-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431865#comment-15431865 ] Pat Ferrel commented on PIO-24: --- Sorry [~chanlee514] my mistake. you don't need an ICLA until you are doing

[jira] [Commented] (PIO-25) Don't attempt to start PostgreSQL when it's not being used

[ https://issues.apache.org/jira/browse/PIO-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431258#comment-15431258 ] Pat Ferrel commented on PIO-25: --- A pull request or patch is welcome. > Don't attempt to start PostgreSQL w

Re: Apache PIO v0.10.0 release

gardless it would be good if someone reviewed the release artifacts now > and validates the License and Notices as opposed to pushing a release and > getting -1 vote from IPMC. > > > >> On Sat, Aug 20, 2016 at 2:21 PM, Pat Ferrel <p...@occamsmachete.com> wrote: >&

[jira] [Commented] (PIO-27) Check release artifacts for licenses and the LICENSE.txt file

[ https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429798#comment-15429798 ] Pat Ferrel commented on PIO-27: --- Further @dev comments It took Gearpump six release candidates before

[jira] [Updated] (PIO-27) Check release artifacts for licenses and the LICENSE.txt file

[ https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated PIO-27: -- Assignee: (was: Pat Ferrel) > Check release artifacts for licenses and the LICENSE.txt f

Re: Apache PIO v0.10.0 release

ensure that all third party jars have been accounted for and the License and Notice files are included in the appropriate project release artifacts. On Sat, Aug 20, 2016 at 2:00 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > What do people think remains for release? > > 1) templ

Apache PIO v0.10.0 release

What do people think remains for release? 1) template donation and mods. Chan Lee has done work on this but we can’t review until the donation and repos are set up. 2) install.sh. There are some suggestions on how to deal with the one-line install here:

[jira] [Updated] (PIO-18) Documentation for setting up the project for developers

[ https://issues.apache.org/jira/browse/PIO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated PIO-18: -- Priority: Minor (was: Major) > Documentation for setting up the project for develop

[jira] [Commented] (PIO-18) Documentation for setting up the project for developers

[ https://issues.apache.org/jira/browse/PIO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429466#comment-15429466 ] Pat Ferrel commented on PIO-18: --- I think this works, but you need to create the correct class for the entry

  1   2   >