[jira] [Created] (PIO-134) Document how to upgrade from 0.11, including building 0.12 for defaults used by 0.11

[Donald Szeto (JIRA)]

Donald Szeto created PIO-134:


 Summary: Document how to upgrade from 0.11, including building 
0.12 for defaults used by 0.11
 Key: PIO-134
 URL: https://issues.apache.org/jira/browse/PIO-134
 Project: PredictionIO
  Issue Type: Improvement
  Components: Documentation
Reporter: Donald Szeto






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Call for quote for the upcoming PredictionIO graduation announcement

[Donald Szeto]

Dear PredictionIO community,

With your support and contribution over the past year, the PredictionIO
project is now very close to graduating to become a top-level project. The
Apache Incubator PMC has voted positively on our proposed graduation, and
it will be included in the ASF Board Meeting on 10/18.

Once the graduation proposal passed, ASF will help make a press release
formally announcing PredictionIO's graduation. There is an opportunity to
include a few quotes from the community. If you find PredictionIO helpful
and would like to be part of the press release, please drop us a message
with your name, affiliation, and the text your quote.

Upon ASF accepting our graduation resolution on 10/18, the press release
will go out the following week. Please note that only a few quotes can be
included, so apologies in advance if yours is not included.

Regards,
Donald

Re: 2d-animated video for Artificial Intelligence

[Donald Szeto]

Hi Max,

Apache projects are non-profit. Specifically this mailing list is for
development of the project by community effort. Do not use this to
advertise your service.

Regards,
Donald

On Thu, Oct 12, 2017 at 11:51 AM Max Harrison  wrote:

> Hey !
>
> My name is Max, I'm a team leader at “Inovit” animation studio.
>
> Our company creates professional 2d animation explainer videos to deliver a
> message about your company or product to your prospects in the best form,
> which helps you attract new customers and potential clients.
>
> We’ve checked your website and we think that our services could be useful
> for you.
>
> You can find some examples of our videos in the links below:
>
> https://www.youtube.com/watch?v=0U1w0qFUD5c
>
> https://youtu.be/OdB-AbkEyvE
>
> Our portfolio: https://vimeo.com/inovitagency
>
> Let me know if you're interested in any kind of cooperation.
>
> Looking forward to hearing from you.
>
> --
> Best Regards
> Max Harrison, Team leader
> 187 E. Warm Springs Rd. Suite B398
> Las Vegas, Nevada 89119, USA
> skype: inovit_order
> Tel: +18882748845; code: 01
> http://inovitagency.com/
>

[jira] [Resolved] (PIO-133) Make sure project web site meets all requirements in Apache Project Website Branding Policy

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-133.
--
Resolution: Fixed

> Make sure project web site meets all requirements in Apache Project Website 
> Branding Policy
> ---
>
> Key: PIO-133
> URL: https://issues.apache.org/jira/browse/PIO-133
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Donald Szeto
>    Assignee: Donald Szeto
>
> Meet all requirements described in 
> https://www.apache.org/foundation/marks/pmcs



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PIO-133) Make sure project web site meets all requirements in Apache Project Website Branding Policy

[Donald Szeto (JIRA)]

Donald Szeto created PIO-133:


 Summary: Make sure project web site meets all requirements in 
Apache Project Website Branding Policy
 Key: PIO-133
 URL: https://issues.apache.org/jira/browse/PIO-133
 Project: PredictionIO
  Issue Type: Improvement
  Components: Documentation
Reporter: Donald Szeto
Assignee: Donald Szeto


Meet all requirements described in https://www.apache.org/foundation/marks/pmcs



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (PIO-101) Document usage of Plug-in of event server and engine server

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto closed PIO-101.

Resolution: Fixed

> Document usage of Plug-in of event server and engine server
> ---
>
> Key: PIO-101
> URL: https://issues.apache.org/jira/browse/PIO-101
> Project: PredictionIO
>  Issue Type: Task
>  Components: Documentation
>Reporter: Kenneth Chan
>Assignee: Naoki Takezoe
>
> see 
> http://mail-archives.apache.org/mod_mbox/incubator-predictionio-dev/201706.mbox/%3CCAF_HxLtEonOVALSQgrCRGXctAbL7eypxwG0ErHpaBJJym15j5Q%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (PIO-129) CLI document does not expand side menu

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto closed PIO-129.

Resolution: Fixed

> CLI document does not expand side menu
> --
>
> Key: PIO-129
> URL: https://issues.apache.org/jira/browse/PIO-129
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Naoki Takezoe
>Assignee: Naoki Takezoe
>Priority: Minor
>
> There are links to CLI document in the deploy section and collecting data 
> section of the side menu, but if these links are clicked, the side menu is 
> closed because these links have a hash like {{/cli/#engine-commands}}. I 
> think that such unclear navigation would confuse readers.
> https://predictionio.incubator.apache.org/cli/#engine-commands
> I propose to remove these links from the deploy section and the collecting 
> data section, and put a link to CLI document in the resource section without 
> hash. In addition, put links to the CLI reference in documents of the event 
> server and the engine server.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PIO-125) Spark 2.2 support

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-125.
--
Resolution: Fixed

> Spark 2.2 support
> -
>
> Key: PIO-125
> URL: https://issues.apache.org/jira/browse/PIO-125
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>
> Add Spark 2.2 to scalaSparkDepsVersion.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (PIO-131) Fix Apache licensing issues for doc site

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto closed PIO-131.

Resolution: Fixed

> Fix Apache licensing issues for doc site
> 
>
> Key: PIO-131
> URL: https://issues.apache.org/jira/browse/PIO-131
> Project: PredictionIO
>  Issue Type: Task
>Reporter: Chan
>Assignee: Chan
>
> Fix issues blocking graduation 
> (https://www.mail-archive.com/general@incubator.apache.org/msg61352.html)
> 1. Add links to http://apache.org as in 
> https://www.apache.org/foundation/marks/pmcs#navigation
> 2. Add instructions for checking signature of download as in 
> http://httpd.apache.org/download.cgi#verify



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (PIO-130) Remove old releases from mirrors

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto closed PIO-130.

Resolution: Fixed

> Remove old releases from mirrors
> 
>
> Key: PIO-130
> URL: https://issues.apache.org/jira/browse/PIO-130
> Project: PredictionIO
>  Issue Type: Task
>    Reporter: Donald Szeto
>    Assignee: Donald Szeto
>
> As pointed out by 
> https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E,
>  we need to remove old releases from mirrors.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PIO-130) Remove old releases from mirrors

[Donald Szeto (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIO-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16193666#comment-16193666
 ] 

Donald Szeto commented on PIO-130:
--

Removed 0.10.0-incubating and 0.11.0-incubating.

https://dist.apache.org/repos/dist/release/incubator/predictionio/

> Remove old releases from mirrors
> 
>
> Key: PIO-130
> URL: https://issues.apache.org/jira/browse/PIO-130
> Project: PredictionIO
>  Issue Type: Task
>    Reporter: Donald Szeto
>    Assignee: Donald Szeto
>
> As pointed out by 
> https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E,
>  we need to remove old releases from mirrors.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (PIO-132) Add instructions to verify download against signatures and hashes

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto closed PIO-132.

Resolution: Duplicate

> Add instructions to verify download against signatures and hashes
> -
>
> Key: PIO-132
> URL: https://issues.apache.org/jira/browse/PIO-132
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: 0.12.0-incubating
>Reporter: Donald Szeto
>    Assignee: Donald Szeto
>
> As pointed out in 
> https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E,
>  there should be instructions on how to verify downloads against signatures 
> and hashes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PIO-132) Add instructions to verify download against signatures and hashes

[Donald Szeto (JIRA)]

Donald Szeto created PIO-132:


 Summary: Add instructions to verify download against signatures 
and hashes
 Key: PIO-132
 URL: https://issues.apache.org/jira/browse/PIO-132
 Project: PredictionIO
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 0.12.0-incubating
Reporter: Donald Szeto
Assignee: Donald Szeto


As pointed out in 
https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E,
 there should be instructions on how to verify downloads against signatures and 
hashes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PIO-130) Improve project web site to meet branding requirements

[Donald Szeto (JIRA)]

Donald Szeto created PIO-130:


 Summary: Improve project web site to meet branding requirements
 Key: PIO-130
 URL: https://issues.apache.org/jira/browse/PIO-130
 Project: PredictionIO
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 0.12.0-incubating
Reporter: Donald Szeto
Assignee: Donald Szeto


As pointed out by 
https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E,
 we need to fix branding issues following 
https://www.apache.org/foundation/marks/pmcs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-128) Incorporate all 7 templates that are in Apache repositories

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-128:
-
Description: 
Current integration tests only test against a couple templates. We should 
expand our tests to include at least all 7 templates on ASF.

Also include the universal recommender as it is the most popular template in 
PIO ecosystem.

  was:Current integration tests only test against a couple templates. We should 
expand our tests to include at least all 7 templates on ASF.


> Incorporate all 7 templates that are in Apache repositories
> ---
>
> Key: PIO-128
> URL: https://issues.apache.org/jira/browse/PIO-128
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Test
>    Reporter: Donald Szeto
>
> Current integration tests only test against a couple templates. We should 
> expand our tests to include at least all 7 templates on ASF.
> Also include the universal recommender as it is the most popular template in 
> PIO ecosystem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PIO-128) Incorporate all 7 templates that are in Apache repositories

[Donald Szeto (JIRA)]

Donald Szeto created PIO-128:


 Summary: Incorporate all 7 templates that are in Apache 
repositories
 Key: PIO-128
 URL: https://issues.apache.org/jira/browse/PIO-128
 Project: PredictionIO
  Issue Type: Improvement
  Components: Test
Reporter: Donald Szeto


Current integration tests only test against a couple templates. We should 
expand our tests to include at least all 7 templates on ASF.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

[Donald Szeto]

Mars, it's fixed now.

Re: https://issues.apache.org/jira/browse/INFRA-15208

On Mon, Oct 2, 2017 at 3:37 PM, Donald Szeto <don...@apache.org> wrote:

> The build went through but the site is not reflecting the new version. I
> will open a ticket against ASF Infra to take a look.
>
> On Mon, Oct 2, 2017 at 2:47 PM, Donald Szeto <don...@apache.org> wrote:
>
>> The doc build failed at Scaladoc: https://builds.apach
>> e.org/job/PredictionIO-build-site/78/console
>>
>> And this has blocked the subsequent publish build. I'll just go ahead and
>> disable Scaladoc generation for now to get the main site updated first.
>>
>> On Mon, Oct 2, 2017 at 12:59 PM, Mars Hall <mars.h...@salesforce.com>
>> wrote:
>>
>>> Actually, I still don't see the updates for version 0.12.0.
>>>
>>> Why don't we see this "Batch Predictions" entry on the docs site?
>>>
>>> https://github.com/apache/incubator-predictionio/blob/develo
>>> p/docs/manual/data/nav/main.yml#L65
>>>
>>> When I made that change locally, that entry did appear under "Deploying
>>> an
>>> Engine" navigation section, but it's still not on the docs site:
>>>   https://predictionio.incubator.apache.org/deploy/
>>>
>>>
>>> On Mon, Oct 2, 2017 at 12:52 PM, Mars Hall <mars.h...@salesforce.com>
>>> wrote:
>>>
>>> > Thank you Chan!
>>> >
>>> > On Thu, Sep 28, 2017 at 9:02 AM, Chan Lee <chanlee...@gmail.com>
>>> wrote:
>>> >
>>> >> My apologies. The doc site has been updated now.
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > *Mars Hall
>>> > 415-818-7039 <(415)%20818-7039>
>>> > Customer Facing Architect
>>> > Salesforce Platform / Heroku
>>> > San Francisco, California
>>> >
>>> >
>>> > <http://smart.salesforce.com/sig/mars.hall//us_mb/default/link.html>
>>> >
>>>
>>>
>>>
>>> --
>>> *Mars Hall
>>> 415-818-7039
>>> Customer Facing Architect
>>> Salesforce Platform / Heroku
>>> San Francisco, California
>>>
>>>
>>> <http://smart.salesforce.com/sig/mars.hall//us_mb/default/link.html>
>>>
>>
>>
>

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

[Donald Szeto]

The build went through but the site is not reflecting the new version. I
will open a ticket against ASF Infra to take a look.

On Mon, Oct 2, 2017 at 2:47 PM, Donald Szeto <don...@apache.org> wrote:

> The doc build failed at Scaladoc: https://builds.
> apache.org/job/PredictionIO-build-site/78/console
>
> And this has blocked the subsequent publish build. I'll just go ahead and
> disable Scaladoc generation for now to get the main site updated first.
>
> On Mon, Oct 2, 2017 at 12:59 PM, Mars Hall <mars.h...@salesforce.com>
> wrote:
>
>> Actually, I still don't see the updates for version 0.12.0.
>>
>> Why don't we see this "Batch Predictions" entry on the docs site?
>>
>> https://github.com/apache/incubator-predictionio/blob/develo
>> p/docs/manual/data/nav/main.yml#L65
>>
>> When I made that change locally, that entry did appear under "Deploying an
>> Engine" navigation section, but it's still not on the docs site:
>>   https://predictionio.incubator.apache.org/deploy/
>>
>>
>> On Mon, Oct 2, 2017 at 12:52 PM, Mars Hall <mars.h...@salesforce.com>
>> wrote:
>>
>> > Thank you Chan!
>> >
>> > On Thu, Sep 28, 2017 at 9:02 AM, Chan Lee <chanlee...@gmail.com> wrote:
>> >
>> >> My apologies. The doc site has been updated now.
>> >>
>> >
>> >
>> >
>> > --
>> > *Mars Hall
>> > 415-818-7039 <(415)%20818-7039>
>> > Customer Facing Architect
>> > Salesforce Platform / Heroku
>> > San Francisco, California
>> >
>> >
>> > <http://smart.salesforce.com/sig/mars.hall//us_mb/default/link.html>
>> >
>>
>>
>>
>> --
>> *Mars Hall
>> 415-818-7039
>> Customer Facing Architect
>> Salesforce Platform / Heroku
>> San Francisco, California
>>
>>
>> <http://smart.salesforce.com/sig/mars.hall//us_mb/default/link.html>
>>
>
>

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

[Donald Szeto]

The doc build failed at Scaladoc:
https://builds.apache.org/job/PredictionIO-build-site/78/console

And this has blocked the subsequent publish build. I'll just go ahead and
disable Scaladoc generation for now to get the main site updated first.

On Mon, Oct 2, 2017 at 12:59 PM, Mars Hall  wrote:

> Actually, I still don't see the updates for version 0.12.0.
>
> Why don't we see this "Batch Predictions" entry on the docs site?
>
> https://github.com/apache/incubator-predictionio/blob/
> develop/docs/manual/data/nav/main.yml#L65
>
> When I made that change locally, that entry did appear under "Deploying an
> Engine" navigation section, but it's still not on the docs site:
>   https://predictionio.incubator.apache.org/deploy/
>
>
> On Mon, Oct 2, 2017 at 12:52 PM, Mars Hall 
> wrote:
>
> > Thank you Chan!
> >
> > On Thu, Sep 28, 2017 at 9:02 AM, Chan Lee  wrote:
> >
> >> My apologies. The doc site has been updated now.
> >>
> >
> >
> >
> > --
> > *Mars Hall
> > 415-818-7039 <(415)%20818-7039>
> > Customer Facing Architect
> > Salesforce Platform / Heroku
> > San Francisco, California
> >
> >
> > 
> >
>
>
>
> --
> *Mars Hall
> 415-818-7039
> Customer Facing Architect
> Salesforce Platform / Heroku
> San Francisco, California
>
>
> 
>

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

[Donald Szeto]

