Re: Regarding PredictionIO templates

o release v0.10 of PredictionIO in September, and we >>>> would need voluntary updates to the org namespace in all templates. As >>>> Pat mentioned, the best way to do this is via pull request to the template >>>> gallery. Below are the links to template gallery

Re: Apache PIO v0.10.0 release

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 wrote: > It’s been over a week waiting for the template donation paperwork, which I > imagine will take a few

Re: Apache PIO v0.10.0 release

BTW the Jira for license checking is https://issues.apache.org/jira/browse/PIO-27 On Sep 1, 2016, at 12:23 PM, Pat Ferrel wrote: 100% agree! I’ll work on the text license verification tomorrow. Oops back to the Jira. Ship it! On Aug 30, 2016, at 1:47 PM, Donald Szeto wrote: I am aware

Re: Sep 2016 Podling report

Thanks Suneel On Sep 2, 2016, at 12:35 PM, Suneel Marthi wrote: Filed the podling report for Sep 2016. On Fri, Sep 2, 2016 at 2:44 PM, Donald Szeto wrote: > Looks good to me. Thanks Suneel and Pat! > > On Thu, Sep 1, 2016 at 9:41 PM, Suneel Marthi wrote: > >> Please find below the proposed

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 incl

Re: Binary or Source release

o I hope you'll take my advice and evidence based assertion it can be done. Caveat: we use maven not SBT as build framework. > > On Sep 5, 2016, at 9:43 AM, Pat Ferrel wrote: > > This weekend I tracked down all out deps, which required a few scripts to > process sbt outpu

Re: Binary or Source release

pressure of hurrying for release. What do others think? On Sep 5, 2016, at 10:45 AM, Pat Ferrel wrote: Thanks Andy. RE “Only need to include one entry with the complete text of a license, everything else can just name the license.” So the copyright notice in the license is not important, only

Re: Binary or Source release

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 wrote: On Sep 5, 2016, at 1:25 PM, Alex Merritt wrote: Agree we should

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 Hat-base

Re: Incubation sponsor

We seem to be having problems with install.sh. I suggest we move it to the docs branch so we can continue to work on it post release. Donald, can you give us a count down or expected freeze date? On Sep 11, 2016, at 11:15 PM, Donald Szeto wrote: Thanks Andrew! On Sunday, September 11, 2016,

Re: Incubation sponsor

bunch of docs and tests. I'm going to publish rc artifacts for us to vote on today. Quick install instructions have been removed from docs. The onboarding experience should be "production quality" now. On Mon, Sep 12, 2016 at 10:56 AM, Pat Ferrel wrote: > We seem to be ha

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

+1 On Sep 13, 2016, at 11:55 AM, Donald Szeto wrote: This is the vote for 0.10.0 of Apache PredictionIO (incubating). The vote will run for at least 72 hours and will close on Sept 16th, 2016. The artifacts can be downloaded here: https://dist.apache.org/repos/dist/dev/incubator/predictionio/

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

Donald, you get a vote too. We need 3 (assuming no one is -1) to graduate this. Everyone please vote! On Sep 14, 2016, at 10:13 AM, Matthew Tovbin wrote: +1 On Wed, Sep 14, 2016 at 10:12 AM, Pat Ferrel wrote: > +1 > > > On Sep 13, 2016, at 11:55 AM, Donald Szeto wrote: >

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

cify "+1 Binding" if u r a PMC member. Its >> only the PMC votes that count for a release to pass. >> >> >> >>> On Thu, Sep 15, 2016 at 2:11 PM, Robert Lu wrote: >>> >>> +1 >>> >>>> On Sep 15, 201

Re: Batch import, Java

thub.com/PredictionIO/PredictionIO-Java-SDK/commit/6691144ebf1382aa1d060770a4fb7c0268f849d3> On Fri, Sep 9, 2016 at 7:59 AM, Pat Ferrel mailto:p...@occamsmachete.com>> wrote: The page is now live On Sep 8, 2016, at 11:49 AM, Gustavo Frederico mailto:gustavo.freder...@thinkwrap.com>&

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: Remove engine registration

