[GitHub] incubator-predictionio-sdk-python pull request #22: Add travis test and Refa...

[marevol]

Github user marevol closed the pull request at:

https://github.com/apache/incubator-predictionio-sdk-python/pull/22


---

[GitHub] incubator-predictionio-sdk-python pull request #22: Add travis test and Refa...

[marevol]

GitHub user marevol reopened a pull request:

https://github.com/apache/incubator-predictionio-sdk-python/pull/22

Add travis test and Refactoring

I'll merge this PR after 
[PIO-117](https://issues.apache.org/jira/browse/PIO-117).

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

$ git pull https://github.com/marevol/incubator-predictionio-sdk-python 
travis

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

https://github.com/apache/incubator-predictionio-sdk-python/pull/22.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 #22


commit cddbd06a8bfa1c904d5b7652b4f1ee72703a0de6
Author: Shinsuke Sugaya 
Date:   2017-09-04T09:00:57Z

add travis and refactoring

commit edeaa98c932876a4937aee6fd5e8bc4f5fa39551
Author: Shinsuke Sugaya 
Date:   2017-09-08T00:09:38Z

use apache github repository




---

[GitHub] incubator-predictionio-sdk-python issue #22: Add travis test and Refactoring

[marevol]

Github user marevol commented on the issue:

https://github.com/apache/incubator-predictionio-sdk-python/pull/22
  
Run Travis.


---

[GitHub] incubator-predictionio pull request #428: [PIO-117] Cannot delete event data...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] incubator-predictionio-sdk-python issue #22: Add travis test and Refactoring

[marevol]

Github user marevol commented on the issue:

https://github.com/apache/incubator-predictionio-sdk-python/pull/22
  
Travis is not available in this repository...
I'll ask Infra to do that.


---

[GitHub] incubator-predictionio pull request #429: [PIO-118] ClassCastException from ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] incubator-predictionio issue #432: [PIO-120] Process hangs if Elasticsearch ...

[mars]

Github user mars commented on the issue:

https://github.com/apache/incubator-predictionio/pull/432
  
Would be great to have this included in 0.12.0 release.


---

[GitHub] incubator-predictionio pull request #432: [PIO-120] Process hangs if Elastic...

[mars]

GitHub user mars opened a pull request:

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

[PIO-120] Process hangs if Elasticsearch is not available during train

Fixes [PIO-120](https://issues.apache.org/jira/browse/PIO-120)

This changeset ensures that the process exits gracefully after ES 
connection error.

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

$ git pull https://github.com/mars/incubator-predictionio 
fix-es-hang-on-train

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

https://github.com/apache/incubator-predictionio/pull/432.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 #432


commit f1c7337e246c9bd2bed5cc080efcf3dc81e4b055
Author: Mars Hall 
Date:   2017-09-07T21:38:46Z

Graceful exit after ES connection error during train.




---

[GitHub] incubator-predictionio issue #428: [PIO-117] Cannot delete event data on ESL...

[mars]

Github user mars commented on the issue:

https://github.com/apache/incubator-predictionio/pull/428
  
👍  looks good


---

[GitHub] incubator-predictionio issue #430: [PIO-119] Bump up Elasticsearch to 5.5.2

[mars]

Github user mars commented on the issue:

https://github.com/apache/incubator-predictionio/pull/430
  
Just tested build, train, batchpredict, & deploy locally with ES 5.5.2.

👍  looks good!


---

[jira] [Commented] (PIO-117) Cannot delete event data on ESLEvents

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PIO-117:


Github user marevol closed the pull request at:

https://github.com/apache/incubator-predictionio-sdk-python/pull/22


> Cannot delete event data on ESLEvents
> -
>
> Key: PIO-117
> URL: https://issues.apache.org/jira/browse/PIO-117
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>
> For elasticsearch event storage, delete request does not work.
> {noformat}
> $ curl -XDELETE 
> "localhost:7070/events/AV5QAIH0VGhejKgUn-2J.json?accessKey=..."
> {
>   "message": "Did not find value which can be converted into java.lang.String"
> }
> {noformat}



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

[jira] [Commented] (PIO-117) Cannot delete event data on ESLEvents

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PIO-117:


Github user asfgit closed the pull request at:

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


> Cannot delete event data on ESLEvents
> -
>
> Key: PIO-117
> URL: https://issues.apache.org/jira/browse/PIO-117
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>
> For elasticsearch event storage, delete request does not work.
> {noformat}
> $ curl -XDELETE 
> "localhost:7070/events/AV5QAIH0VGhejKgUn-2J.json?accessKey=..."
> {
>   "message": "Did not find value which can be converted into java.lang.String"
> }
> {noformat}



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

[jira] [Commented] (PIO-118) ClassCastException from NullWritable to Text in ESEventsUtil

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PIO-118:


Github user asfgit closed the pull request at:

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


> ClassCastException from NullWritable to Text in ESEventsUtil
> 
>
> Key: PIO-118
> URL: https://issues.apache.org/jira/browse/PIO-118
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>
> {noformat}
> Caused by: java.lang.ClassCastException: org.apache.hadoop.io.NullWritable 
> cannot be cast to org.apache.hadoop.io.Text
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESEventsUtil$.getOptStringCol$1(ESEventsUtil.scala:58)
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESEventsUtil$.resultToEvent(ESEventsUtil.scala:68)
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESPEvents$$anonfun$5.apply(ESPEvents.scala:89)
> at 
> org.apache.predictionio.data.storage.elasticsearch.ESPEvents$$anonfun$5.apply(ESPEvents.scala:87)
> at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
> at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
> at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
> at 
> org.apache.spark.sql.catalyst.expressions.GeneratedClass$GeneratedIterator.processNext(Unknown
>  Source)
> at 
> org.apache.spark.sql.execution.BufferedRowIterator.hasNext(BufferedRowIterator.java:43)
> at 
> org.apache.spark.sql.execution.WholeStageCodegenExec$$anonfun$8$$anon$1.hasNext(WholeStageCodegenExec.scala:377)
> at 
> org.apache.spark.sql.execution.SparkPlan$$anonfun$2.apply(SparkPlan.scala:231)
> at 
> org.apache.spark.sql.execution.SparkPlan$$anonfun$2.apply(SparkPlan.scala:225)
> at 
> org.apache.spark.rdd.RDD$$anonfun$mapPartitionsInternal$1$$anonfun$apply$25.apply(RDD.scala:827)
> at 
> org.apache.spark.rdd.RDD$$anonfun$mapPartitionsInternal$1$$anonfun$apply$25.apply(RDD.scala:827)
> at 
> org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
> at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)
> at org.apache.spark.rdd.RDD.iterator(RDD.scala:287)
> at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:87)
> at org.apache.spark.scheduler.Task.run(Task.scala:99)
> at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:322)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ... 1 more
> {noformat}



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