The vote passes, with 9 +1 votes (8 binding) and no -1 votes.

+1 Andrew Purtell (binding)
+1 Chan Lee (binding)
+1 Donald Szeto (binding)
+1 Jianhe Liao (non-PPMC, non-binding)
+1 Mars Hall (binding)
+1 Naoki Takezoe (binding)
+1 Shinsuke Sugaya (binding)
+1 Suneel Marthi (binding)
+1 Takako Shimamoto (binding)

Thanks all for voting. We will proceed to post our resolution to the
general incubator list for discussion.

On Wed, Sep 27, 2017 at 9:54 PM, takako shimamoto <chiboch...@gmail.com>
wrote:

> +1 binding
>
> Thanks, Donald! I really appreciate that.
>
>
> 2017-09-26 12:50 GMT+09:00 Donald Szeto <don...@apache.org>:
> > Hi all,
> >
> > Based on previous discussions (
> > https://lists.apache.org/thread.html/2b4ef7c394584988cf0c99920824af
> aa60ee4c648d5c0069b1bf55c0@%3Cdev.predictionio.apache.org%3E
> > and
> > https://lists.apache.org/thread.html/1b06e510773ee1d315728e0ce25f22
> 0c9cf7d9e8ad601ec9dba4fe1d@%3Cdev.predictionio.apache.org%3E),
> > I would like to start a formal vote on graduating PredictionIO from an
> > Incubator podling to a top level project with the following resolution.
> > This thread will be forwarded to the Incubator general mailing list.
> >
> > Once again, Salesforce has already signed and executed an assignment
> > agreement to assign the PredictionIO mark to ASF.
> >
> > The graduation process we are following is described here:
> > http://incubator.apache.org/guides/graduation.html
> >
> > Once this vote passes, a discussion will be started on Incubator general,
> > followed by a vote when a consensus there would be arrived. The vote will
> > run for at least 72 hours before closing at 9PM PST on 9/28/2017.
> >
> > Thank you all! Let's graduate.
> >
> > +1 (binding) from me.
> >
> > Regards,
> > Donald
> >
> > -
> >
> > X. Establish the Apache PredictionIO Project
> >
> >WHEREAS, the Board of Directors deems it to be in the best
> >interests of the Foundation and consistent with the
> >Foundation's purpose to establish a Project Management
> >Committee charged with the creation and maintenance of
> >open-source software, for distribution at no charge to
> >the public, related to a machine learning server built on top of
> >state-of-the-art open source stack, that enables developers to
> manage
> >and deploy production-ready predictive services for various kinds
> of
> >machine learning tasks.
> >
> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >Committee (PMC), to be known as the "Apache PredictionIO Project",
> >be and hereby is established pursuant to Bylaws of the
> >Foundation; and be it further
> >
> >RESOLVED, that the Apache PredictionIO Project be and hereby is
> >responsible for the creation and maintenance of software
> >related to a machine learning server built on top of
> >state-of-the-art open source stack, that enables developers to
> manage
> >and deploy production-ready predictive services for various kinds
> of
> >machine learning tasks;
> >and be it further
> >
> >RESOLVED, that the office of "Vice President, Apache
> PredictionIO" be
> >and hereby is created, the person holding such office to
> >serve at the direction of the Board of Directors as the chair
> >of the Apache PredictionIO Project, and to have primary
> > responsibility
> >for management of the projects within the scope of
> >    responsibility of the Apache PredictionIO Project; and be it
> further
> >
> >RESOLVED, that the persons listed immediately below be and
> >hereby are appointed to serve as the initial members of the
> >Apache PredictionIO Project:
> >
> >  * Alex Merritt <emergentor...@apache.org>
> >  * Andrew Kyle Purtell <apurt...@apache.org>
> >  * Chan Lee <chan...@apache.org>
> >  * 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>
> >  * Lars Hofhansl <la...@apache.org>
> >  * Lee Moon Soo <m...@apache.org>
> >  * Luciano Resende <lrese...@apache.org>
> >  * Marcin Ziemiński <zie...

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

[Donald Szeto]

Congrats to everyone who is part of this, and Chan for his first Apache
release!

On Wed, Sep 27, 2017 at 2:40 PM Chan Lee  wrote:

> The Apache PredictionIO team would like to announce the release of Apache
> PredictionIO 0.12.0-incubating.
>
> Release notes are here:
>
> https://github.com/apache/incubator-predictionio/blob/release/0.12.0/RELEASE.md
>
> Apache PredictionIO (incubating) is an open source Machine Learning Server
> built on top of state-of-the-art open source stack, that enables developers
> to manage and deploy production-ready predictive services for various kinds
> of machine learning tasks.
>
> More details regarding Apache PredictionIO (incubating) can be found here:
> http://predictionio.incubator.apache.org/
>
> The release artifacts can be downloaded here:
>
> https://dist.apache.org/repos/dist/release/incubator/predictionio/0.12.0-incubating/
>
> All JIRAs completed for this release are tagged with 'FixVersion =
> 0.12.0-incubating'; the JIRA release notes can be found here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12340591=12320420
>
> Thanks!
> The Apache PredictionIO Team
>
> DISCLAIMER
> Apache PredictionIO (incubating) is an effort undergoing incubation at the
> Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects. While incubation status is not necessarily a reflection of
> the completeness or stability of the code, it does indicate that the
> project has yet to be fully endorsed by the ASF.
>

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

[Donald Szeto]

Hi all,

Based on previous discussions (
https://lists.apache.org/thread.html/2b4ef7c394584988cf0c99920824afaa60ee4c648d5c0069b1bf55c0@%3Cdev.predictionio.apache.org%3E
and
https://lists.apache.org/thread.html/1b06e510773ee1d315728e0ce25f220c9cf7d9e8ad601ec9dba4fe1d@%3Cdev.predictionio.apache.org%3E),
I would like to start a formal vote on graduating PredictionIO from an
Incubator podling to a top level project with the following resolution.
This thread will be forwarded to the Incubator general mailing list.

Once again, Salesforce has already signed and executed an assignment
agreement to assign the PredictionIO mark to ASF.

The graduation process we are following is described here:
http://incubator.apache.org/guides/graduation.html

Once this vote passes, a discussion will be started on Incubator general,
followed by a vote when a consensus there would be arrived. The vote will
run for at least 72 hours before closing at 9PM PST on 9/28/2017.

Thank you all! Let's graduate.

+1 (binding) from me.

Regards,
Donald

-

X. Establish the Apache PredictionIO Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software, for distribution at no charge to
   the public, related to a machine learning server built on top of
   state-of-the-art open source stack, that enables developers to manage
   and deploy production-ready predictive services for various kinds of
   machine learning tasks.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache PredictionIO Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache PredictionIO Project be and hereby is
   responsible for the creation and maintenance of software
   related to a machine learning server built on top of
   state-of-the-art open source stack, that enables developers to manage
   and deploy production-ready predictive services for various kinds of
   machine learning tasks;
   and be it further

   RESOLVED, that the office of "Vice President, Apache PredictionIO" be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache PredictionIO Project, and to have primary
responsibility
   for management of the projects within the scope of
   responsibility of the Apache PredictionIO Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache PredictionIO Project:

 * Alex Merritt <emergentor...@apache.org>
 * Andrew Kyle Purtell <apurt...@apache.org>
 * Chan Lee <chan...@apache.org>
 * 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>
 * Lars Hofhansl <la...@apache.org>
 * Lee Moon Soo <m...@apache.org>
 * Luciano Resende <lrese...@apache.org>
 * Marcin Ziemiński <zie...@apache.org>
 * Marco Vivero <mviv...@apache.org>
 * Mars Hall <m...@apache.org>
 * Matthew Tovbin <tovb...@apache.org>
 * Naoki Takezoe <take...@apache.org>
 * Pat Ferrel <p...@apache.org>
 * Paul Li <pau...@apache.org>
 * Shinsuke Sugaya <shins...@apache.org>
 * Simon Chan <sim...@apache.org>
 * Takahiro Hagino <hag...@apache.org>
 * Takako Shimamoto <shimam...@apache.org>
 * Tamas Jambor <tjam...@apache.org>
 * Tom Chan <tc...@apache.org>
 * Vitaly Gordon <vit...@apache.org>
 * Xiangrui Meng <m...@apache.org>
 * Xusen Yin <y...@apache.org>
 * Yevgeny Khodorkovsky <y...@apache.org>

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Donald Szeto
   be appointed to the office of Vice President, Apache PredictionIO, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the initial Apache PredictionIO PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache PredictionIO Project; and be

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

[Donald Szeto]

Thank you. I will move this forward to a formal vote.

On Fri, Sep 22, 2017 at 2:30 PM, Mars Hall <mars.h...@salesforce.com> wrote:

> Thank you for creating this resolution Donald.
>
> I move that we start the vote, pending any additional feedback from the
> group.
>
> Best regards,
>
> On Thu, Sep 21, 2017 at 12:19 PM, Andrew Purtell <apurt...@apache.org>
> wrote:
>
> > This looks great Donald, and I'm so glad you accepted the role of Chair.
> >
> > This part of the Special Order will establish the project description
> text
> > which must appear at the top of every report to the Board:
> >
> > [...] software related to *a machine learning server built on top of
> > state-of-the-art open source stack, that enables developers to manage and
> > deploy production-ready predictive services for various kinds of machine
> > learning tasks*
> >
> >
> > It is in effect the Apache in-house elevator pitch to other projects and
> > PMC or anyone reading the reports. This is the opportunity to improve
> this
> > description, if desired. It could also be fine as-is.
> >
> >
> > On Thu, Sep 21, 2017 at 10:29 AM, Donald Szeto <don...@apache.org>
> wrote:
> >
> > > Hi all,
> > >
> > > Based on the previous discussion (
> > > https://lists.apache.org/thread.html/2b4ef7c394584988cf0c99920824af
> > > aa60ee4c648d5c0069b1bf55c0@%3Cdev.predictionio.apache.org%3E),
> > > I would like to start discussing a graduation resolution and reach a
> > > consent before starting a community vote on the following. Please read
> > > carefully the resolution, and voice any concerns you may have. If you
> > are a
> > > current PMC member, please make sure your name is listed unless you
> have
> > > already asked to be excluded. We will start an official community vote
> > when
> > > a consent is reached.
> > >
> > > Regarding the PredictionIO trademark assignment, Salesforce has signed
> > and
> > > executed an assignment agreement, and is only pending ASF to
> countersign.
> > >
> > > The graduation process we are following is described here:
> > > http://incubator.apache.org/guides/graduation.html
> > >
> > > Thank you all! Let's graduate.
> > >
> > > Regards,
> > > Donald
> > >
> > > -
> > >
> > > X. Establish the Apache PredictionIO Project
> > >
> > >WHEREAS, the Board of Directors deems it to be in the best
> > >interests of the Foundation and consistent with the
> > >Foundation's purpose to establish a Project Management
> > >Committee charged with the creation and maintenance of
> > >open-source software, for distribution at no charge to
> > >the public, related to a machine learning server built on top of
> > >state-of-the-art open source stack, that enables developers to
> > > manage
> > >and deploy production-ready predictive services for various
> kinds
> > of
> > >machine learning tasks.
> > >
> > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >Committee (PMC), to be known as the "Apache PredictionIO
> Project",
> > >be and hereby is established pursuant to Bylaws of the
> > >Foundation; and be it further
> > >
> > >RESOLVED, that the Apache PredictionIO Project be and hereby is
> > >responsible for the creation and maintenance of software
> > >related to a machine learning server built on top of
> > >state-of-the-art open source stack, that enables developers to
> > > manage
> > >and deploy production-ready predictive services for various
> kinds
> > of
> > >machine learning tasks;
> > >and be it further
> > >
> > >RESOLVED, that the office of "Vice President, Apache
> PredictionIO"
> > > be
> > >and hereby is created, the person holding such office to
> > >serve at the direction of the Board of Directors as the chair
> > >of the Apache PredictionIO Project, and to have primary
> > > responsibility
> > >for management of the projects within the scope of
> > >responsibility of the Apache PredictionIO Project; and be it
> > further
> > >
> > >RESOLVED, that the persons listed immediately below be and

[DISCUSS] Resolution to create a TLP from graduating Incubator podling

[Donald Szeto]

Hi all,

Based on the previous discussion (
https://lists.apache.org/thread.html/2b4ef7c394584988cf0c99920824afaa60ee4c648d5c0069b1bf55c0@%3Cdev.predictionio.apache.org%3E),
I would like to start discussing a graduation resolution and reach a
consent before starting a community vote on the following. Please read
carefully the resolution, and voice any concerns you may have. If you are a
current PMC member, please make sure your name is listed unless you have
already asked to be excluded. We will start an official community vote when
a consent is reached.

Regarding the PredictionIO trademark assignment, Salesforce has signed and
executed an assignment agreement, and is only pending ASF to countersign.

The graduation process we are following is described here:
http://incubator.apache.org/guides/graduation.html

Thank you all! Let's graduate.

Regards,
Donald

-

X. Establish the Apache PredictionIO Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software, for distribution at no charge to
   the public, related to a machine learning server built on top of
   state-of-the-art open source stack, that enables developers to manage
   and deploy production-ready predictive services for various kinds of
   machine learning tasks.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache PredictionIO Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache PredictionIO Project be and hereby is
   responsible for the creation and maintenance of software
   related to a machine learning server built on top of
   state-of-the-art open source stack, that enables developers to manage
   and deploy production-ready predictive services for various kinds of
   machine learning tasks;
   and be it further

   RESOLVED, that the office of "Vice President, Apache PredictionIO" be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache PredictionIO Project, and to have primary
responsibility
   for management of the projects within the scope of
   responsibility of the Apache PredictionIO Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache PredictionIO Project:

 * Alex Merritt <emergentor...@apache.org>
 * Andrew Kyle Purtell <apurt...@apache.org>
 * Chan Lee <chan...@apache.org>
 * 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>
 * Lars Hofhansl <la...@apache.org>
 * Lee Moon Soo <m...@apache.org>
 * Luciano Resende <lrese...@apache.org>
 * Marcin Ziemiński <zie...@apache.org>
 * Marco Vivero <mviv...@apache.org>
 * Mars Hall <m...@apache.org>
 * Matthew Tovbin <tovb...@apache.org>
 * Naoki Takezoe <take...@apache.org>
 * Pat Ferrel <p...@apache.org>
 * Paul Li <pau...@apache.org>
 * Shinsuke Sugaya <shins...@apache.org>
 * Simon Chan <sim...@apache.org>
 * Takahiro Hagino <hag...@apache.org>
 * Takako Shimamoto <shimam...@apache.org>
 * Tamas Jambor <tjam...@apache.org>
 * Tom Chan <tc...@apache.org>
 * Vitaly Gordon <vit...@apache.org>
 * Xiangrui Meng <m...@apache.org>
 * Xusen Yin <y...@apache.org>
 * Yevgeny Khodorkovsky <y...@apache.org>

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Donald Szeto
   be appointed to the office of Vice President, Apache PredictionIO, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the initial Apache PredictionIO PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache PredictionIO Project; and be it further

   RESOLVED, that the Apache PredictionIO Project be and hereby
   is tasked with the migration and rationalization of the Apache
  

[jira] [Commented] (PIO-68) Port UR template to Java

[Donald Szeto (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIO-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172398#comment-16172398
 ] 

Donald Szeto commented on PIO-68:
-

Cornell students implemented this: 
https://github.com/cbora/predictionio-template-java-universal-recommender

> Port UR template to Java
> 
>
> Key: PIO-68
> URL: https://issues.apache.org/jira/browse/PIO-68
> Project: PredictionIO
>  Issue Type: New Feature
>  Components: Templates
>Reporter: Sara Asher
>Assignee: Donald Szeto
> Fix For: 0.12.0-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-67) Add link for guide for creating java templates to documentation

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-67:

Labels: newbie  (was: )

> Add link for guide for creating java templates to documentation
> ---
>
> Key: PIO-67
> URL: https://issues.apache.org/jira/browse/PIO-67
> Project: PredictionIO
>  Issue Type: Task
>  Components: Documentation
>Reporter: Sara Asher
>Priority: Minor
>  Labels: newbie
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (PIO-36) Use Spark standalone cluster in integration tests

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto reassigned PIO-36:
---

Assignee: Chan
Target Version/s: 0.13.0-incubating

> Use Spark standalone cluster in integration tests
> -
>
> Key: PIO-36
> URL: https://issues.apache.org/jira/browse/PIO-36
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Test
>Reporter: Marcin Ziemiński
>Assignee: Chan
>Priority: Minor
>
> Although Spark master and worker are executed inside the docker image that 
> run integration tests, no tests actually make use of them. Only a default 
> local spark implementation is used. Setting a --master to a living cluster 
> would resemble a real world cases better and also be more reliable.
> The python framework has to be updated to fix this issue, which should be 
> just a matter of adding a few lines. We can make it an option in the tests to 
> set up the master.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-7) document use of SSL

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-7:
---
Labels: newbie  (was: )

> document use of SSL
> ---
>
> Key: PIO-7
> URL: https://issues.apache.org/jira/browse/PIO-7
> Project: PredictionIO
>  Issue Type: Sub-task
>  Components: Documentation
>Reporter: Pat Ferrel
>Assignee: Donald Szeto
>  Labels: newbie
>
> Document how to enable/disable SSL and manage certs, once pio-1 is ready



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-7) document use of SSL

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-7:
---
Component/s: Documentation