ceId 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 mailto:p...@occamsmachete.com>> wrote: This is a great disc

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

> >>>> >>>> >>>>> On Thu, Sep 15, 2016 at 2:11 PM, Robert Lu > >>> wrote: >>>>> >>>>> +1 >>>>> >>>>>> On Sep 15, 2016, at 01:13, Matthew Tovbin > wrote: >>>>

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. All

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

> >>>> 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 Maven staging repo here: >>>> https://repository.a

Re: Batch import, Java

, Sep 16, 2016 at 2:25 PM, Pat Ferrel 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 be better > categorized to include SDKs, Templates, other extras lik

Re: Remove engine registration

on 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 for deployment. > > Regards, > Marcin > >

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 `pio app new X`, but pe

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 0.10.0 of Apache PredictionIO (incubating). >> >> The vote will run

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 hitti

Re: clashing hbase queries

be better distributed, which is another avenue of attack - partitioning, keying strategy. > On Oct 13, 2016, at 6:10 PM, Pat Ferrel wrote: > > The DAG for a template just happens to schedule 2 tasks that do something > like this: > > val fieldsRDD: RDD[(I

Re: clashing hbase queries

created in a pathological manner. On Oct 15, 2016, at 3:14 PM, Pat Ferrel 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 it out may cause parallel tasks

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 insta

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 ad

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 wrote: Now that we have a release what do people think about a joint idea sharing doc like this: https://docs.google.com/document/d

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 full

Re: consolidate repos into 1

I wouldn’t favor merging for Tom’s point and others: So far from the template I maintain, there have been 2 PIO releases and soon to be 7 template releases. The point being that active templates will have their own revision schedule. You have only to look at the history of the templates to see t

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) wrote: [ https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all

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

w. > > Alex > > On Nov 21, 2016 12:05 PM, "Pat Ferrel" 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 it erases all data. Since it is >> only used from templates we haven’t ha

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 with

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

roduce the issue (using SelfCleaningDataSourceTest). Will aim to track down & attempt a fix today / tomorrow. Alex On Mon, Nov 21, 2016 at 5:16 PM, Alex Merritt mailto:leca...@gmail.com>> wrote: Sure, I can try to reproduce this / take a look tomorrow. Alex On Nov 21, 2016 12:05

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 us

Re: Micro-releases

messed up my head before. Although more or less the same work, I believe it to be less of an issue if we end up messing up dev. I'm also in favor of using a well-documented approach such as gitflow, since I often forget the exact workflows of different projects. > On 25 Nov 2016, at 18:

Re: Micro-releases

nio. > incubator.apache.org/community/contribute-code/ > > On Sat, Nov 26, 2016 at 10:00 AM, Pat Ferrel > wrote: > >> This is a better description of how we should be managing code and git >> branches than I have every seen: http://nvie.com/posts/a-succes >> sful-git-

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: https://docs.google.com/document/d/1gxHeTHlAOfk

Re: Micro-releases

n, Nov 28, 2016 at 10:26 AM, Pat Ferrel wrote: > Good point (reliable building). An extension of strict semantic versioning > allows an extension like -incubating, this could include a Jira # too so > the full artifact name might be: > > org.apache.predictionio-0.10.0-incubating-ji

Re: Virtual Kickoff Meeting

Ping, Is anyone interested in a Google Hangout this coming week? On Dec 1, 2016, at 10:10 AM, Pat Ferrel wrote: 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

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 also, depending on final time > El El do

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 question

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 wrote: My first question

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 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 wrote: I can do Tuesday 11-12pm and 3-4pm PST

Re: Micro-releases

probably need a dedicated page or micro site in the doc for these kind of unofficial tar balls. It is against ASF policy to mark anything as release and encourage people to use without the formal voting process. They also cannot be sync to ASF distribution. On Thu, Dec 1, 2016 at 10:25 AM Pat Ferrel

Re: Micro-releases

you pull from master. it will not trigger a new release. Please remember that master is not our SNAPSHOT branch as explained below. speak soon or... On Dec 14, 2016, at 4:11 PM, Pat Ferrel wrote: @Mentors We are discussing creating a “hotfix” branch from which we will merge into development

Search on docs not working

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

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 wa

Re: Stateless Builds

ple 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 >> it's not c

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 wrote: Great, I’m really glad you are picking this up again. This is an important step! TLDR; To

Evolving PIO CLI

. Thread was Re: [jira] [Commented] (PIO-51) Enable `pio build/train/deploy` outside of engine directory On Jan 22, 2017, at 11:54 AM, Pat Ferrel (JIRA) wrote: [ https://issues.apache.org/jira/browse/PIO-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedComme

Re: Moving Builds to Apache?

IIRC build machines are of indeterminate capacity. We used to fail builds randomly based on the machine resources. Containers being somewhat more heavyweight than plain old unit tests I worry about that and ask infra. On Feb 17, 2017, at 10:22 AM, Donald Szeto wrote: Hi all, We have been dep

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 PMC members should indicate whether the vote

Attack email

If anyone gets a Google Docs share from me don’t click it. The URL is https:// accounts.google.com……. but it is an attack to get your contacts. Delete it.

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. https://docs.google.com/documen

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 woul

Re: Host PIO on Github (not ASF Git)

3:26 PM Pat Ferrel 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 directly, direct merging > of doc changes by users, l

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 wrote: Heard it from Mahout. I agree it’s not completely clear. Unless someone can illuminate us I’ll follow up with infra and report back.

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 “incuba

Re: Graduation to TLP

what the VP vs Member responsibilities look like. Let's graduate. +1 *Mars On Wed, Aug 30, 2017 at 15:21 Pat Ferrel wrote: > 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 mor

Re: Graduation to TLP

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 wrote: > Along with the link Donald gave, check this out: > http://community.apache.org/apache-way/apache-project-maturity-model.html > <http://com

Re: Graduation to TLP

The Chair, PMC, and Committers may be different after graduation. PMC/committers are sometimes not active committers but can have a valuable role as mentors, in non-technical roles, as support people on the mailing list, or as sometimes committers who don’t seem very active but come in every so

Re: Graduation to TLP

rom > main ASF doc) > - IN10, IN20 > > Let me know what you think. > > On Fri, Sep 1, 2017 at 10:32 AM, Pat Ferrel wrote: > >> The Chair, PMC, and Committers may be different after graduation. >> PMC/committers are sometimes not active committers but can have a &g

Re: Graduation to TLP

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 : > I personally don’t see much benefit in removing people unless they prove the > exception. AFA

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: [RESULT][VOTE] Resolution to create a TLP from graduating Incubator podling

>> Apache PredictionIO Project: >> >> * Alex Merritt >> * Andrew Kyle Purtell >> * Chan Lee >> * Donald Szeto >> * Felipe Oliveira >> * James Taylor >> * Justin Yip >> * Kenneth C

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 wrote: Actually we did go over the maturity checklist ourselves. Donald, maybe you can forwards the thread here. pasted from the thread on dev

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 w

All Github PR closed

Maybe I missed the explanation but why are all the gitub PRs against the PIO account closed? This is not ideas, especially if some should be merged with the ASF git, because the PRs have user/branch info that can be used to hand-merge.

Re: All Github PR closed

PRs are closed, so it left me wondering if there is a set of conditions that were triggered when GitHub integration was turned on. On Thursday, June 30, 2016, Pat Ferrel wrote: > Maybe I missed the explanation but why are all the gitub PRs against the > PIO account closed? This is not

Fwd: predictionio.NotCreatedError: Exception happened: [Errno 111] Connection refused for request POST /

ertPathBuilder.build(CertPathBuilder.java:280) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382) ... 23 more The build doesn't finish. Any help regarding the following? On Friday, July 1, 2016 at 8:29:49 PM UTC+5:30, Pat Ferrel wrote: The script is failing t

Re: predictionio.NotCreatedError: Exception happened: [Errno 111] Connection refused for request POST /

Shouldn’t all exceptions (well the vast majority) be caught in that code so no error would cause a failure of a build? On Jul 1, 2016, at 9:55 AM, Pat Ferrel wrote: io.prediction.workflow.UpgradeCheckRunner.run(WorkflowUtils.scala:400) Seems to be looking for "

Re: predictionio.NotCreatedError: Exception happened: [Errno 111] Connection refused for request POST /

disabled until our Apache migration is complete and stable. On Fri, Jul 1, 2016 at 10:01 AM, Pat Ferrel mailto:p...@occamsmachete.com>> wrote: Shouldn’t all exceptions (well the vast majority) be caught in that code so no error would cause a failure of a build? On Jul 1, 2016, at 9:55 AM, Pat

Re: Development Model

+1 (in general) The only issue will be when we have more than one release to support. For instance Elasticsearch 2.x forces an upgrade on all users and so may not be a good idea to add to our songle release branch, which is the master. This or other cases will eventually require us to have more

Re: The future of PIO

-snapshop, a months long WIP with relatively ambitious goals. If this discussion is seen as constructive by the PMC it should probably be moved to dev@ to get user’s input. On Jul 2, 2016, at 6:06 PM, Suneel Marthi mailto:suneel.mar...@gmail.com>> wrote: On Sat, Jul 2, 2016 at 8:58 P

Re: All Github PR closed

(as patch) to the new > PIO JIRA instance? > > There is some discussion about allowing GH Issues as a blessed resource for > development workflow, but we are not there yet where there is guidance for > podlings (or even TLPs). > > On Thu, Jun 30, 2016 at 4:04 PM, Pat Ferrel

Re: All Github PR closed

work on. > On Jul 4, 2016, at 10:35 AM, Pat Ferrel wrote: > > Creating a Jira for a PR is all well and fine but using pathces + Jira is a > pretty archaic and cumbersome way to handle PRs. If we simply reopen the PR > against the mirror github repo then all conversations there

Doc site

Some of us were talking on Slack and came up with the plan to have a docs/ directory in the main repo that will hold a Jekyll docs site. Whenever this is committed to, Jenkins will push this to a separate repo to which gitpubsub is connected. This will allow easier user PRs to docs and still mai

Re: [Proposal] The new template gallery

If we used the same mechanisms supported in the site generator it would simplify support. Yaml is fine but isn’t middleman in ruby?Maybe you don’t need a separate Python script. On Jul 20, 2016, at 9:50 AM, Donald Szeto wrote: Hey Marcin, I think this looks great for now! I think it is fine t

Re: [Proposal] Integration tests

+1 for integration tests. We have one for the UR that tests PIO too and can be a starter. It is probably possible to create one that is template independent that only tests the EventServer or some null template. https://github.com/actionml/template-scala-parallel-universal-recommendation/blob/m

First release

I’d like to propose a first minimum release from Apache to include: 1) SSL optional (I think @alex has already merged this PR) 2) Heal ActionML fork 3) change to Apache class naming and include Apache license notices in all code 4) live doc site 5) Apache classes published to the maven/sbt univers

