GitHub settings for templates

2017-05-11 Thread Shinsuke Sugaya
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


[GitHub] incubator-predictionio pull request #383: Cache downloaded jars in Travis bu...

2017-05-11 Thread takezoe
GitHub user takezoe reopened a pull request:

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

Cache downloaded jars in Travis build

Sometimes Travis build fails in downloading jars. Maybe caching them makes 
Travis build stable and also decreases build time.

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

$ git pull https://github.com/takezoe/incubator-predictionio 
cache-travis-build

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

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


commit e45f24f8cc4a50f81ded99daeb74638a68b3915a
Author: Naoki Takezoe 
Date:   2017-05-11T12:40:04Z

Cache downloaded jars in Travis build

commit 13599e36fc2beb4e7e8f6616a0c8b73db37ba96f
Author: Naoki Takezoe 
Date:   2017-05-12T00:52:03Z

Cache other downloaded files as well




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio pull request #383: Cache downloaded jars in Travis bu...

2017-05-11 Thread takezoe
Github user takezoe closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio-template-ecom-recommender pull request #13: Fix warni...

2017-05-11 Thread asfgit
Github user asfgit closed the pull request at:


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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio-template-text-classifier pull request #13: Fix warnin...

2017-05-11 Thread asfgit
Github user asfgit closed the pull request at:


https://github.com/apache/incubator-predictionio-template-text-classifier/pull/13


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio-template-recommender pull request #17: Fix warnings

2017-05-11 Thread asfgit
Github user asfgit closed the pull request at:


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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: New PMC member and committer: Shinsuke Sugaya

2017-05-11 Thread Andrew Purtell
Congratulations, and welcome!


On Thu, May 11, 2017 at 12:50 AM, Shinsuke Sugaya  wrote:

> Thank you for this exciting opportunity.
> I'd like to work on new features/improvements for graduation from
> incubator.
>
> Regards,
>  shinsuke
>
> 2017-05-11 13:32 GMT+09:00 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
>



-- 
Best regards,

   - Andy

If you are given a choice, you believe you have acted freely. - Raymond
Teller (via Peter Watts)


[GitHub] incubator-predictionio issue #382: [PIO-64] Fixed a bug that JDBCPEvents uni...

2017-05-11 Thread dszeto
Github user dszeto commented on the issue:

https://github.com/apache/incubator-predictionio/pull/382
  
Hey @emergentorder, do you have a chance to take a look at this?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio pull request #383: Cache downloaded jars in Travis bu...

2017-05-11 Thread takezoe
GitHub user takezoe reopened a pull request:

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

Cache downloaded jars in Travis build

Sometimes Travis build fails in downloading jars. Maybe caching them makes 
Travis build stable.

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

$ git pull https://github.com/takezoe/incubator-predictionio 
cache-travis-build

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

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


commit e45f24f8cc4a50f81ded99daeb74638a68b3915a
Author: Naoki Takezoe 
Date:   2017-05-11T12:40:04Z

Cache downloaded jars in Travis build




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio pull request #383: Cache downloaded jars in Travis bu...

2017-05-11 Thread takezoe
GitHub user takezoe opened a pull request:

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

Cache downloaded jars in Travis build

Sometimes Travis build fails in downloading jars. Maybe caching them makes 
Travis build stable.

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

$ git pull https://github.com/takezoe/incubator-predictionio 
cache-travis-build

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

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


commit e45f24f8cc4a50f81ded99daeb74638a68b3915a
Author: Naoki Takezoe 
Date:   2017-05-11T12:40:04Z

Cache downloaded jars in Travis build




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio pull request #381: Fix sbt warnings

2017-05-11 Thread takezoe
GitHub user takezoe reopened a pull request:

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

Fix sbt warnings

Some operators are deprecated since sbt 0.13.13, so current sbt 
configuration causes following warnings. This pull request fix them.
```
[info] Compiling 1 Scala source to 
/Users/takezoe/Downloads/apache-predictionio-0.11.0-incubating/apache-predictionio-0.11.0-incubating/project/target/scala-2.10/sbt-0.13/classes...

/Users/takezoe/Downloads/apache-predictionio-0.11.0-incubating/apache-predictionio-0.11.0-incubating/build.sbt:86:
 warning: `<+=` operator is deprecated. Use `lhs += { x.value }`.
  sourceGenerators in Compile <+= buildInfo,
  ^

/Users/takezoe/Downloads/apache-predictionio-0.11.0-incubating/apache-predictionio-0.11.0-incubating/tools/build.sbt:38:
 warning: `<<=` operator is deprecated. Use `key := { x.value }` or `key ~= 