> document use of SSL
> ---
>
> Key: PIO-7
> URL: https://issues.apache.org/jira/browse/PIO-7
> Project: PredictionIO
>  Issue Type: Sub-task
>  Components: Documentation
>Reporter: Pat Ferrel
>Assignee: Donald Szeto
>  Labels: newbie
>
> Document how to enable/disable SSL and manage certs, once pio-1 is ready



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (PIO-7) document use of SSL

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto reassigned PIO-7:
--

Assignee: (was: Donald Szeto)

> document use of SSL
> ---
>
> Key: PIO-7
> URL: https://issues.apache.org/jira/browse/PIO-7
> Project: PredictionIO
>  Issue Type: Sub-task
>  Components: Documentation
>Reporter: Pat Ferrel
>  Labels: newbie
>
> Document how to enable/disable SSL and manage certs, once pio-1 is ready



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PIO-122) always get Error initializing storage client for source ELASTICSEARCH in 0.11 when pio train

[Donald Szeto (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIO-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170987#comment-16170987
 ] 

Donald Szeto commented on PIO-122:
--

[~glorysdj], since you have closed this, did you find a solution?

> always get Error initializing storage client for source ELASTICSEARCH in 0.11 
> when pio train
> 
>
> Key: PIO-122
> URL: https://issues.apache.org/jira/browse/PIO-122
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: dongjie.shi
>
> Always get this error when I try to run PIO train to test a local PIO with 
> HBase and Elasticsearch.
> [ERROR] [Storage$] Error initializing storage client for source ELASTICSEARCH
> Exception in thread "main" 
> org.apache.predictionio.data.storage.StorageClientException: Data source 
> ELASTICSEARCH was not properly initialized.
> at 
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at 
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at scala.Option.getOrElse(Option.scala:120)
> at 
> org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
> at 
> org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
> at 
> org.apache.predictionio.data.storage.Storage$.getMetaDataEngineInstances(Storage.scala:371)
> at 
> org.apache.predictionio.workflow.CreateWorkflow$.main(CreateWorkflow.scala:247)
> at 
> org.apache.predictionio.workflow.CreateWorkflow.main(CreateWorkflow.scala)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:731)
> at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:181)
> at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:206)
> at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:121)
> at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
> It seems that every component is ok in pio staus:
> [INFO] [Management$] Your system is all ready to go.
> And about the configurations in pio-env.conf, I have checked them for many 
> times.
> PIO_FS_BASEDIR=${HOME}/.pio_store
> PIO_FS_ENGINESDIR=${PIO_FS_BASEDIR}/engines
> PIO_FS_TMPDIR=${PIO_FS_BASEDIR}/tmp
> SPARK_HOME=${SPARK_HOME}
> HBASE_CONF_DIR=${HBASE_HOME}/conf
> PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta
> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH
> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event
> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=HBASE
> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model
> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=LOCALFS
> PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch
> PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=predictionio
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost
> PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=${ELASTICSEARCH_HOME}
> PIO_STORAGE_SOURCES_LOCALFS_TYPE=localfs
> PIO_STORAGE_SOURCES_LOCALFS_PATH=${PIO_FS_BASEDIR}/models
> PIO_STORAGE_SOURCES_HBASE_TYPE=hbase
> PIO_STORAGE_SOURCES_HBASE_HOME=${HBASE_HOME}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Graduation to TLP

[Donald Szeto]

Goal is the follow Apache's convention, so I think we will proceed with the
same list, excluding those who have requested to be excluded.

On Mon, Sep 18, 2017 at 11:00 AM Luciano Resende <luckbr1...@gmail.com>
wrote:

> On Mon, Aug 28, 2017 at 10:20 PM, Donald Szeto <don...@apache.org> wrote:
>
> > Hi all,
> >
> > Since the ASF Board meeting in May (
> > http://apache.org/foundation/records/minutes/2017/board_
> > minutes_2017_05_17.txt),
> > PredictionIO has been considered nearing graduation and I think we are
> > almost there. I am kickstarting this thread so that we can discuss on
> these
> > 3 things:
> >
> > 1. Does the development community feel ready to graduate?
> >
>
> +1
>
>
> > 2. If we are to graduate, who should we include in the list of the
> initial
> > PMC?
> >
>
> Not sure about the goal of the question, but usually the PPMC will become
> the PMC unless you had done explicit committer versus ppmc votes or folks
> explicitly request to leave.
>
>
> > 3. If we are to graduate, who should be the VP of the initial PMC?
> >
> > These points are relevant for graduation. Please take a look at the
> > official graduation guide:
> > http://incubator.apache.org/guides/graduation.html.
> >
> > In addition, Sara and I have been working to transfer the PredictionIO
> > trademark to the ASF. We will keep you updated with our progress.
> >
> > I would also like to propose to cut a 0.12.0 release by merging JIRAs
> that
> > have a target version set to 0.12.0-incubating for graduation. 0.12.0
> will
> > contain cleanups for minor license and copyright issues that were pointed
> > out in previous releases by IPMC.
> >
> > Let me know what you think.
> >
> > Regards,
> > Donald
> >
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

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

[Donald Szeto]

+1 binding

I checked:
- Downloads matched PGP signatures, MD5, and SHA512
- Binaries working out of the box
- Test results on Travis
- Maven artifacts structure in good shape

Thanks, Chan!

On Sun, Sep 17, 2017 at 11:31 AM, Chan Lee  wrote:

> This is the vote for 0.12.0 of Apache PredictionIO (incubating).
>
> The vote will run for at least 72 hours and will close on Sep 20th, 2017.
>
> The release candidate artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.12.0-
> incubating-rc3
>
> Test results of RC3 can be found here:
> https://travis-ci.org/apache/incubator-predictionio/builds/276558626
>
> Maven artifacts are built from the release candidate artifacts above, and
> are provided as convenience for testing with engine templates. The Maven
> artifacts are provided at the Maven staging repo here:
> https://repository.apache.org/content/repositories/
> orgapachepredictionio-1021/
>
> All JIRAs completed for this release are tagged with 'FixVersion =
> 0.12.0-incubating'. You can view them here: https://issues.apache.or
> g/jira/secure/ReleaseNote.jspa?version=12340591=12320420
>
> The artifacts have been signed with Key: ytX8GpWv
>
> Please vote accordingly:
>
> [ ] +1, accept RC as the official 0.12.0 release
> [ ] -1, do not accept RC as the official 0.12.0 release because...
>

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

[Donald Szeto]

That should be fine. Chan, the binary distribution package should be
treated the same as what we are doing with publishing Maven artifacts
(classified as convenience binaries by ASF). Instead of going to Nexus,
they need to go alongside the source (i.e. SVN). We will similarly need to
produce PGP signature, MD5 and SHA512 for the binary distribution.

On Sat, Sep 16, 2017 at 5:13 AM Naoki Takezoe  wrote:

> Can we publish the binary distribution which is built by
> make-distribution.sh together?
> It would makes possible newbies to try PredictionIO in default
> combination without build from source code.
>
> I fixed make-distribution.sh to include a license file in PIO-69, so
> it's ready to be released.
>
> https://github.com/apache/incubator-predictionio/commit/2a4ecf3bc873a5fc5532c1b95166b9232e82d525#diff-a482fdd2c39acfb78529c30718c3c9ab
>
> 2017-09-15 6:06 GMT+09:00 Chan Lee :
> > This is the vote for 0.12.0 of Apache PredictionIO (incubating).
> >
> > The vote will run for at least 72 hours and will close on Sep 17th, 2017.
> >
> > The release candidate artifacts can be downloaded here:
> > https://dist.apache.org/repos/dist/dev/incubator/predi
> > ctionio/0.12.0-incubating-rc2
> >
> > Test results of RC1 can be found here: https://travis-ci.org/ap
> > ache/incubator-predictionio/builds/275634960
> >
> > Maven artifacts are built from the release candidate artifacts above, and
> > are provided as convenience for testing with engine templates. The Maven
> > artifacts are provided at the Maven staging repo here:
> >
> https://repository.apache.org/content/repositories/orgapachepredictionio-1020
> >
> > All JIRAs completed for this release are tagged with 'FixVersion =
> > 0.12.0-incubating'. You can view them here: https://issues.apache.or
> > g/jira/secure/ReleaseNote.jspa?version=12340591=12320420
> >
> > The artifacts have been signed with Key: ytX8GpWv
> >
> > Please vote accordingly:
> >
> > [ ] +1, accept RC as the official 0.12.0 release
> > [ ] -1, do not accept RC as the official 0.12.0 release because...
>
>
>
> --
> Naoki Takezoe
>

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

[Donald Szeto]

Votes are tied to tag/commit by ASF convention, so a new RC and vote will
be required.

On Fri, Sep 15, 2017 at 10:57 AM Mars Hall <mars.h...@salesforce.com> wrote:

> I just opened a release notes PR against apache:release/0.12.0, because
> that seems to be the right place.
>
> Chan, will that work okay with the release process?
>
> On Fri, Sep 15, 2017 at 10:20 AM, Mars Hall <mars.h...@salesforce.com>
> wrote:
>
> > Also, I'd love to directly link the PIO-* issue numbers to JIRA.
> >
> > On Fri, Sep 15, 2017 at 10:19 AM, Mars Hall <mars.h...@salesforce.com>
> > wrote:
> >
> >> RC2 is working perfectly.
> >>
> >> I see a few issues with the releases notes:
> >>
> >>
> >>- PIO-95 should be "Raised request timeout for REST API to
> 35-seconds"
> >>- PIO-102, PIO-106, PIO-117, PIO-118, PIO-120 actually includes a
> >>breaking change to Elasticsearch 5.x StorageClient interface. I
> think these
> >>should be enumerated more explicitly with one of them called out in a
> >>"Breaking changes" section.
> >>
> >> May I revise RELEASE.md on develop to fix these issues? Does that
> require
> >> restarting vote for an RC3?
> >>
> >>
> >> On Thu, Sep 14, 2017 at 11:49 PM, Donald Szeto <don...@apache.org>
> wrote:
> >>
> >>> I believe those are fixed by PIO-60, PIO-62 and PIO-63 in the release
> >>> notes.
> >>>
> >>> +1 binding from me
> >>>
> >>> On Thu, Sep 14, 2017 at 2:13 PM Pat Ferrel <p...@occamsmachete.com>
> >>> wrote:
> >>>
> >>> > 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 2:06 PM, Chan Lee <chanlee...@gmail.com> wrote:
> >>> >
> >>> > This is the vote for 0.12.0 of Apache PredictionIO (incubating).
> >>> >
> >>> > The vote will run for at least 72 hours and will close on Sep 17th,
> >>> 2017.
> >>> >
> >>> > The release candidate artifacts can be downloaded here:
> >>> > https://dist.apache.org/repos/dist/dev/incubator/predi
> >>> > ctionio/0.12.0-incubating-rc2
> >>> >
> >>> > Test results of RC1 can be found here: https://travis-ci.org/ap
> >>> > ache/incubator-predictionio/builds/275634960
> >>> >
> >>> > Maven artifacts are built from the release candidate artifacts above,
> >>> and
> >>> > are provided as convenience for testing with engine templates. The
> >>> Maven
> >>> > artifacts are provided at the Maven staging repo here:
> >>> >
> >>> > https://repository.apache.org/content/repositories/orgapache
> >>> predictionio-1020
> >>> >
> >>> > All JIRAs completed for this release are tagged with 'FixVersion =
> >>> > 0.12.0-incubating'. You can view them here: https://issues.apache.or
> >>> > g/jira/secure/ReleaseNote.jspa?version=12340591=12320420
> >>> >
> >>> > The artifacts have been signed with Key: ytX8GpWv
> >>> >
> >>> > Please vote accordingly:
> >>> >
> >>> > [ ] +1, accept RC as the official 0.12.0 release
> >>> > [ ] -1, do not accept RC as the official 0.12.0 release because...
> >>> >
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> *Mars Hall
> >> 415-818-7039 <(415)%20818-7039>
> >> Customer Facing Architect
> >> Salesforce Platform / Heroku
> >> San Francisco, California
> >>
> >
> >
> >
> > --
> > *Mars Hall
> > 415-818-7039 <(415)%20818-7039>
> > Customer Facing Architect
> > Salesforce Platform / Heroku
> > San Francisco, California
> >
>
>
>
> --
> *Mars Hall
> 415-818-7039
> Customer Facing Architect
> Salesforce Platform / Heroku
> San Francisco, California
>

[jira] [Commented] (PIO-122) always get Error initializing storage client for source ELASTICSEARCH in 0.11 when pio train

[Donald Szeto (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIO-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167425#comment-16167425
 ] 

Donald Szeto commented on PIO-122:
--

Can you provide information on
* how you built PIO 0.11
* the template you are using
* the {{conf/pio-env.sh}} of your PIO 0.11 build
* Elasticsearch version
* detail error message in {{pio.log}} where you run {{pio train}}
?

> always get Error initializing storage client for source ELASTICSEARCH in 0.11 
> when pio train
> 
>
> Key: PIO-122
> URL: https://issues.apache.org/jira/browse/PIO-122
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: dongjie.shi
>
> Always get this error when I try to run PIO train to test a local PIO with 
> HBase and Elasticsearch.
> [ERROR] [Storage$] Error initializing storage client for source ELASTICSEARCH
> Exception in thread "main" 
> org.apache.predictionio.data.storage.StorageClientException: Data source 
> ELASTICSEARCH was not properly initialized.
> at 
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at 
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at scala.Option.getOrElse(Option.scala:120)
> at 
> org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
> at 
> org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
> at 
> org.apache.predictionio.data.storage.Storage$.getMetaDataEngineInstances(Storage.scala:371)
> at 
> org.apache.predictionio.workflow.CreateWorkflow$.main(CreateWorkflow.scala:247)
> at 
> org.apache.predictionio.workflow.CreateWorkflow.main(CreateWorkflow.scala)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:731)
> at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:181)
> at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:206)
> at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:121)
> at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
> It seems that every component is ok in pio staus:
> [INFO] [Management$] Your system is all ready to go.
> And about the configurations in pio-env.conf, I have checked them for many 
> times.
> PIO_FS_BASEDIR=${HOME}/.pio_store
> PIO_FS_ENGINESDIR=${PIO_FS_BASEDIR}/engines
> PIO_FS_TMPDIR=${PIO_FS_BASEDIR}/tmp
> SPARK_HOME=${SPARK_HOME}
> HBASE_CONF_DIR=${HBASE_HOME}/conf
> PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta
> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH
> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event
> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=HBASE
> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model
> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=LOCALFS
> PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch
> PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=predictionio
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost
> PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=${ELASTICSEARCH_HOME}
> PIO_STORAGE_SOURCES_LOCALFS_TYPE=localfs
> PIO_STORAGE_SOURCES_LOCALFS_PATH=${PIO_FS_BASEDIR}/models
> PIO_STORAGE_SOURCES_HBASE_TYPE=hbase
> PIO_STORAGE_SOURCES_HBASE_HOME=${HBASE_HOME}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Donald Szeto]