Re: First release

. Hoping to get Jenkins running soon. How about Aug 8 as our first release? Due to all these package name changes, I'd also like to suggest to start a new minor version. How about 0.10.0? Regards, Donald On Sat, Jul 23, 2016 at 7:45 AM, Pat Ferrel wrote: > I’d like to propose a first minimum

Re: [Proposal] The new template gallery

guidelines on how to submit new templates. Introduced changes <https://github.com/apache/incubator-predictionio/compare/develop...Ziemin:template-gallery> śr., 20.07.2016 o 16:56 użytkownik Pat Ferrel napisał: > If we used the same mechanisms supported in the site generator it would > simp

Re: [Proposal] Integration tests

d template(s). Maybe the directory structure can be > something like this? > root/ > test/ >integration/ > EventserverSuite.scala > AppSuite.scala > SimilarProductTemplateSuite.scala > > seed/ > json data for testing eventserver >json data for testi

Re: [Proposal] Integration tests

Oops I see the code now. If it were a PR the discussion would be copied to the dev@ address On Jul 30, 2016, at 10:45 AM, Pat Ferrel wrote: Very nice step and I agree with the no-Scala approach. From my experience answering questions on several forums for users over the last year. PIO

Cleanup app

I’m trying to merge the AML fork and looked deeper into the cleanup app, which we turned into a optional feature of any Datasource. In the cleanup app example it uses an RDD.collect, which is not scalable. It seems that PEvents does not really support delete so you have to get the `eventsToDelet

Re: Support mailing list policy

On Aug 2, 2016, at 8:03 AM, Pat Ferrel wrote: > > Since Simon made the old pio Google Group read only there have been no posts > to the Apache user list and afaik no subscribes. This is not a good thing. Indeed. An Apache branded release with PR from the foundation (we can coordina

Re: Cleanup app

Thanks Alex. My pet feature :-) On Aug 2, 2016, at 2:42 PM, Alex Merritt wrote: It does look like we do need a new delete method there. I will take a look at this today. On Tue, Aug 2, 2016 at 8:47 AM, Pat Ferrel wrote: > I’m trying to merge the AML fork and looked deeper into the clea

Re: Inquery about the stroage and other file formats on HDFS and local FS.

This would work for some templates but not all. The Events as a collection need to support PEvents and LEvents APIs and files would make those type of queries rather difficult. I believe the current philosophy for PIO is that to include something in the core it would need to support all template

Re: transition from "official" PredictionIO templates to Apache

Actually this is mostly a fine idea but I think the bigger question is how do we treat templates in general. IMO the maintaining author can decide to contribute them or not and the committers can decide to accept or not. For example in the case of the UR I may decide to support and maintain it

Re: transition from "official" PredictionIO templates to Apache

too as long as the committer is willing to support the template. As far as the Salesforce templates marked official, I’d hope that most would be donated. According to the proposed rules all we need is a PR for each. And again a big thanks to Salesforce! On Aug 4, 2016, at 2:55 PM, Pat Ferrel

Trying to merge PR

I’m trying to build a template against the aml/apache merged pio. Obviously there are a few template code changes needed so I started with a completely clean EventServer meaning HBase and Elasticsearch were completely wiped and restarted. I deleted manifest.json and was able to build, and train.

Trying to merge PR

I’m trying to build a template against the aml/apache merged pio. Obviously there are a few template code changes needed so I started with a completely clean EventServer meaning HBase and Elasticsearch were completely wiped and restarted. I deleted manifest.json and was able to build, and train.

Re: Trying to merge PR

) ... 18 more On Aug 10, 2016, at 1:31 PM, Pat Ferrel wrote: I’m trying to build a template against the aml/apache merged pio. Obviously there are a few template code changes needed so I started with a completely clean EventServer meaning HBase and Elasticsearch were completely wiped and

PIO-20 problems

I’m always disinclined to commit code that has not been tested. However many things in the current state of the develop branch seem broken or at least too big to address in a single commit. 1) Style test fail in Travis that are not runnable or at least have not been documented for local build.

Re: PIO-20 problems

maybe this was not clear enough. If you > have any additional questions or run into issues executing the tests, > please let me know. > > Thanks, > Chan > > On Thu, Aug 11, 2016 at 6:07 AM, Pat Ferrel wrote: > >> I’m always disinclined to commit code that has not be

Re: transition from "official" PredictionIO templates to Apache

d > Marcin just submitted ( > https://github.com/apache/incubator-predictionio/pull/267 > <https://github.com/apache/incubator-predictionio/pull/267>). That way we > can > make commitment to included templates be part of every committer's effort. > Just my 2c. > > On

Re: PIO-20 problems

ching distribution found for unittest Tried forcing the version to 0.0 but again no luck Ideas? In the meantime waiting for Travis to do it—sigh On Aug 11, 2016, at 2:31 PM, Pat Ferrel wrote: With the keystore my template-based integration test passes and I’ve put the keystore back in. The diffs on P

  1   2   3   >