[jira] [Commented] (PIO-120) Process hangs if Elasticsearch is not available during train

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PIO-120:


Github user mars commented on the issue:

https://github.com/apache/incubator-predictionio/pull/432
  
Would be great to have this included in 0.12.0 release.


> Process hangs if Elasticsearch is not available during train
> 
>
> Key: PIO-120
> URL: https://issues.apache.org/jira/browse/PIO-120
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.12.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
>
> I noticed that, when Elasticsearch is configured as meta storage, `pio train` 
> will hang with the following error unless Elasticsearch is on-line/available:
> {code}
> Exception in thread "main" java.net.ConnectException: Connection refused
>   at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>   at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:171)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:145)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:192)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Commented] (PIO-120) Process hangs if Elasticsearch is not available during train

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PIO-120:


GitHub user mars opened a pull request:

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

[PIO-120] Process hangs if Elasticsearch is not available during train

Fixes [PIO-120](https://issues.apache.org/jira/browse/PIO-120)

This changeset ensures that the process exits gracefully after ES 
connection error.

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

$ git pull https://github.com/mars/incubator-predictionio 
fix-es-hang-on-train

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

https://github.com/apache/incubator-predictionio/pull/432.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 #432


commit f1c7337e246c9bd2bed5cc080efcf3dc81e4b055
Author: Mars Hall 
Date:   2017-09-07T21:38:46Z

Graceful exit after ES connection error during train.




> Process hangs if Elasticsearch is not available during train
> 
>
> Key: PIO-120
> URL: https://issues.apache.org/jira/browse/PIO-120
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.12.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
>
> I noticed that, when Elasticsearch is configured as meta storage, `pio train` 
> will hang with the following error unless Elasticsearch is on-line/available:
> {code}
> Exception in thread "main" java.net.ConnectException: Connection refused
>   at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>   at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:171)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:145)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:192)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Updated] (PIO-120) Process hangs if Elasticsearch is not available during train

[Mars Hall (JIRA)]

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

Mars Hall updated PIO-120:
--
External issue URL: 
https://github.com/apache/incubator-predictionio/pull/432

> Process hangs if Elasticsearch is not available during train
> 
>
> Key: PIO-120
> URL: https://issues.apache.org/jira/browse/PIO-120
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.12.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
>
> I noticed that, when Elasticsearch is configured as meta storage, `pio train` 
> will hang with the following error unless Elasticsearch is on-line/available:
> {code}
> Exception in thread "main" java.net.ConnectException: Connection refused
>   at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>   at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:171)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:145)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:192)
>   at 
> org.apache.predictionio.shaded.org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Created] (PIO-120) Process hangs if Elasticsearch is not available during train

[Mars Hall (JIRA)]

Mars Hall created PIO-120:
-

 Summary: Process hangs if Elasticsearch is not available during 
train
 Key: PIO-120
 URL: https://issues.apache.org/jira/browse/PIO-120
 Project: PredictionIO
  Issue Type: Bug
  Components: Core
Affects Versions: 0.12.0-incubating
Reporter: Mars Hall
Assignee: Mars Hall