I believe those are fixed by PIO-60, PIO-62 and PIO-63 in the release notes.

+1 binding from me

On Thu, Sep 14, 2017 at 2:13 PM Pat Ferrel  wrote:

> 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 2:06 PM, Chan Lee  wrote:
>
> This is the vote for 0.12.0 of Apache PredictionIO (incubating).
>
> The vote will run for at least 72 hours and will close on Sep 17th, 2017.
>
> The release candidate artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/dev/incubator/predi
> ctionio/0.12.0-incubating-rc2
>
> Test results of RC1 can be found here: https://travis-ci.org/ap
> ache/incubator-predictionio/builds/275634960
>
> Maven artifacts are built from the release candidate artifacts above, and
> are provided as convenience for testing with engine templates. The Maven
> artifacts are provided at the Maven staging repo here:
>
> https://repository.apache.org/content/repositories/orgapachepredictionio-1020
>
> All JIRAs completed for this release are tagged with 'FixVersion =
> 0.12.0-incubating'. You can view them here: https://issues.apache.or
> g/jira/secure/ReleaseNote.jspa?version=12340591=12320420
>
> The artifacts have been signed with Key: ytX8GpWv
>
> Please vote accordingly:
>
> [ ] +1, accept RC as the official 0.12.0 release
> [ ] -1, do not accept RC as the official 0.12.0 release because...
>
>

[jira] [Updated] (PIO-59) "pio app new" sometimes takes long time

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-59:

Component/s: Core

> "pio app new" sometimes takes long time
> ---
>
> Key: PIO-59
> URL: https://issues.apache.org/jira/browse/PIO-59
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Shinsuke Sugaya
>Priority: Minor
> Fix For: 0.12.0-incubating
>
>
> Some users reported this problem in user ML, and I also encountered it.
> Checking stack traces, I think the cause is an entropy shortage for 
> /dev/random.
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7fc94803f800 nid=0x49a9 runnable 
> [0x7fc94fa1b000]
>java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at 
> sun.security.provider.NativePRNG$RandomIO.readFully(NativePRNG.java:424)
> at 
> sun.security.provider.NativePRNG$RandomIO.ensureBufferValid(NativePRNG.java:525)
> at 
> sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:544)
> - locked <0x0003d34e8a48> (a java.lang.Object)
> at 
> sun.security.provider.NativePRNG$RandomIO.access$400(NativePRNG.java:331)
> at 
> sun.security.provider.NativePRNG$Blocking.engineNextBytes(NativePRNG.java:268)
> at java.security.SecureRandom.nextBytes(SecureRandom.java:468)
> at 
> org.apache.predictionio.data.storage.AccessKeys$class.generateKey(AccessKeys.scala:71)
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.generateKey(ESAccessKeys.scala:40)
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.insert(ESAccessKeys.scala:60)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:71)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:62)
> at scala.Option.map(Option.scala:145)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:62)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:55)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.predictionio.tools.commands.App$.create(App.scala:55)
> at 
> org.apache.predictionio.tools.console.Pio$App$.create(Pio.scala:172)
> at 
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:683)
> at 
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:626)
> at scala.Option.map(Option.scala:145)
> at 
> org.apache.predictionio.tools.console.Console$.main(Console.scala:626)
> at org.apache.predictionio.tools.console.Console.main(Console.scala)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-59) "pio app new" sometimes takes long time

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-59:

Fix Version/s: 0.12.0-incubating

> "pio app new" sometimes takes long time
> ---
>
> Key: PIO-59
> URL: https://issues.apache.org/jira/browse/PIO-59
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Shinsuke Sugaya
>Priority: Minor
> Fix For: 0.12.0-incubating
>
>
> Some users reported this problem in user ML, and I also encountered it.
> Checking stack traces, I think the cause is an entropy shortage for 
> /dev/random.
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7fc94803f800 nid=0x49a9 runnable 
> [0x7fc94fa1b000]
>java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at 
> sun.security.provider.NativePRNG$RandomIO.readFully(NativePRNG.java:424)
> at 
> sun.security.provider.NativePRNG$RandomIO.ensureBufferValid(NativePRNG.java:525)
> at 
> sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:544)
> - locked <0x0003d34e8a48> (a java.lang.Object)
> at 
> sun.security.provider.NativePRNG$RandomIO.access$400(NativePRNG.java:331)
> at 
> sun.security.provider.NativePRNG$Blocking.engineNextBytes(NativePRNG.java:268)
> at java.security.SecureRandom.nextBytes(SecureRandom.java:468)
> at 
> org.apache.predictionio.data.storage.AccessKeys$class.generateKey(AccessKeys.scala:71)
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.generateKey(ESAccessKeys.scala:40)
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.insert(ESAccessKeys.scala:60)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:71)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:62)
> at scala.Option.map(Option.scala:145)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:62)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:55)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.predictionio.tools.commands.App$.create(App.scala:55)
> at 
> org.apache.predictionio.tools.console.Pio$App$.create(Pio.scala:172)
> at 
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:683)
> at 
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:626)
> at scala.Option.map(Option.scala:145)
> at 
> org.apache.predictionio.tools.console.Console$.main(Console.scala:626)
> at org.apache.predictionio.tools.console.Console.main(Console.scala)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-59) "pio app new" sometimes takes long time

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-59:

Affects Version/s: 0.11.0-incubating

> "pio app new" sometimes takes long time
> ---
>
> Key: PIO-59
> URL: https://issues.apache.org/jira/browse/PIO-59
> Project: PredictionIO
>  Issue Type: Improvement
>Affects Versions: 0.11.0-incubating
>Reporter: Shinsuke Sugaya
>Priority: Minor
>
> Some users reported this problem in user ML, and I also encountered it.
> Checking stack traces, I think the cause is an entropy shortage for 
> /dev/random.
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7fc94803f800 nid=0x49a9 runnable 
> [0x7fc94fa1b000]
>java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at 
> sun.security.provider.NativePRNG$RandomIO.readFully(NativePRNG.java:424)
> at 
> sun.security.provider.NativePRNG$RandomIO.ensureBufferValid(NativePRNG.java:525)
> at 
> sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:544)
> - locked <0x0003d34e8a48> (a java.lang.Object)
> at 
> sun.security.provider.NativePRNG$RandomIO.access$400(NativePRNG.java:331)
> at 
> sun.security.provider.NativePRNG$Blocking.engineNextBytes(NativePRNG.java:268)
> at java.security.SecureRandom.nextBytes(SecureRandom.java:468)
> at 
> org.apache.predictionio.data.storage.AccessKeys$class.generateKey(AccessKeys.scala:71)
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.generateKey(ESAccessKeys.scala:40)
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.insert(ESAccessKeys.scala:60)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:71)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:62)
> at scala.Option.map(Option.scala:145)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:62)
> at 
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:55)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.predictionio.tools.commands.App$.create(App.scala:55)
> at 
> org.apache.predictionio.tools.console.Pio$App$.create(Pio.scala:172)
> at 
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:683)
> at 
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:626)
> at scala.Option.map(Option.scala:145)
> at 
> org.apache.predictionio.tools.console.Console$.main(Console.scala:626)
> at org.apache.predictionio.tools.console.Console.main(Console.scala)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Graduation to TLP

[Donald Szeto]

It would be my pleasure to pick up TLP Chair responsibilities if nobody
objects.

Andrew, it would be really great and beneficial to the community if you
could stay on mentoring as PMC of the new TLP. Could you also help update
the project status page on the incubator site please?

I will reference other podling's graduation proposal and draft a board
resolution.

On Thu, Sep 7, 2017 at 1:26 PM, Andrew Purtell <andrew.purt...@gmail.com>
wrote:

> Donald would be great.
> Donald - please think about it.
>
> It was suggested privately to me that I stay on from mentoring as PMC. If
> you'll have me, I would be glad to help the new TLP as/if needed.
>
>
> > On Sep 7, 2017, at 6:07 PM, Pat Ferrel <p...@occamsmachete.com> wrote:
> >
> > This has been an informal poll and it looks like people are ready. I
> suggest we push for graduation after the next release, which will be done
> by someone not Donald, I think we have 2 volunteers? I think this will be a
> requirement since it’s been mentioned by several IPMC members.
> >
> > I’d like to think several people could be our candidate VP but since
> most of them are too busy and since we have another great candidate in
> Donald, I’d like to nominate him for TLP Chair/VP.
> >
> > I’d suggest we poll the committers and PMC members to see if any want
> out of the TLP, and otherwise go with the current list. We should try to
> add any committers that are ready before the graduation push, the more the
> better to the IPMC.
> >
> > We should put this in a proposal and get mentors feedback before
> applying since mentors are also IPMC members.
> >
> > Andy has mentioned several choices for convention that we should
> discuss, like our choice of git flow for commit process. He mentioned
> rotating Chair, which seems better suited to a larger project IMO but
> please chime in if you like the idea.
> >
> > If that is all clear we have to release, have a podling vote, then have
> the IPMC vote. If there is anything else regarding how we are run speak up
> now.
> >
> >
> > On Sep 7, 2017, at 5:01 AM, takako shimamoto <chiboch...@gmail.com>
> wrote:
> >
> > I'd like to remain as committer and contribute my humble efforts to
> > the prosperity of the project.
> >
> >> I propose we stay with the current PMC and committer list unless
> someone 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 removing people unless they
> prove the exception. AFAIK this generally does not happen in ASF. I’m
> certainly not aware of the process except that it is easier in moving from
> podling to TLP.  You prove some worthiness and once that’s done, it’s done.
> A poll might just ask project members if they want to be removed. I have
> seen people ask to be removed from PMC and also “go emeritus” and those are
> cases of the individuals making the choice.
> >>
> >> So to settle the role call issue I propose we stay with the current PMC
> and committer list unless someone wants to remove themselves.
> >>
> >> As to maturity I agree with Donald that the checklist is heavy in our
> favor.
> >>
> >>
> >> On Sep 5, 2017, at 11:16 AM, Simon Chan <si...@salesforce.com> wrote:
> >>
> >> +1 for graduation
> >>
> >>> On Tue, Sep 5, 2017 at 10:32 AM, Donald Szeto <don...@apache.org>
> wrote:
> >>>
> >>> Thanks for the clarification Pat! It always help to have Apache
> veterans to
> >>> provide historical context to these processes.
> >>>
> >>> As for me, I'd like to remain as PMC and committer.
> >>>
> >>> I like the idea of polling the current committers and PMC, but like you
> >>> said, most of them got pretty busy and may not be reading mailing list
> in a
> >>> while. Maybe let me try a shout out here and see if anyone would
> >>> acknowledge it, so that we know whether a poll will be effective.
> >>>
> >>> *>> If you're a PMC or committer who see this line but hasn't been
> replying
> >>> this thread, please acknowledge. <<*
> >>>
> >>> Regarding the maturity model, this is my perception right now:
> >>> - CD10, CD20, CD30, CD40 (and we start to have CD50 as well)
> >>> - LC10, LC20, LC30, LC40, LC50
> >>

Re: Graduation to TLP

[Donald Szeto]

Thanks for the clarification Pat! It always help to have Apache veterans to
provide historical context to these processes.

As for me, I'd like to remain as PMC and committer.

I like the idea of polling the current committers and PMC, but like you
said, most of them got pretty busy and may not be reading mailing list in a
while. Maybe let me try a shout out here and see if anyone would
acknowledge it, so that we know whether a poll will be effective.

*>> If you're a PMC or committer who see this line but hasn't been replying
this thread, please acknowledge. <<*

