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

2017-09-15 Thread Mars Hall 
Sorry I didn't catch this before RC1. Thank you Chan.

On Fri, Sep 15, 2017 at 12:35 PM, Chan Lee  wrote:

> Mars, this seems like a necessary change, so I'll create RC3 with the PR
> and additional updates here: http://predictionio.incubator.apache.org/
> resources/upgrade/
>
> If there are changes anyone would like to add, please let me know by today.
> I'll patch up another release tonight and send out a new email.
>
> Thanks,
> Chan
>
>
> On Fri, Sep 15, 2017 at 11:54 AM, Donald Szeto  wrote:
>
> > 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 
> > 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 
> > > 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 
> > > 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 
> > > >>> 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/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&
> projectId=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
> > >
> >
>



-- 
*Mars Hall
415-818-7039
Customer Facing Architect
Salesforce Platform / Heroku
San Francisco, California

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

2017-09-15 Thread Chan Lee 
Mars, this seems like a necessary change, so I'll create RC3 with the PR
and additional updates here: http://predictionio.incubator.apache.org/
resources/upgrade/

If there are changes anyone would like to add, please let me know by today.
I'll patch up another release tonight and send out a new email.

Thanks,
Chan


On Fri, Sep 15, 2017 at 11:54 AM, Donald Szeto  wrote:

> 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 
> 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 
> > 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 
> > > 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 
> > 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 
> > >>> 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/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
> >
>

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

2017-09-15 Thread 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  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 
> 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 
> > 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 
> 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 
> >>> 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/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
>

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

2017-09-15 Thread Mars Hall 
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 
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 
> 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  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 
>>> 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/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

[GitHub] incubator-predictionio pull request #435: Revise release notes: clarify brea...

2017-09-15 Thread mars 
GitHub user mars opened a pull request:

https://github.com/apache/incubator-predictionio/pull/435

Revise release notes: clarify breaking changes; link issue IDs to JIRA



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mars/incubator-predictionio patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-predictionio/pull/435.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #435


commit cbe7063c869611f7ece0613a16cf0bebf22e404e
Author: Mars Hall 
Date:   2017-09-15T17:53:02Z

Revise release notes: clarify breaking changes; link issue IDs to JIRA




---

[jira] [Updated] (PIO-95) Raise request timeout for REST API

2017-09-15 Thread Mars Hall (JIRA) 

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

Mars Hall updated PIO-95:
-
Summary: Raise request timeout for REST API  (was: Configurable request 
timeout for REST API)

> Raise 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)

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

2017-09-15 Thread Mars Hall 
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  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  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...
> >
> >
>



-- 
*Mars Hall
415-818-7039
Customer Facing Architect
Salesforce Platform / Heroku
San Francisco, California

[GitHub] incubator-predictionio-template-recommender pull request #19: [WIP] 0.12.0-i...

2017-09-15 Thread shimamoto 
GitHub user shimamoto opened a pull request:


https://github.com/apache/incubator-predictionio-template-recommender/pull/19

[WIP] 0.12.0-incubating release

waiting for official 0.12.0 release

You can merge this pull request into a Git repository by running:

$ git pull 
https://github.com/shimamoto/incubator-predictionio-template-recommender 
release-0.12.0-incubating

Alternatively you can review and apply these changes as the patch at:


https://github.com/apache/incubator-predictionio-template-recommender/pull/19.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #19


commit 9c431a6aecfdc67b73418256c63211368763a46b
Author: shimamoto 
Date:   2017-09-15T04:44:41Z

0.12.0-incubating release




---

[GitHub] incubator-predictionio-template-ecom-recommender pull request #14: [WIP] 0.1...

2017-09-15 Thread shimamoto 
GitHub user shimamoto opened a pull request:


https://github.com/apache/incubator-predictionio-template-ecom-recommender/pull/14

[WIP] 0.12.0-incubating release

waiting for official 0.12.0 release

You can merge this pull request into a Git repository by running:

$ git pull 
https://github.com/shimamoto/incubator-predictionio-template-ecom-recommender 
release-0.12.0-incubating

Alternatively you can review and apply these changes as the patch at:


https://github.com/apache/incubator-predictionio-template-ecom-recommender/pull/14.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #14


commit 5300fbc58b93b2eed1e4a9a212a4984e26f20ba5
Author: shimamoto 
Date:   2017-09-15T06:41:44Z

0.12.0-incubating release




---

[GitHub] incubator-predictionio-template-similar-product pull request #17: [WIP] 0.12...

2017-09-15 Thread shimamoto 
GitHub user shimamoto opened a pull request:


https://github.com/apache/incubator-predictionio-template-similar-product/pull/17

[WIP] 0.12.0-incubating release

waiting for official 0.12.0 release

You can merge this pull request into a Git repository by running:

$ git pull 
https://github.com/shimamoto/incubator-predictionio-template-similar-product 
release-0.12.0-incubating

Alternatively you can review and apply these changes as the patch at:


https://github.com/apache/incubator-predictionio-template-similar-product/pull/17.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #17


commit c7890692a968c2c087ed477a0af69ac595ecc0b2
Author: shimamoto 
Date:   2017-09-15T07:36:57Z

0.12.0-incubating release




---

[GitHub] incubator-predictionio-template-attribute-based-classifier pull request #12:...

2017-09-15 Thread shimamoto 
GitHub user shimamoto opened a pull request:


https://github.com/apache/incubator-predictionio-template-attribute-based-classifier/pull/12

[WIP] 0.12.0-incubating release

waiting for official 0.12.0 release

You can merge this pull request into a Git repository by running:

$ git pull 
https://github.com/shimamoto/incubator-predictionio-template-attribute-based-classifier
 release-0.12.0-incubating

Alternatively you can review and apply these changes as the patch at:


https://github.com/apache/incubator-predictionio-template-attribute-based-classifier/pull/12.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #12


commit 0e78268843093122d4d918941a69fadcf8b1e9ff
Author: shimamoto 
Date:   2017-09-15T08:34:25Z

0.12.0-incubating release




---

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

2017-09-15 Thread 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)

2017-09-15 Thread 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] [Comment Edited] (PIO-122) always get Error initializing storage client for source ELASTICSEARCH in 0.11 when pio train

2017-09-15 Thread dongjie.shi (JIRA) 

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

dongjie.shi edited comment on PIO-122 at 9/15/17 6:35 AM:
--

It  works correctly when I change PIO to version 0.10.0.
But for PIO 0.11.0, it always fail.


was (Author: glorysdj):
it is ok when i change pio to version 0.10.0

> 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)

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

2017-09-15 Thread dongjie.shi (JIRA) 

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

dongjie.shi commented on PIO-122:
-

it is ok when i change pio to version 0.10.0

> 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)