I noticed that, when Elasticsearch is configured as meta storage, `pio train` 
will hang with the following error unless Elasticsearch is on-line/available:

{code}
Exception in thread "main" java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at 
org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:171)
at 
org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:145)
at 
org.apache.predictionio.shaded.org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)
at 
org.apache.predictionio.shaded.org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:192)
at 
org.apache.predictionio.shaded.org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
at java.lang.Thread.run(Thread.java:745)
{code}




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

[jira] [Commented] (PIO-117) Cannot delete event data on ESLEvents

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PIO-117:


Github user mars commented on the issue:

https://github.com/apache/incubator-predictionio/pull/428
  
  looks good


> Cannot delete event data on ESLEvents
> -
>
> Key: PIO-117
> URL: https://issues.apache.org/jira/browse/PIO-117
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>
> For elasticsearch event storage, delete request does not work.
> {noformat}
> $ curl -XDELETE 
> "localhost:7070/events/AV5QAIH0VGhejKgUn-2J.json?accessKey=..."
> {
>   "message": "Did not find value which can be converted into java.lang.String"
> }
> {noformat}



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

[jira] [Commented] (PIO-119) Bump up Elasticsearch to 5.5.2

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PIO-119:


Github user mars commented on the issue:

https://github.com/apache/incubator-predictionio/pull/430
  
Just tested build, train, batchpredict, & deploy locally with ES 5.5.2.

  looks good!


> Bump up Elasticsearch to 5.5.2
> --
>
> Key: PIO-119
> URL: https://issues.apache.org/jira/browse/PIO-119
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>
> I encountered [this 
> problem|https://discuss.elastic.co/t/org-elasticsearch-hadoop-rest-eshadoopinvalidrequest-returned-400-bad-request/95803].
> To support elasticsearch 5.5, we need to update it.



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

Re: Graduation to TLP

[Andrew Purtell]

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  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  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 :
>> 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  wrote:
>> 
>> +1 for graduation
>> 
>>> On Tue, Sep 5, 2017 at 10:32 AM, Donald Szeto  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
>>> - 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  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 

0.12 Release and Rotation on Release Management

[Chan Lee]

Hi all,

It seems we are ready to push for 0.12 release. Since we have two
additional volunteers (Shinsuke and I) for release management, I think it
would be nice to rotate between releases depending on availability.

I can start the process for 0.12 release if no one objects.

Best,
Chan

Re: Graduation to TLP

[Pat Ferrel]

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  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 :
> 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  wrote:
> 
> +1 for graduation
> 
> On Tue, Sep 5, 2017 at 10:32 AM, Donald Szeto  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
>> - 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  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 

Re: Graduation to TLP

[takako shimamoto]

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 :
> 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  wrote:
>
> +1 for graduation
>
> On Tue, Sep 5, 2017 at 10:32 AM, Donald Szeto  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
>> - 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  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 
>> 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

[GitHub] incubator-predictionio issue #427: [PIO-116] PySpark Support

[dszeto]

Github user dszeto commented on the issue:

https://github.com/apache/incubator-predictionio/pull/427
  
@marevol Looks like Python 3 is also a hard requirement? This does not work 
when I run `pyspark` with Python 2.


---

[jira] [Commented] (PIO-119) Bump up Elasticsearch to 5.5.2

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PIO-119:


Github user dszeto commented on the issue:

https://github.com/apache/incubator-predictionio/pull/430
  
@mars may want to test this.


> Bump up Elasticsearch to 5.5.2
> --
>
> Key: PIO-119
> URL: https://issues.apache.org/jira/browse/PIO-119
> Project: PredictionIO
>  Issue Type: Improvement
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>
> I encountered [this 
> problem|https://discuss.elastic.co/t/org-elasticsearch-hadoop-rest-eshadoopinvalidrequest-returned-400-bad-request/95803].
> To support elasticsearch 5.5, we need to update it.



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

[GitHub] incubator-predictionio issue #430: [PIO-119] Bump up Elasticsearch to 5.5.2

[dszeto]

Github user dszeto commented on the issue:

https://github.com/apache/incubator-predictionio/pull/430
  
@mars may want to test this.


---

[jira] [Commented] (PIO-116) PySpark Support

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PIO-116:


Github user dszeto commented on the issue:

https://github.com/apache/incubator-predictionio/pull/427
  
@marevol Looks like Python 3 is also a hard requirement? This does not work 
when I run `pyspark` with Python 2.


> PySpark Support
> ---
>
> Key: PIO-116
> URL: https://issues.apache.org/jira/browse/PIO-116
> Project: PredictionIO
>  Issue Type: New Feature
>  Components: Core
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>
> This provides PySpark support with minimum PIO changes.
> 1. Support pyspark on pio-shell
> 2. Add python files to use pyspark
> 3. Add --main-py-file option to "pio train" to submit .py file to spark
> Note that this provides only fixes for Spark 2.x.
> (because this fixes expect to use SparkML)
> Sample project is:
> https://github.com/jpioug/predictionio-template-iris
> (For prediction API, Scala code is used.)



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