Regarding the maturity model, this is my perception right now:
- CD10, CD20, CD30, CD40 (and we start to have CD50 as well)
- LC10, LC20, LC30, LC40, LC50
- RE10, RE20, RE30, RE50 (I think we hope to also do RE40 with 0.12)
- QU10, QU30, QU40, QU50 (we should put a bit of focus to QU20)
- CO10, CO20, CO30, CO40, CO60, CO70 (for CO50, I think we've been
operating under the assumption that PMC and contributors are pretty
standard definitions by ASF. We can call those out explicitly.)
- CS10, CS50 (We are also assuming 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.
> 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 often to make a key contribution. So I hope this doesn’t become a
> time to prune too deeply. I’d suggest we only do that if one of the
> committers has done something to lessen our project maturity or wants to be
> left out for their own reasons. An example of bad behavior is someone
> trying to exert corporate dominance (which is severely frowned on by the
> ASF). Another would be someone who is disruptive to the point of destroying
> team effectiveness. I personally haven’t seen any of this but purposely
> don’t read everything so chime in here.
>
> It would be good to have people declare their interest-level. As for me,
> I’d like to remain on the PMC as a committer but have no interest in Chair.
> Since people can become busy periodically and not read @dev (me?) we could,
> maybe should, poll the current committers and PMC to get the lists ready
> for the graduation proposal.
>
>
> Don’t forget that we are not just asking for dev community opinion about
> graduation. We are also asking that people check things like the Maturity
> Checklist to see it we are ready. http://community.apache.org/
> apache-way/apache-project-maturity-model.html <
> http://community.apache.org/apache-way/apache-project-maturity-model.html>
> People seem fairly enthusiastic about applying for graduation, but are
> there things we need to do before hand? The goal is to show that we do not
> require the second level check for decisions that the IPMC provides. The
> last release required no changes but had a proviso about content licenses.
> This next release should fly through without provisos IMHO. Are there other
> things we should do?
>
>
> On Sep 1, 2017, at 6:16 AM, takako shimamoto <chiboch...@gmail.com> wrote:
>
> I entirely agree with everyone else.
> I hope the PIO community will become more active after graduation.
>
> > 2. If we are to graduate, who should we include in the list of the
> initial
> > PMC?
>
> Don't all present IPMC members are included in the list of the initial PMC?
>
> Personally, I think we may as well check and see if present IPMC
> members intend to become an initial PMC for graduation.
> Members who make a declaration of intent to become it will surely
> contribute to the project.
> It is a great contribution not only to develop a program but also to
> respond to email aggressively or fix document.
>
>
> 2017-08-29 14:20 GMT+09:00 Donald Szeto <don...@apache.org>:
> > Hi all,
> >
> > Since the ASF Board meeting in May (
> > http://apache.org/foundation/records/minutes/2017/board_
> minutes_2017_05_17.txt),
> > PredictionIO has been considered nearing graduation and I think we are
> > almost there. I am kickstarting this thread so that we can discuss on
> these
> > 3 things:
> >
> > 1. Does the development community feel ready to graduate?
> > 2. If we are to graduate, who should we include in the list of the
> initial
> > PMC?
> > 3. If we are to graduate, who should be the VP of the initial PMC?
> >
> > These points are relevant for graduation. Please take a look at the
> > official graduation guide:
> > http://incubator.apache.org/guides/graduation

[jira] [Comment Edited] (PIO-99) `pio build` exits successfully even when compilation fails

[Donald Szeto (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148202#comment-16148202
 ] 

Donald Szeto edited comment on PIO-99 at 8/30/17 11:20 PM:
---

To reproduce:

# Build an engine that will return a successful run.
# Purposely introduce a syntax error in engine code.
# Build again.

This is a bug because log lines above mentioned it ran into an error and was 
going to abort, but it did not and proceeded to check for build JARs, which 
succeeded because there was a good previous build.


was (Author: dszeto):
To reproduce:

1. Build an engine that will return a successful run.
2. Purposely introduce a syntax error in engine code.
3. Build again.

This is a bug because log lines above mentioned it ran into an error and was 
going to abort, but it did not and proceeded to check for build JARs, which 
succeeded because there was a good previous build.

> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>  Labels: newbie
>
> The build command does not fail as expected. While not a big deal when 
> working locally, it seems like this could be problematic for automated, 
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command: 
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt  
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when 
> composing {{pio build}} command into a shell script.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PIO-99) `pio build` exits successfully even when compilation fails

[Donald Szeto (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148202#comment-16148202
 ] 

Donald Szeto commented on PIO-99:
-

To reproduce:

1. Build an engine that will return a successful run.
2. Purposely introduce a syntax error in engine code.
3. Build again.

This is a bug because log lines above mentioned it ran into an error and was 
going to abort, but it did not and proceeded to check for build JARs, which 
succeeded because there was a good previous build.

> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>  Labels: newbie
>
> The build command does not fail as expected. While not a big deal when 
> working locally, it seems like this could be problematic for automated, 
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command: 
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt  
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when 
> composing {{pio build}} command into a shell script.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Graduation to TLP

[Donald Szeto]

Hi all,

Since the ASF Board meeting in May (
http://apache.org/foundation/records/minutes/2017/board_minutes_2017_05_17.txt),
PredictionIO has been considered nearing graduation and I think we are
almost there. I am kickstarting this thread so that we can discuss on these
3 things:

1. Does the development community feel ready to graduate?
2. If we are to graduate, who should we include in the list of the initial
PMC?
3. If we are to graduate, who should be the VP of the initial PMC?

These points are relevant for graduation. Please take a look at the
official graduation guide:
http://incubator.apache.org/guides/graduation.html.

In addition, Sara and I have been working to transfer the PredictionIO
trademark to the ASF. We will keep you updated with our progress.

I would also like to propose to cut a 0.12.0 release by merging JIRAs that
have a target version set to 0.12.0-incubating for graduation. 0.12.0 will
contain cleanups for minor license and copyright issues that were pointed
out in previous releases by IPMC.

Let me know what you think.

Regards,
Donald

[jira] [Updated] (PIO-106) Elasticsearch 5.x StorageClient should reuse RestClient

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-106:
-
Target Version/s: 0.12.0-incubating

> Elasticsearch 5.x StorageClient should reuse RestClient
> ---
>
> Key: PIO-106
> URL: https://issues.apache.org/jira/browse/PIO-106
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
>
> When using the proposed [PIO-105 Batch 
> Predictions|https://issues.apache.org/jira/browse/PIO-105] feature with an 
> engine that queries Elasticsearch in {{Algorithm#predict}}, Elasticsearch's 
> REST interface appears to become overloaded, ending with the Spark job being 
> killed from errors like:
> {noformat}
> [ERROR] [ESChannels] Failed to access to /pio_meta/channels/_search
> [ERROR] [Utils] Aborting task
> [ERROR] [ESApps] Failed to access to /pio_meta/apps/_search
> [ERROR] [Executor] Exception in task 747.0 in stage 1.0 (TID 749)
> [ERROR] [Executor] Exception in task 735.0 in stage 1.0 (TID 737)
> [ERROR] [Common$] Invalid app name ur
> [ERROR] [Utils] Aborting task
> [ERROR] [URAlgorithm] Error when read recent events: 
> java.lang.IllegalArgumentException: Invalid app name ur
> [ERROR] [Executor] Exception in task 749.0 in stage 1.0 (TID 751)
> [ERROR] [Utils] Aborting task
> [ERROR] [Executor] Exception in task 748.0 in stage 1.0 (TID 750)
> [WARN] [TaskSetManager] Lost task 749.0 in stage 1.0 (TID 751, localhost, 
> executor driver): java.net.BindException: Can't assign requested address
>   at sun.nio.ch.Net.connect0(Native Method)
>   at sun.nio.ch.Net.connect(Net.java:454)
>   at sun.nio.ch.Net.connect(Net.java:446)
>   at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
>   at 
> org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processSessionRequests(DefaultConnectingIOReactor.java:273)
>   at 
> org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:139)
>   at 
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)
>   at 
> org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:192)
>   at 
> org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> After these errors happen & the job is killed, Elasticsearch immediately 
> recovers. It responds to queries normally. I researched what could cause this 
> and found an [old issue in the main Elasticsearch 
> repo|https://github.com/elastic/elasticsearch/issues/3647]. With the hints 
> given therein about *using keep-alive in the ES client* to avoid these 
> performance issues, I investigated how PredictionIO's [Elasticsearch 
> StorageClient|https://github.com/apache/incubator-predictionio/tree/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch]
>  manages its connections.
> I found that unlike the other StorageClients (Elasticsearch1, HBase, JDBC), 
> Elasticsearch creates a new underlying connection, an Elasticsearch 
> RestClient, for 
> [every|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESApps.scala#L80]
>  
> [single|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESApps.scala#L157]
>  
> [query|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESChannels.scala#L78]
>  & 
> [interaction|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESEngineInstances.scala#L205]
>  with its API. As a result, *there is no way Elasticsearch TCP connections 
> can be reused via HTTP keep-alive*.
> High-performance workloads with Elasticsearch 5.x will suffer from these 
> issues unless we refactor Elasticsearch StorageClient to share the underlying 
> RestClient instead of [building a new one everytime the client is 
> used|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/StorageClient.scala#L31].
> There are certainly different approache

[jira] [Updated] (PIO-99) `pio build` exits successfully even when compilation fails

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-99:

Target Version/s: 0.12.0-incubating

> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>  Labels: newbie
>
> The build command does not fail as expected. While not a big deal when 
> working locally, it seems like this could be problematic for automated, 
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command: 
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt  
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when 
> composing {{pio build}} command into a shell script.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-105) Batch Predictions

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-105:
-
Target Version/s: 0.12.0-incubating

> Batch Predictions
> -
>
> Key: PIO-105
> URL: https://issues.apache.org/jira/browse/PIO-105
> Project: PredictionIO
>  Issue Type: New Feature
>  Components: Core
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> Implement a new {{pio batchpredict}} command to enable massive, fast, batch 
> predictions from a trained model. Read a multi-object JSON file as the input 
> format, with one query object per line. Similarly, write results to a 
> multi-object JSON file, with one prediction result + its original query per 
> line.
> Currently getting bulk predictions from PredictionIO is possible with either:
> * a {{pio eval}} script, which will always train a fresh, unvalidated model 
> before getting predictions
> * a custom script that hits the {{queries.json}} HTTP API, which is a serious 
> bottleneck when requesting hundreds-of-thousands or millions of predictions
> Neither of these existing bulk-prediction hacks are adequate for the reasons 
> mentioned.
> It's time for this use-case to be a firstclass command :D
> Pull request https://github.com/apache/incubator-predictionio/pull/412



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-102) ESEngineInstances `getAll` results out of order (Elasticsearch 5.x)

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-102:
-
Target Version/s: 0.12.0-incubating

> ESEngineInstances `getAll` results out of order (Elasticsearch 5.x)
> ---
>
> Key: PIO-102
> URL: https://issues.apache.org/jira/browse/PIO-102
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> Using the new Elasticsearch 5.x REST storage client as the meta storage 
> source (`PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH` setup in 
> conf/pio-env.sh), I found that once an engine has been trained a certain 
> number of times, that the most recent engine instance is no longer retrieved. 
> So, I tracked down where those Elasticsearch queries originate.
> In the original Elasticsearch 1.x storage client, [the "scroll" pagination 
> responses are collected by 
> *appending*|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch1/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESUtils.scala#L44]
>  them to one another.
> In the new Elasticsearch 5.x client, [the "scroll" responses are collected by 
> *prepending*|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESUtils.scala#L152]
>  them to one another.
> This out-of-order concatenation breaks [ESEngineInstances 
> `getLatestCompleted`|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESEngineInstances.scala#L192]
>  by erroneously replacing the head of the results with an older engine 
> instance, when there are enough engine instances to overflow a single page of 
> Elasticsearch hits.
> I've observed this buggy behavior after ten trainings, when enough engine 
> instances are stored to trigger Elasticsearch's scroll feature.
> Pull request: https://github.com/apache/incubator-predictionio/pull/406



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-100) Remove SLF4J warning messages on pio command

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-100:
-
Target Version/s: 0.12.0-incubating

> Remove SLF4J warning messages on pio command 
> -
>
> Key: PIO-100
> URL: https://issues.apache.org/jira/browse/PIO-100
> Project: PredictionIO
>  Issue Type: Improvement
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>Priority: Minor
>
> pio command prints SLF4J warning as below:
> {code}
> $ /usr/share/predictionio/bin/pio status
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/usr/share/predictionio/lib/spark/pio-data-hdfs-assembly-0.11.1-v1-SNAPSHOT.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/usr/share/predictionio/lib/pio-assembly-0.11.1-v1-SNAPSHOT.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> ...
> {code}
> The cause is that pio-data-hdfs contains slf4j-log4j12 jar file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-115) Cache name-to-ID lookups for Storage app & channel

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-115:
-
Target Version/s: 0.12.0-incubating

> Cache name-to-ID lookups for Storage app & channel
> --
>
> Key: PIO-115
> URL: https://issues.apache.org/jira/browse/PIO-115
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
>
> When stress testing the Universal Recommender with high-concurrency HTTP/REST 
> queries, we observed that Elasticsearch traffic was majority composed of 
> requests resolving the Storage app's name & channel, over and over and over 
> again! In this case, [each per-query call to 
> `LEventStore.findByEntity`|https://github.com/heroku/predictionio-engine-ur/blob/master/src/main/scala/URAlgorithm.scala#L694]
>  re-resolves the app name to an ID.
> Implement memoization for the function that performs these name-to-ID 
> lookups, so that only one set of lookups is performed per process for each 
> app+channel combination.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-111) Document pio batchpredict

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-111:
-
Target Version/s: 0.12.0-incubating

> Document pio batchpredict
> -
>
> Key: PIO-111
> URL: https://issues.apache.org/jira/browse/PIO-111
> Project: PredictionIO
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: 0.12.0-incubating
>Reporter: Donald Szeto
>Assignee: Mars Hall
>  Labels: newbie
> Fix For: 0.12.0-incubating
>
>
> {{pio batchpredict}} is a new feature created in PIO-105. It needs to be 
> documented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PIO-114) Elasticsearch 5.x StorageClient basic HTTP authentication

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-114:
-
Target Version/s: 0.12.0-incubating

> Elasticsearch 5.x StorageClient basic HTTP authentication
> -
>
> Key: PIO-114
> URL: https://issues.apache.org/jira/browse/PIO-114
> Project: PredictionIO
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
>
> Add optional username-password configuration for the new Elasticsearch 5 
> client; in {{conf/pio-env.sh}} config:
> {code}
> # Optional basic HTTP auth
> PIO_STORAGE_SOURCES_ELASTICSEARCH_USERNAME=my-name
> PIO_STORAGE_SOURCES_ELASTICSEARCH_PASSWORD=my-secret
> {code}
> These credentials are sent in each Elasticsearch request as an HTTP Basic 
> Authorization header.
> Enables use of public-cloud, hosted Elasticsearch clusters, such as [Bonsai 
> on Heroku](https://elements.heroku.com/addons/bonsai).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: August 2017 Release

[Donald Szeto]

Hey Mars,

Is this the PR in question?
https://github.com/apache/incubator-predictionio/pull/372

Regards,
Donald

On Thu, Aug 3, 2017 at 11:49 AM, Mars Hall <m...@heroku.com> wrote:

> Hit an Authenticated Elasticsearch 5.x problem on the current develop
> branch.
>
> I just tested the HEAD of develop by performing:
>
>   ./make-distribution.sh \
> -Dscala.version=2.11.8 \
> -Dspark.version=2.1.0 \
> -Dhadoop.version=2.7.3 \
> -Delasticsearch.version=5.1.1
>
> Then, tried build/train/deploy of our Universal Recommender template.
>
> Locally, it makes it through train to the point when it saves to
> Elasticsearch, failing with:
>
> > Exception in thread "main" java.lang.NoSuchMethodError:
> org.elasticsearch.client.RestClient.performRequest(
> Ljava/lang/String;Ljava/lang/String;Ljava/util/Map;[Lorg/
> apache/http/Header;)Lorg/elasticsearch/client/Response;
> >   at org.template.EsClient$.createIndex(EsClient.scala:132)
> >   at org.template.EsClient$.hotSwap(EsClient.scala:218)
> >   at org.template.URModel.save(URModel.scala:86)
>
> I tried deploying it to Heroku as well, and it fails much earlier when
> simply connecting to Elasticsearch:
>
> > remote: Exception in thread "main" 
> > org.elasticsearch.client.ResponseException:
> HEAD https://xx.us-east-1.bonsaisearch.net:443/pio_meta: HTTP/1.1 401
> Unauthorized
> > remote:   at org.elasticsearch.client.RestClient$1.completed(
> RestClient.java:311)
> > remote:   at org.elasticsearch.client.RestClient$1.completed(
> RestClient.java:300)
> > remote:   at shadeio.data.http.concurrent.BasicFuture.completed(
> BasicFuture.java:119)
> > remote:   at shadeio.data.http.impl.nio.client.
> DefaultClientExchangeHandlerImpl.responseCompleted(
> DefaultClientExchangeHandlerImpl.java:177)
> > remote:   at shadeio.data.http.nio.protocol.
> HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:
> 436)
> > remote:   at shadeio.data.http.nio.protocol.
> HttpAsyncRequestExecutor.responseReceived(HttpAsyncRequestExecutor.java:
> 309)
> > remote:   at shadeio.data.http.impl.nio.
> DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.
> java:255)
>
>
> These issues were previously found to be caused by this shade rule:
>   https://github.com/apache/incubator-predictionio/blob/
> develop/storage/elasticsearch/build.sbt#L42
>
> It looks like the shaded package does not actually use the new
> authentication code.
>
> Chan Lee mentioned to me that he was only able to make the TravisCI build
> pass by adding this shade rule, but it is clearly breaking the authenicated
> Elasticsearch functionality.
>
> Any ideas how to solve this?
>
> *Mars
>
> ( <> .. <> )
>
> > On Aug 3, 2017, at 11:02, Donald Szeto <don...@apache.org> wrote:
> >
> > On Thu, Aug 3, 2017 at 10:07 AM, Mars Hall <m...@heroku.com> wrote:
> >
> >> I just opened a PR to add docs for batch predict.
> >>
> >> Moving forward with the 0.12.0 release sounds great. Today, I will pull
> >> develop and see how it's working with the Heroku buildpack.
> >>
> >
> > Awesome. Thanks!
> >
> >
> >>> On Aug 3, 2017, at 00:37, takako shimamoto <chiboch...@gmail.com>
> wrote:
> >>>
> >>> I think it's almost ready, and now we just have to update the current
> >>> documentation.
> >>> The deadline of several unresolved issues for Target Version/s:
> >>> 0.12.0-incubating is extended, right?
> >>
> >
> > Yes. Let's extend those that have not started working if there's no
> > objection.
>
>

[jira] [Resolved] (PIO-66) Document JIRA processes and add to public documentation

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-66.
-
   Resolution: Fixed
 Assignee: Takako Shimamoto  (was: Sara Asher)
Fix Version/s: 0.12.0-incubating

> Document JIRA processes and add to public documentation
> ---
>
> Key: PIO-66
> URL: https://issues.apache.org/jira/browse/PIO-66
> Project: PredictionIO
>  Issue Type: Task
>Reporter: Sara Asher
>Assignee: Takako Shimamoto
> Fix For: 0.12.0-incubating
>
>
> https://docs.google.com/document/d/1nQpENncXZq72KeI3WMe_X8Xz8HKkYO2QC12GD3ZKP9g/edit#heading=h.4og7ud94e5g1



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PIO-111) Document pio batchpredict

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-111.
--
   Resolution: Fixed
Fix Version/s: 0.12.0-incubating

> Document pio batchpredict
> -
>
> Key: PIO-111
> URL: https://issues.apache.org/jira/browse/PIO-111
> Project: PredictionIO
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: 0.12.0-incubating
>Reporter: Donald Szeto
>Assignee: Mars Hall
>  Labels: newbie
> Fix For: 0.12.0-incubating
>
>
> {{pio batchpredict}} is a new feature created in PIO-105. It needs to be 
> documented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: August 2017 Release

[Donald Szeto]

On Thu, Aug 3, 2017 at 10:07 AM, Mars Hall  wrote:

> I just opened a PR to add docs for batch predict.
>
> Moving forward with the 0.12.0 release sounds great. Today, I will pull
> develop and see how it's working with the Heroku buildpack.
>

Awesome. Thanks!


> > On Aug 3, 2017, at 00:37, takako shimamoto  wrote:
> >
> > I think it's almost ready, and now we just have to update the current
> > documentation.
> > The deadline of several unresolved issues for Target Version/s:
> > 0.12.0-incubating is extended, right?
>

Yes. Let's extend those that have not started working if there's no
objection.

[jira] [Resolved] (PIO-63) Fix incubator branding issues

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-63.
-
   Resolution: Fixed
 Assignee: Naoki Takezoe  (was: Donald Szeto)
Fix Version/s: 0.12.0-incubating

> Fix incubator branding issues
> -
>
> Key: PIO-63
> URL: https://issues.apache.org/jira/browse/PIO-63
> Project: PredictionIO
>  Issue Type: Bug
>Affects Versions: 0.11.0-incubating
>    Reporter: Donald Szeto
>Assignee: Naoki Takezoe
> Fix For: 0.12.0-incubating
>
>
> {quote}
> John D. Ament <johndam...@apache.org>
> Please review the branding guide here: 
> http://incubator.apache.org/guides/branding.html
> Specifically, we expect all podlings to show a logo (the actual logo has 
> changed) for the Incubator, and include a disclaimer (the same release 
> disclaimer) on the website.  I can find neither on your website.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PIO-105) Batch Predictions

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-105.
--
   Resolution: Fixed
Fix Version/s: 0.12.0-incubating

> Batch Predictions
> -
>
> Key: PIO-105
> URL: https://issues.apache.org/jira/browse/PIO-105
> Project: PredictionIO
>  Issue Type: New Feature
>  Components: Core
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> Implement a new {{pio batchpredict}} command to enable massive, fast, batch 
> predictions from a trained model. Read a multi-object JSON file as the input 
> format, with one query object per line. Similarly, write results to a 
> multi-object JSON file, with one prediction result + its original query per 
> line.
> Currently getting bulk predictions from PredictionIO is possible with either:
> * a {{pio eval}} script, which will always train a fresh, unvalidated model 
> before getting predictions
> * a custom script that hits the {{queries.json}} HTTP API, which is a serious 
> bottleneck when requesting hundreds-of-thousands or millions of predictions
> Neither of these existing bulk-prediction hacks are adequate for the reasons 
> mentioned.
> It's time for this use-case to be a firstclass command :D
> Pull request https://github.com/apache/incubator-predictionio/pull/412



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PIO-111) Document pio batchpredict

[Donald Szeto (JIRA)]

Donald Szeto created PIO-111:


 Summary: Document pio batchpredict
 Key: PIO-111
 URL: https://issues.apache.org/jira/browse/PIO-111
 Project: PredictionIO
  Issue Type: Task
  Components: Documentation
Affects Versions: 0.12.0-incubating
Reporter: Donald Szeto


{{pio batchpredict}} is a new feature created in PIO-105. It needs to be 
documented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PIO-110) Refactor common code shared by CreateServer and BatchPredict

[Donald Szeto (JIRA)]

Donald Szeto created PIO-110:


 Summary: Refactor common code shared by CreateServer and 
BatchPredict
 Key: PIO-110
 URL: https://issues.apache.org/jira/browse/PIO-110
 Project: PredictionIO
  Issue Type: Improvement
  Components: Core
Affects Versions: 0.12.0-incubating
Reporter: Donald Szeto


{{BatchPredict}} was created in PIO-105 and has a substantial amount of shared 
code with {{CreateServer}}. It would be beneficial to refactor both of them to 
share as much common code as possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PIO-110) Refactor common code shared by CreateServer and BatchPredict

[Donald Szeto (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIO-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109721#comment-16109721
 ] 

Donald Szeto commented on PIO-110:
--

Please follow [~takezoe]'s code style advice on 
https://github.com/apache/incubator-predictionio/pull/412.

> Refactor common code shared by CreateServer and BatchPredict
> 
>
> Key: PIO-110
> URL: https://issues.apache.org/jira/browse/PIO-110
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.12.0-incubating
>Reporter: Donald Szeto
>  Labels: newbie
>
> {{BatchPredict}} was created in PIO-105 and has a substantial amount of 
> shared code with {{CreateServer}}. It would be beneficial to refactor both of 
> them to share as much common code as possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

August 2017 Release

[Donald Szeto]

Hey all,

To adhere to the proposed release cadence by Sara, let's shoot to cut a
release in early August that addresses all the top level graduation issues.

How does the developer community feel about this? Any major issues that we
should also resolve with this release? It looks like many TLP cleanup, new
features and bug fixes have already gone into the current development
branch.

Regards,
Donald

August 2017 Podling Report

[Donald Szeto]

Hi all,

Please review the following report. Mentors, if this is good to go, please
put this on the incubator wiki.

Regards,
Donald

---

PredictionIO

PredictionIO is an open source Machine Learning Server built on top of a
state-of-the-art open source stack, that enables developers to manage and
deploy production-ready predictive services for various kinds of machine
learning tasks.

PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.

Three most important issues to address in the move towards graduation:

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  1. Our new committers have been actively contributing new features and
bug fixes to the core codebase.
  2. There are new local meetups about PredictionIO in Japan.
  3. There has been growing integration effort of PredictionIO on the
Heroku platform.
  4. Increased traffic on the user mailing list.

How has the project developed since the last report?

  1. Around 40 pull requests have been accepted and merged since 0.11's
release, from both committers and contributors.
  2. On track to stick with a bi-monthly release schedule. Proposing a new
release for the beginning of August.
  3. Many cleanup effort into TLP graduation.

Date of the last release:

  Apache PredictionIO 0.11.0-incubating on 2017-04-25

When were the last committers or PMC members elected?

  Mars Hall was elected as committer and PMC member on July 8, 2017.

Re: Podling Report Reminder - August 2017

[Donald Szeto]

Any PMC member who want to take a shot at this? A sample of the previous
report can be found on this mailing list's archive.

Regards,
Donald

On Sat, Jul 29, 2017 at 6:02 AM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 August 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, August 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/August2017
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

[jira] [Resolved] (PIO-104) Make proper implementation of plugins

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-104.
--
   Resolution: Fixed
Fix Version/s: 0.12.0-incubating

> Make proper implementation of plugins
> -
>
> Key: PIO-104
> URL: https://issues.apache.org/jira/browse/PIO-104
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Naoki Takezoe
>Assignee: Naoki Takezoe
> Fix For: 0.12.0-incubating
>
>
> The current plugin system has some issues to be fixed:
> - start() method of plugin is not called, this method seems to be unnecessary
> - outputSniffer exists as interface, but it's not implemented in engine server
> We should fix them before documenting plugin usage in PIO-101



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

New PMC member and committer: Mars Hall

[Donald Szeto]

Hi all,

The Project Management Committee (PMC) for Apache PredictionIO (incubating)
has asked Mars Hall to become a PMC member and committer, and we are
pleased to announce that he has accepted.

Mars has been working on PredictionIO since 0.10 and has suggested and made
changes to the core so that it has become more configurable and easier to
deploy on Heroku. He added authentication support to the REST-based
Elasticsearch client. He has also found and fixed core bugs.

Mars is the primary driver in delivering a good developer experience
through Heroku buildpacks for PredictionIO (
https://github.com/heroku/predictionio-buildpack), which allows engine
templates to be submitted to Heroku and deployed automatically. He also
made a couple engine templates that are preset to do so (
https://github.com/heroku/predictionio-engine-classification,
https://github.com/heroku/predictionio-engine-ur).

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity. Being a PMC member enables assistance with the management and
to guide the direction of the project.

Please join us in welcoming Mars.

Regards,
Donald

[jira] [Resolved] (PIO-102) ESEngineInstances `getAll` results out of order (Elasticsearch 5.x)

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-102.
--
   Resolution: Fixed
Fix Version/s: 0.12.0-incubating

> ESEngineInstances `getAll` results out of order (Elasticsearch 5.x)
> ---
>
> Key: PIO-102
> URL: https://issues.apache.org/jira/browse/PIO-102
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> Using the new Elasticsearch 5.x REST storage client as the meta storage 
> source (`PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH` setup in 
> conf/pio-env.sh), I found that once an engine has been trained a certain 
> number of times, that the most recent engine instance is no longer retrieved. 
> So, I tracked down where those Elasticsearch queries originate.
> In the original Elasticsearch 1.x storage client, [the "scroll" pagination 
> responses are collected by 
> *appending*|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch1/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESUtils.scala#L44]
>  them to one another.
> In the new Elasticsearch 5.x client, [the "scroll" responses are collected by 
> *prepending*|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESUtils.scala#L152]
>  them to one another.
> This out-of-order concatenation breaks [ESEngineInstances 
> `getLatestCompleted`|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESEngineInstances.scala#L192]
>  by erroneously replacing the head of the results with an older engine 
> instance, when there are enough engine instances to overflow a single page of 
> Elasticsearch hits.
> I've observed this buggy behavior after ten trainings, when enough engine 
> instances are stored to trigger Elasticsearch's scroll feature.
> Pull request: https://github.com/apache/incubator-predictionio/pull/406



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PIO-72) In `pio-shell` jdbc.StorageClient cannot be loaded

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-72.
-
   Resolution: Fixed
Fix Version/s: 0.12.0-incubating

> In `pio-shell` jdbc.StorageClient cannot be loaded
> --
>
> Key: PIO-72
> URL: https://issues.apache.org/jira/browse/PIO-72
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.11.0-incubating
> Environment: local developer machines
>Reporter: Mars Hall
>Assignee: Chan
> Fix For: 0.12.0-incubating
>
> Attachments: image.png
>
>
> Class loading/classpath is currently broken in {{pio-shell}}. Attached 
> screenshot is the public docs that explain the intended functionality. 
> Instead, users see errors when attempting to use storage classes:
> {code:title=pio-shell.error|borderStyle=solid}
> java.lang.ClassNotFoundException: jdbc.StorageClient
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.apache.predictionio.data.storage.Storage$.getClient(Storage.scala:228)
> at 
> org.apache.predictionio.data.storage.Storage$.org$apache$predictionio$data$storage$Storage$$updateS2CM(Storage.scala:254)
> at 
> org.apache.predictionio.data.storage.Storage$$anonfun$sourcesToClientMeta$1.apply(Storage.scala:215)
> at 
> org.apache.predictionio.data.storage.Storage$$anonfun$sourcesToClientMeta$1.apply(Storage.scala:215)
> at scala.collection.mutable.MapLike$class.getOrElseUpdate(MapLike.scala:189)
> at scala.collection.mutable.AbstractMap.getOrElseUpdate(Map.scala:91)
> at 
> org.apache.predictionio.data.storage.Storage$.sourcesToClientMeta(Storage.scala:215)
> at 
> org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
> at 
> org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
> at 
> org.apache.predictionio.data.storage.Storage$.getMetaDataApps(Storage.scala:387)
> at 
> org.apache.predictionio.data.store.Common$.appsDb$lzycompute(Common.scala:27)
> at org.apache.predictionio.data.store.Common$.appsDb(Common.scala:27)
> at org.apache.predictionio.data.store.Common$.appNameToId(Common.scala:32)
> at 
> org.apache.predictionio.data.store.PEventStore$.aggregateProperties(PEventStore.scala:108)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:31)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:36)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:38)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC.(:40)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC.(:42)
> at $line20.$read$$iwC$$iwC$$iwC.(:44)
> at $line20.$read$$iwC$$iwC.(:46)
> at $line20.$read$$iwC.(:48)
> at $line20.$read.(:50)
> at $line20.$read$.(:54)
> at $line20.$read$.()
> at $line20.$eval$.(:7)
> at $line20.$eval$.()
> at $line20.$eval.$print()
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
> at org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1346)
> at org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:840)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:871)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:819)
> at org.apache.spark.repl.SparkILoop.reallyInterpret$1(SparkILoop.scala:857)
> at 
> org.apache.spark.repl.SparkILoop.interpretStartingWith(SparkILoop.scala:902)
> at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:814)
> at org.apache.spark.repl.SparkILoop.processLine$1(SparkILoop.scala:657)
> at org.apache.spark.repl.SparkILoop.innerLoop$1(SparkILoop.scala:665)
> at 
> org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$loop(SparkILoop.scala:670)
> at 
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply$mcZ$sp(SparkILoop.scala:997)
> at 
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
> at 
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)