(old => { newValue })`.
See http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html
assemblyExcludedJars in assembly <<= (fullClasspath in assembly) map { cp =>
 ^

/Users/takezoe/Downloads/apache-predictionio-0.11.0-incubating/apache-predictionio-0.11.0-incubating/tools/build.sbt:58:
 warning: `<+=` operator is deprecated. Use `lhs += { x.value }`.
cleanFiles <+= baseDirectory { base => base.getParentFile /
   ^
[info] Set current project to apache-predictionio-parent (in build 
file:/Users/takezoe/Downloads/apache-predictionio-0.11.0-incubating/apache-predictionio-0.11.0-incubating/)
```

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

$ git pull https://github.com/takezoe/incubator-predictionio 
fix-sbt-warnings

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

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


commit 1dcbe1aade300a4b4053757ef94e371bc6baa54a
Author: Naoki Takezoe 
Date:   2017-05-06T17:07:48Z

Fix sbt warnings




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio issue #381: Fix sbt warnings

2017-05-11 Thread takezoe
Github user takezoe commented on the issue:

https://github.com/apache/incubator-predictionio/pull/381
  
Once close and reopen to re-run Travis build.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio-template-ecom-recommender pull request #13: Fix warni...

2017-05-11 Thread takezoe
GitHub user takezoe opened a pull request:


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

Fix warnings



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

$ git pull 
https://github.com/takezoe/incubator-predictionio-template-ecom-recommender 
fix-warnings

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


https://github.com/apache/incubator-predictionio-template-ecom-recommender/pull/13.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 #13


commit 10fbabf492cd5e9506c691f68207153aec24cf68
Author: Naoki Takezoe 
Date:   2017-05-11T09:36:03Z

Fix warnings




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio-template-text-classifier pull request #13: Fix warnin...

2017-05-11 Thread takezoe
GitHub user takezoe opened a pull request:


https://github.com/apache/incubator-predictionio-template-text-classifier/pull/13

Fix warnings



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

$ git pull 
https://github.com/takezoe/incubator-predictionio-template-text-classifier 
fix-warnings

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


https://github.com/apache/incubator-predictionio-template-text-classifier/pull/13.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 #13


commit e3f93c835f0905160fc4efc05405a714cf918d3e
Author: Naoki Takezoe 
Date:   2017-05-11T09:53:13Z

Fix warnings




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-predictionio-template-recommender pull request #17: Fix warnings

2017-05-11 Thread takezoe
GitHub user takezoe opened a pull request:


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

Fix warnings



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

$ git pull 
https://github.com/takezoe/incubator-predictionio-template-recommender 
fix-warnings

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


https://github.com/apache/incubator-predictionio-template-recommender/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 97857398a1f387b6c50811fbb6832e5cda866cf9
Author: Naoki Takezoe 
Date:   2017-05-11T08:32:00Z

Fix warnings




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


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

2017-05-11 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on PIO-64:
---

Github user dszeto commented on the issue:

https://github.com/apache/incubator-predictionio/pull/382
  
Hey @emergentorder, do you have a chance to take a look at this?


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

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

2017-05-11 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on PIO-64:
---

GitHub user shimamoto opened a pull request:

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

[PIO-64] Fixed a bug that JDBCPEvents unit tests fail intermittently

Revert the following commit which is the cause of the error:

https://github.com/apache/incubator-predictionio/commit/be3611d9d00625975f1f64de4cc6c1c829d8f542

For more information, see 
[here](https://issues.apache.org/jira/browse/PIO-64?focusedCommentId=16004227=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16004227).

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

$ git pull https://github.com/shimamoto/incubator-predictionio 
pio-64_unit-tests-fail

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

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


commit b623fb0b8c4bf6113c99564bd4d0d675f1526e05
Author: shimamoto 
Date:   2017-05-10T11:14:47Z

[PIO-64] Fixed a bug that JDBCPEvents unit tests fail intermittently.

Revert the following commit which is the cause of the error:

https://github.com/apache/incubator-predictionio/commit/be3611d9d00625975f1f64de4cc6c1c829d8f542




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

Re: New PMC member and committer: Shinsuke Sugaya

2017-05-11 Thread Shinsuke Sugaya
Thank you for this exciting opportunity.
I'd like to work on new features/improvements for graduation from incubator.

Regards,
 shinsuke

2017-05-11 13:32 GMT+09:00 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