[jira] [Assigned] (PIO-56) Unit tests in module core should not require real setup

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto reassigned PIO-56:
---

Assignee: Lucas Bonatto Miguel

> Unit tests in module core should not require real setup
> ---
>
> Key: PIO-56
> URL: https://issues.apache.org/jira/browse/PIO-56
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.10.0-incubating
> Environment: Tested with Mac OS X, i7, 8GB
>Reporter: Lucas Bonatto Miguel
>Assignee: Lucas Bonatto Miguel
>  Labels: development_environment
> Fix For: 0.12.0-incubating
>
>
> *This issue affects only developers*
> When downloading the code from github and trying to run the tests of the 
> project core via sbt, one will face an error stating that the METADATA 
> configuration is missing, e.g:
> [ERROR] [Storage$] Required repository (METADATA) configuration is missing.
> [ERROR] [Storage$] There were 1 configuration errors. Exiting.
> It looks like the project predictionio core requires a METADATA datasource 
> (elasticsearch) installed and configured in the developer machine.
> There are some benefits if the project require less external 
> installation/configuration:
>  - Developers would have an easy setup of the environment.
>  - Continuous integration would be easier
> How to reproduce:
>  - Download predictionio from github
>  - In root folder run ./make-distribution.sh
>  - In root folder run sbt core/test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: License for templates and sdk

[Donald Szeto]

Hi Shinsuke,

It's a good question. Templates and SDKs are not part of an actual release
defined by ASF, and they don't go into ASF distribution network. That's why
they don't get voted on like the core release.

Would a mentor kindly weigh in on this? Templates are like hello-worlds
tailored for different ML use cases. SDKs are lightweight client code for
REST APIs exposed by core (event and engine server).

Regards,
Donald

On Tue, Jul 11, 2017 at 11:18 AM Shinsuke Sugaya  wrote:

> Hi,
>
> For license updates, my understanding is that we need to
> also update the following repositories for graduation.
> Is it correct? If yes, I'll file JIRA issues.
>
> https://github.com//apache/incubator-predictionio-sdk-python
> https://github.com//apache/incubator-predictionio-sdk-php
> https://github.com//apache/incubator-predictionio-sdk-ruby
> https://github.com//apache/incubator-predictionio-sdk-java
> https://github.com//apache/incubator-predictionio-template-recommender
> https://github.com//apache/incubator-predictionio-template-skeleton
> https://github.com//apache/incubator-predictionio-template-similar-product
> https://github.com//apache/incubator-predictionio-template-ecom-recommender
> https://github.com//apache/incubator-predictionio-template-text-classifier
>
> https://github.com//apache/incubator-predictionio-template-attribute-based-classifier
>
> https://github.com//apache/incubator-predictionio-template-java-ecom-recommender
>
> It seems not to update Swift SDK repository for a long time.
> If nobody update it, it's better to remove it at graduation.
>
> https://github.com//apache/incubator-predictionio-sdk-swift
>
> Regards,
>  shinsuke
>

[jira] [Updated] (PIO-99) `pio build` exits successfully even when compilation fails

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-99:

Labels: newbie  (was: )

> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>  Labels: newbie
>
> The build command does not fail as expected. While not a big deal when 
> working locally, it seems like this could be problematic for automated, 
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command: 
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt  
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when 
> composing {{pio build}} command into a shell script.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PIO-95) Configurable request timeout for REST API

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-95.
-
  Resolution: Fixed
   Fix Version/s: 0.12.0-incubating
Target Version/s: 0.12.0-incubating

> Configurable request timeout for REST API
> -
>
> Key: PIO-95
> URL: https://issues.apache.org/jira/browse/PIO-95
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> We've found the default 20-second REST API request timeout is too short for 
> our batch-prediction use cases. We're running PredictionIO on Heroku which 
> has its own [timeout starting at 
> 30-seconds|https://devcenter.heroku.com/articles/limits#http-timeouts]. So 
> we'd prefer a more generous or easily configurable timeout to allow Heroku's 
> routing layer to impose & track this limit in the platform layer.
> I investigated how to configure this and found [Spray 
> `application.conf`|http://spray.io/documentation/1.2.4/spray-can/configuration/].
>  This PR simply increases the timeout.
> I would love guidance on how we might extract this config into an environment 
> variable or a value in `pio-env.sh`.
> Investigation / implementation PR: 
> https://github.com/apache/incubator-predictionio/pull/394



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (PIO-95) Configurable request timeout for REST API

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto reassigned PIO-95:
---

Assignee: Mars Hall

> Configurable request timeout for REST API
> -
>
> Key: PIO-95
> URL: https://issues.apache.org/jira/browse/PIO-95
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> We've found the default 20-second REST API request timeout is too short for 
> our batch-prediction use cases. We're running PredictionIO on Heroku which 
> has its own [timeout starting at 
> 30-seconds|https://devcenter.heroku.com/articles/limits#http-timeouts]. So 
> we'd prefer a more generous or easily configurable timeout to allow Heroku's 
> routing layer to impose & track this limit in the platform layer.
> I investigated how to configure this and found [Spray 
> `application.conf`|http://spray.io/documentation/1.2.4/spray-can/configuration/].
>  This PR simply increases the timeout.
> I would love guidance on how we might extract this config into an environment 
> variable or a value in `pio-env.sh`.
> Investigation / implementation PR: 
> https://github.com/apache/incubator-predictionio/pull/394



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PIO-94) Query parsing may throw intractable errors

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-94.
-
  Resolution: Fixed
   Fix Version/s: 0.12.0-incubating
Target Version/s: 0.12.0-incubating

> Query parsing may throw intractable errors
> --
>
> Key: PIO-94
> URL: https://issues.apache.org/jira/browse/PIO-94
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> We get intractable errors from some `queries.json` requests, like this one 
> without a stacktrace:
> {code}
> [ERROR] [ServerActor] Query '{
>   "item": "000"
> }' is invalid. Reason: Expected object but got JNothing
> {code}
> To solve, add stacktraces to these errors using the pattern already present 
> elsewhere in `CreateServer.scala`.
> PR: https://github.com/apache/incubator-predictionio/pull/393



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PIO-65) Cache downloaded jars in Travis build

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-65.
-
   Resolution: Fixed
Fix Version/s: 0.12.0-incubating

> Cache downloaded jars in Travis build
> -
>
> Key: PIO-65
> URL: https://issues.apache.org/jira/browse/PIO-65
> Project: PredictionIO
>  Issue Type: Task
>Reporter: Naoki Takezoe
>Assignee: Naoki Takezoe
> Fix For: 0.12.0-incubating
>
>
> Sometimes Travis build fails in downloading jars. Now Travis build has 12 
> patterns of test and we don't have a permission to rebuild failed test. So we 
> have to re-run all patterns by additional push or reopen pull request even if 
> a part of test failed.
> Maybe caching them makes Travis build stable and also decreases build time.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (PIO-69) Create binary version of PredictionIO as part of release process

[Donald Szeto (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIO-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037643#comment-16037643
 ] 

Donald Szeto commented on PIO-69:
-

Hey [~shinsuke], the main issue here is that Apache requires auditing all 
bundled 3rd party libraries in any binary distributions that would be uploaded 
to the Apache distribution network. Our make-distribution.sh script already 
handles creating the binary distribution part. What is missing here is to make 
sure the binary distribution only contains 3rd party libraries that are 
compatible with the APLv2 license.

> Create binary version of PredictionIO as part of release process
> 
>
> Key: PIO-69
> URL: https://issues.apache.org/jira/browse/PIO-69
> Project: PredictionIO
>  Issue Type: New Feature
>  Components: Build
>Reporter: Sara Asher
>Assignee: Shinsuke Sugaya
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (PIO-61) Add S3 Model Data Repository

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-61:

Fix Version/s: 0.12.0-incubating

> Add S3 Model Data Repository
> 
>
> Key: PIO-61
> URL: https://issues.apache.org/jira/browse/PIO-61
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
> Fix For: 0.12.0-incubating
>
>
> To put/get model data to AWS S3 directly, using aws-java-sdk-s3, add 
> storage/s3 implementation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (PIO-61) Add S3 Model Data Repository

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto resolved PIO-61.
-
Resolution: Fixed

> Add S3 Model Data Repository
> 
>
> Key: PIO-61
> URL: https://issues.apache.org/jira/browse/PIO-61
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
> Fix For: 0.12.0-incubating
>
>
> To put/get model data to AWS S3 directly, using aws-java-sdk-s3, add 
> storage/s3 implementation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: PIO 0.12.0 and Graduation Time?

[Donald Szeto]

Hey Andrew, is it possible for us to create non-release binary
distributions and ask Incubator PMC to help take a look without starting a
voting thread? This would allow us iron out issues in parallel to working
on 0.12.

On Wed, May 31, 2017 at 9:08 AM, Andrew Purtell  wrote:

> Really glad to see this discussion started, because I think your podling
> is nearing graduation. The most important determination of that is taking
> the initiative to propose it.
>
> I looked over the spreadsheet and have only this comment: You'll gain from
> having the incubator picking over your binary artifact release attempt, the
> first time you try to put one together. You won't have that after
> graduation. I recommend working through binary artifacts as part of 0.12,
> then proposing yourselves for graduation.
>
>
> On Thu, May 18, 2017 at 1:49 PM, Pat Ferrel  wrote:
>
>> 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/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
>> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
>
>
>
>
> --
> Best regards,
>
>- Andy
>
> If you are given a choice, you believe you have acted freely. - Raymond
> Teller (via Peter Watts)
>

Re: PIO 0.12.0 and Graduation Time?

[Donald Szeto]

Thanks Pat for starting this. Added some edits to it. Everyone please feel
free to comment. PMCs please feel free to request edit access.

Very happy that we started the discussion!

On Thu, May 18, 2017 at 1:50 PM Pat Ferrel  wrote:

> 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/document/d/1LTlzxH_CcWi67p8kCQPfPyu-1SwIJBkEonH3Yw4T6pY/edit?usp=sharing

Re: JIRA and release process for PredictionIO

[Donald Szeto]

+1. Thanks Sara!

On Thu, May 18, 2017 at 8:48 AM Sara Asher  wrote:

> Hi everyone,
>
> Thank you for allowing me to join the PredictionIO team!
>
> To start with, I would like to document a process for using JIRA and to
> suggest a standard release cadence for PredictionIO.
>
> I've worked with Donald to come up with the following:
>
> https://docs.google.com/document/d/1nQpENncXZq72KeI3WMe_
> X8Xz8HKkYO2QC12GD3ZKP9g/edit?usp=sharing
>
> Please comment and give suggestions!  When you are all content, I will add
> this to our public documentation.
>
> Thanks,
> Sara
>

Re: [Proposal] Update the default build targets

[Donald Szeto]

By the way, one of the graduation criteria is to establish a stable release
process. Sara has proposed one, so let's review that as well.

On Thu, May 18, 2017 at 1:28 PM Donald Szeto <don...@apache.org> wrote:

> +1 on this. We should do a survey in user@ to measure the impact as well.
>
> We should start a separate thread for graduation discussion. There are a
> couple cleanups that we need to address and are already filed in JIRA.
>
> On Thu, May 18, 2017 at 10:07 AM Naoki Takezoe <take...@gmail.com> wrote:
>
>> Hi all,
>>
>> Currently, the default build targets look like following:
>>
>> - PIO_SCALA_VERSION=2.10.6
>> - PIO_SPARK_VERSION=1.6.3
>> - PIO_ELASTICSEARCH_VERSION=1.7.6
>> - PIO_HADOOP_VERSION=2.6.5
>>
>> However they look too old now despite PredictionIO has supported newer
>> versions.
>> How is change the default build targets as following?
>>
>> - PIO_SCALA_VERSION=2.11.8
>> - PIO_SPARK_VERSION=2.1.0
>> - PIO_ELASTICSEARCH_VERSION=5.2.2
>> - PIO_HADOOP_VERSION=2.7.3
>>
>> Also, are there roadmap for graduating incubator?
>> It might have to contain the plan of default and supported versions if
>> we will change them.
>>
>> Regards,
>>
>> --
>> Naoki Takezoe
>>
>

Re: [Proposal] Update the default build targets

[Donald Szeto]

+1 on this. We should do a survey in user@ to measure the impact as well.

We should start a separate thread for graduation discussion. There are a
couple cleanups that we need to address and are already filed in JIRA.

On Thu, May 18, 2017 at 10:07 AM Naoki Takezoe  wrote:

> Hi all,
>
> Currently, the default build targets look like following:
>
> - PIO_SCALA_VERSION=2.10.6
> - PIO_SPARK_VERSION=1.6.3
> - PIO_ELASTICSEARCH_VERSION=1.7.6
> - PIO_HADOOP_VERSION=2.6.5
>
> However they look too old now despite PredictionIO has supported newer
> versions.
> How is change the default build targets as following?
>
> - PIO_SCALA_VERSION=2.11.8
> - PIO_SPARK_VERSION=2.1.0
> - PIO_ELASTICSEARCH_VERSION=5.2.2
> - PIO_HADOOP_VERSION=2.7.3
>
> Also, are there roadmap for graduating incubator?
> It might have to contain the plan of default and supported versions if
> we will change them.
>
> Regards,
>
> --
> Naoki Takezoe
>

Re: Pipeline support for predictionIO

[Donald Szeto]

Hey Ravi,

For pipeline support do you mean Spark ML pipelines? If so, let's continue
the discussion on other thread named "Support for Spark ML pipelines". The
JIRA ticket is https://issues.apache.org/jira/browse/PIO-71.

Regards,
Donald

On Tue, May 16, 2017 at 3:55 AM, Ravi Kiran  wrote:

> Hi,
> How can I follow/contribute to development of 'pipeline support for
> predicitonio'?
>

Re: Support for spark ML pipelines

[Donald Szeto]

Hi Pankil,

Thank you for your interest. There is a ticket at
https://issues.apache.org/jira/browse/PIO-71. There isn't a design yet, so
we are open to collaborate on starting one.

Regards,
Donald

On Fri, May 12, 2017 at 11:04 AM, Pankil Doshi  wrote:

> Hi,
>
> I am interested to know about the road map of having Spark pipelines work
> natively with prediction.io. Is there a rough draft or plan ? May be JIRA
> ticket?
>
> Thanks,
> Pankil
>

[jira] [Assigned] (PIO-71) Support Spark ML natively as an alternative to DASE

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto reassigned PIO-71:
---

Assignee: Donald Szeto

> Support Spark ML natively as an alternative to DASE
> ---
>
> Key: PIO-71
> URL: https://issues.apache.org/jira/browse/PIO-71
> Project: PredictionIO
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Donald Szeto
>    Assignee: Donald Szeto
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (PIO-71) Support Spark ML natively as an alternative to DASE

[Donald Szeto (JIRA)]

Donald Szeto created PIO-71:
---

 Summary: Support Spark ML natively as an alternative to DASE
 Key: PIO-71
 URL: https://issues.apache.org/jira/browse/PIO-71
 Project: PredictionIO
  Issue Type: New Feature
  Components: Core
Affects Versions: 0.11.0-incubating
Reporter: Donald Szeto






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

New product manager: Sara Asher

[Donald Szeto]

Hi all,

The Project Management Committee (PMC) for Apache PredictionIO (incubating)
has asked Sara Asher to become a product manager, and we are pleased to
announce that she has accepted.

Sara is a Director of Product Management for Salesforce Einstein, where she
creates products that let people build smarter applications with Salesforce
and advanced AI. Prior to Salesforce, Sara worked at Alpine Data where she
was chief product manager and founding director of Alpine Labs. Sara holds
an AB in mathematics from Princeton University and a PhD in mathematics
from Northwestern University.

Being a product manager enables management of JIRA tickets. This should
make prioritizing product features more efficient.

Please join us in welcoming Sara.

Regards,
Donald

Re: New PMC member and committer: Takahiro Hagino

[Donald Szeto]

Correction: Takahiro is not a committer of Apache Portals. Sorry for the
misinformation.

On Wed, May 17, 2017 at 8:50 AM, Donald Szeto <don...@apache.org> wrote:

> Hi all,
>
> The Project Management Committee (PMC) for Apache PredictionIO
> (incubating) has asked Takahiro Hagino to become a PMC member and
> committer, and we are pleased to announce that he has accepted. He is also
> a committer of the Apache Portals project.
>
> He has made major contributions to the PredictionIO 0.11.0 release by
> adding Elasticsearch 5 support. This shows solid understanding of the core
> PredictionIO codebase. In addition, he also helped cleaning up and
> refactoring code in the core. Having him join forces with us would be
> beneficial for PredictionIO's growth.
>
> Being a committer enables easier contribution to the project since there
> is no need to go via the patch submission process. This should enable
> better productivity. Being a PMC member enables assistance with the
> management and to guide the direction of the project.
>
> Please join us in welcoming Takahiro.
>
> Regards,
> Donald
>

Re: GitHub settings for templates

[Donald Szeto]

Hey Shinsuke,

For GitHub integration issues, we need to file Apache JIRA tickets in the
INFRA project. They will be able to help. Please give it a shot.

Regards,
Donald

On Thu, May 11, 2017 at 9:18 PM Shinsuke Sugaya 
wrote:

> Hi,
>
> I have 2 questions for template repositories in GitHub:
>
> 1) incubator-predictionio-template-text-classifier
>
> This repository uses master branch as default, but others use develop.
> Can we change the default branch to develop?
>
> 2) incubator-predictionio-template-similar-product
>
> I updated this repository, but it seems not to send a notification mail
> to dev@predictionio.i.a.o. Could you check notification settings
> in this repository of GitHub?
>
> Regards,
>  shinsuke
>

New PMC member and committer: Shinsuke Sugaya

[Donald Szeto]

Hi all,

The Project Management Committee (PMC) for Apache PredictionIO (incubating)
has asked Shinsuke Sugaya to become a PMC member and committer, and we are
pleased to announce that he has accepted. He is also a committer of the
Apache Portals project.

He has made major contributions to the PredictionIO 0.11.0 release by
adding Elasticsearch 5 support. This shows solid understanding of the core
PredictionIO codebase. In addition, he also helped cleaning up and
refactoring code in the core. Having him join forces with us would be
beneficial for PredictionIO's growth.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity. Being a PMC member enables assistance with the management and
to guide the direction of the project.

Please join us in welcoming Shinsuke.

Regards,
Donald

Re: Maintain template projects

[Donald Szeto]

So far we have been following a similar procedure outlined here:
http://mahout.apache.org/developers/github.html

We should definitely create our own committer documentation as well.

On Tue, May 9, 2017 at 8:43 PM Naoki Takezoe  wrote:

> Hi all,
>
> I found some pull requests which should be merged in template projects
> such as:
>
> -
> https://github.com/apache/incubator-predictionio-template-recommender/pull/16
> -
> https://github.com/apache/incubator-predictionio-template-java-ecom-recommender/pull/5
>
> I would like to take them, but I don't know a correct way to merge from
> GitHub.
> Just merge from GitHub and push it to ASF repo?
>
> Regards,
>
> --
> Naoki Takezoe
>

[jira] [Updated] (PIO-64) JDBCPEvents unit tests fail intermittently

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-64:

Fix Version/s: (was: 0.11.1-incubating)

> JDBCPEvents unit tests fail intermittently
> --
>
> Key: PIO-64
> URL: https://issues.apache.org/jira/browse/PIO-64
> Project: PredictionIO
>  Issue Type: Bug
>Affects Versions: 0.11.0-incubating
> Environment: Travis CI
>Reporter: Donald Szeto
>  Labels: newbie
>
> The creation timestamp of a test event mismatch the expectation by 1 
> millisecond and sometimes causes annoyance with PR's tests not passing even 
> though the error is irrelevant.
> Example test failure: 
> https://travis-ci.org/apache/incubator-predictionio/jobs/228316305
> Excerpt of output above:
> {code}
> [info] PEventsSpec
> [info] 
> [info]   PredictionIO Storage PEvents Specification
> [info] 
> [info] PEvents can be implemented by:
> [info] - JDBCPEvents 
> [info] 
> [info] JDBCPEvents should
> [info] - behave like any PEvents implementation 
> [info] 
> [info] + - (init test)
> [info] + - (insert test events)
> [info] + find in default
> [info] + find in channel
> [info] + aggregate user properties in default
> [info] + aggregate user properties in channel
> [info] + write to default
> [info] x write to channel
> [error]  
> List(Event(id=None,event=$set,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(a
>  -> JInt(22), b -> JString(value13), d -> JArray(List(JInt(5), JInt(6), 
> JInt(1),t=1970-01-01T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
>  
> Event(id=None,event=$unset,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(a
>  -> 
> JNull)),t=1970-01-02T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
>  
> Event(id=None,event=$set,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(b
>  -> JString(value10), f -> JString(new12), d -> JArray(List(JInt(1), JInt(3), 
> JInt(2),t=1970-01-03T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
>  
> Event(id=None,event=my_event3,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(propA
>  -> JDouble(1.2345), propB -> 
> JString(valueB))),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.172Z),
>  
> Event(id=None,event=my_event4,eType=my_entity_type4,eId=my_entity_id4,tType=Some(my_target_entity_type4),tId=Some(my_target_entity_id4),p=DataMap(Map(prop6
>  -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a), 
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), 
> prop3 -> JArray(List(JInt(1), JInt(2), 
> JInt(3),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z),
>  
> Event(id=None,event=my_event6,eType=my_entity_type6,eId=my_entity_id6,tType=Some(my_target_entity_type6),tId=Some(my_target_entity_id6),p=DataMap(Map(prop6
>  -> JDouble(4.56), prop1 -> JInt(6), prop5 -> JArray(List(JString(a), 
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), 
> prop3 -> JArray(List(JInt(6), JInt(7), 
> JInt(8),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z),
>  
> Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
>  -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a), 
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), 
> prop3 -> JArray(List(JInt(1), JInt(2), 
> JInt(3),t=2017-05-03T12:43:42.171Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.171Z),
>  
> Event(id=None,event=my_event5,eType=my_entity_type5,eId=my_entity_id5,tType=Some(my_target_entity_type5),tId=Some(my_target_entity_id5),p=DataMap(Map(prop6
>  -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a), 
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), 
> prop3 -> JArray(List(JInt(1), JInt(2), 
> JInt(3),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z))
> [error]is missing: 
> Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
>  -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a), 
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true)

[jira] [Updated] (PIO-62) Investigate RAT issues and other authorship information

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-62:

Labels: newbie  (was: )

> Investigate RAT issues and other authorship information
> ---
>
> Key: PIO-62
> URL: https://issues.apache.org/jira/browse/PIO-62
> Project: PredictionIO
>  Issue Type: Bug
>Affects Versions: 0.11.0-incubating
>    Reporter: Donald Szeto
>  Labels: newbie
>
> {quote}
> From: Luciano Resende <l...@gmail.com>
> Subject: Re: [VOTE] Release Apache PredictionIO 0.11.0 (incubating) RC2
> Date: 2017-04-17 13:29 (-0700)
> List: gene...@incubator.apache.org
> show/hide original text
> I was running RAT on the source distribution and there are a lot of unknown
> licenses, some might be ok, but many are not, such as:
> *.sbt in projects and sub-projects
> *.css in docs
> Other things like signatures, etc seems ok
> -- 
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
> {quote}
> Also take a look at
> # docs/manual/source/humans.txt
> # 
> examples/scala-parallel-recommendation/custom-query/data/src/main/scala/org/template/recommendation/ImportDataScript.scala



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (PIO-64) JDBCPEvents unit tests fail intermittently

[Donald Szeto (JIRA)]

Donald Szeto created PIO-64:
---

 Summary: JDBCPEvents unit tests fail intermittently
 Key: PIO-64
 URL: https://issues.apache.org/jira/browse/PIO-64
 Project: PredictionIO
  Issue Type: Bug
Affects Versions: 0.11.0-incubating
 Environment: Travis CI
Reporter: Donald Szeto
 Fix For: 0.11.1-incubating


The creation timestamp of a test event mismatch the expectation by 1 
millisecond and sometimes causes annoyance with PR's tests not passing even 
though the error is irrelevant.

Example test failure: 
https://travis-ci.org/apache/incubator-predictionio/jobs/228316305

Excerpt of output above:
{code}
[info] PEventsSpec
[info] 
[info]   PredictionIO Storage PEvents Specification
[info] 
[info] PEvents can be implemented by:
[info] - JDBCPEvents 
[info] 
[info] JDBCPEvents should
[info] - behave like any PEvents implementation 
[info] 
[info] + - (init test)
[info] + - (insert test events)
[info] + find in default
[info] + find in channel
[info] + aggregate user properties in default
[info] + aggregate user properties in channel
[info] + write to default
[info] x write to channel
[error]  
List(Event(id=None,event=$set,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(a
 -> JInt(22), b -> JString(value13), d -> JArray(List(JInt(5), JInt(6), 
JInt(1),t=1970-01-01T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
 
Event(id=None,event=$unset,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(a
 -> 
JNull)),t=1970-01-02T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
 Event(id=None,event=$set,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(b 
-> JString(value10), f -> JString(new12), d -> JArray(List(JInt(1), JInt(3), 
JInt(2),t=1970-01-03T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
 
Event(id=None,event=my_event3,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(propA
 -> JDouble(1.2345), propB -> 
JString(valueB))),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.172Z),
 
Event(id=None,event=my_event4,eType=my_entity_type4,eId=my_entity_id4,tType=Some(my_target_entity_type4),tId=Some(my_target_entity_id4),p=DataMap(Map(prop6
 -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a), 
JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), prop3 
-> JArray(List(JInt(1), JInt(2), 
JInt(3),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z),
 
Event(id=None,event=my_event6,eType=my_entity_type6,eId=my_entity_id6,tType=Some(my_target_entity_type6),tId=Some(my_target_entity_id6),p=DataMap(Map(prop6
 -> JDouble(4.56), prop1 -> JInt(6), prop5 -> JArray(List(JString(a), 
JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), prop3 
-> JArray(List(JInt(6), JInt(7), 
JInt(8),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z),
 
Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
 -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a), 
JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), prop3 
-> JArray(List(JInt(1), JInt(2), 
JInt(3),t=2017-05-03T12:43:42.171Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.171Z),
 
Event(id=None,event=my_event5,eType=my_entity_type5,eId=my_entity_id5,tType=Some(my_target_entity_type5),tId=Some(my_target_entity_id5),p=DataMap(Map(prop6
 -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a), 
JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), prop3 
-> JArray(List(JInt(1), JInt(2), 
JInt(3),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z))
[error]is missing: 
Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
 -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a), 
JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), prop3 
-> JArray(List(JInt(1), JInt(2), 
JInt(3),t=2017-05-03T12:43:42.171Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.172Z)
[error]must not contain: 
Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
 -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a), 
JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true), prop3 
-> JArray(List(JInt(1), JInt(2), 
JInt(3),t=2017-05-03T12:43:42.171Z,tag

Re: May 2017 Podling Report

[Donald Szeto]

Adding a note that the new PMC members were voted on but status change has
not yet completed. Please review.

---

PredictionIO

PredictionIO is an open source Machine Learning Server built on top of a
state-of-the-art open source stack, that enables developers to manage and
deploy production-ready predictive services for various kinds of machine
learning tasks.

PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.

Three most important issues to address in the move towards graduation:

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  1. We have published the first release (0.11.0) that incorporates major
changes by non-committer contributors.
  2. There are new tutorials and online classes for PredictionIO by third
parties.
  3. The user mailing list has more activities than last report.
  4. GitHub stars keep growing.

How has the project developed since the last report?

  1. Released version 0.11.0 with major contributions from the
non-committer community.
  2. Established PMC documentation regarding release processes.
  3. In the process of preparing for top level graduation discussion.

Date of the last release:

  Apache PredictionIO 0.11.0-incubating on 2017-04-25

When were the last committers or PMC members elected?

  Naoki Takezoe was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Shinsuke Sugaya was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Takahiro Hagino was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Takako Shimamoto was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Sara Asher was elected as product manager and JIRA administrator on Apr
30, 2017.

On Tue, May 2, 2017 at 10:29 AM, Donald Szeto <don...@apache.org> wrote:

> Hi all,
>
> Please review the following report. Mentors, if this is good to go, please
> put this on the incubator wiki.
>
> Regards,
> Donald
>
> ---
>
> PredictionIO
>
> PredictionIO is an open source Machine Learning Server built on top of a
> state-of-the-art open source stack, that enables developers to manage and
> deploy production-ready predictive services for various kinds of machine
> learning tasks.
>
> PredictionIO has been incubating since 2016-05-26. The initial code for
> PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
> templates and SDKs was granted on 2016-09-20.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Establish a formal release schedule and process, allowing for
> dependable release cycles in a manner consistent with the Apache way.
>   2. Grow the community to establish diversity of background.
>   3. Transition remaining former PredictionIO users from google-groups to
> ASF mailing lists.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   None
>
> How has the community developed since the last report?
>
>   1. We have published the first release (0.11.0) that incorporates major
> changes by non-committer contributors.
>   2. There are new tutorials and online classes for PredictionIO by third
> parties.
>   3. The user mailing list has more activities than last report.
>   4. GitHub stars keep growing.
>
> How has the project developed since the last report?
>
>   1. Released version 0.11.0 with major contributions from the
> non-committer community.
>   2. Established PMC documentation regarding release processes.
>   3. In the process of preparing for top level graduation discussion.
>
> Date of the last release:
>
>   Apache PredictionIO 0.11.0-incubating on 2017-04-25
>
> When were the last committers or PMC members elected?
>
>   Naoki Takezoe was elected as committer and PMC member on Apr 28, 2017.
>   Shinsuke Sugaya was elected as committer and PMC member on Apr 28, 2017.
>   Takahiro Hagino was elected as committer and PMC member on Apr 28, 2017.
>   Takako Shimamoto was elected as committer and PMC member on Apr 28, 2017.
>   Sara Asher was elected as product manager and JIRA administrator on Apr
> 30, 2017.
>

May 2017 Podling Report

[Donald Szeto]

Hi all,

Please review the following report. Mentors, if this is good to go, please
put this on the incubator wiki.

Regards,
Donald

---

PredictionIO

PredictionIO is an open source Machine Learning Server built on top of a
state-of-the-art open source stack, that enables developers to manage and
deploy production-ready predictive services for various kinds of machine
learning tasks.

PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.

Three most important issues to address in the move towards graduation:

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  1. We have published the first release (0.11.0) that incorporates major
changes by non-committer contributors.
  2. There are new tutorials and online classes for PredictionIO by third
parties.
  3. The user mailing list has more activities than last report.
  4. GitHub stars keep growing.

How has the project developed since the last report?

  1. Released version 0.11.0 with major contributions from the
non-committer community.
  2. Established PMC documentation regarding release processes.
  3. In the process of preparing for top level graduation discussion.

Date of the last release:

  Apache PredictionIO 0.11.0-incubating on 2017-04-25

When were the last committers or PMC members elected?

  Naoki Takezoe was elected as committer and PMC member on Apr 28, 2017.
  Shinsuke Sugaya was elected as committer and PMC member on Apr 28, 2017.
  Takahiro Hagino was elected as committer and PMC member on Apr 28, 2017.
  Takako Shimamoto was elected as committer and PMC member on Apr 28, 2017.
  Sara Asher was elected as product manager and JIRA administrator on Apr
30, 2017.

[ANNOUNCE] Apache PredictionIO 0.11.0-incubating Release

[Donald Szeto]

The Apache PredictionIO team would like to announce the release of Apache
PredictionIO 0.11.0-incubating.

Release notes are here:
https://github.com/apache/incubator-predictionio/blob/v0.11.0-incubating/RELEASE.md

Apache PredictionIO (incubating) is an open source Machine Learning Server
built on top of state-of-the-art open source stack, that enables developers
to manage and deploy production-ready predictive services for various kinds
of machine learning tasks.

More details regarding Apache PredictionIO (incubating) can be found here:
http://predictionio.incubator.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/predictionio/0.11.0-incubating/

All JIRAs completed for this release are tagged with 'FixVersion =
0.11.0-incubating'; the JIRA release notes can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320420=12338381

Thanks!
The Apache PredictionIO Team

DISCLAIMER
Apache PredictionIO (incubating) is an effort undergoing incubation at the
Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.

[jira] [Created] (PIO-63) Fix incubator branding issues

[Donald Szeto (JIRA)]

Donald Szeto created PIO-63:
---

 Summary: Fix incubator branding issues
 Key: PIO-63
 URL: https://issues.apache.org/jira/browse/PIO-63
 Project: PredictionIO
  Issue Type: Bug
Affects Versions: 0.11.0-incubating
Reporter: Donald Szeto


{quote}
John D. Ament <johndam...@apache.org>

Please review the branding guide here: 
http://incubator.apache.org/guides/branding.html

Specifically, we expect all podlings to show a logo (the actual logo has 
changed) for the Incubator, and include a disclaimer (the same release 
disclaimer) on the website.  I can find neither on your website.
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)