Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

t;don...@apache.org> wrote: > > > >> The doc build failed at Scaladoc: https://builds.apach > >> e.org/job/PredictionIO-build-site/78/console > >> > >> And this has blocked the subsequent publish build. I'll just go ahead > and > >> disable Scaladoc g

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

"Deploying an Engine" navigation section, but it's still not on the docs site: https://predictionio.incubator.apache.org/deploy/ On Mon, Oct 2, 2017 at 12:52 PM, Mars Hall <mars.h...@salesforce.com> wrote: > Thank you Chan! > > On Thu, Sep 28, 2017 at 9:02 AM, Chan Lee &l

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

Thank you Chan! On Thu, Sep 28, 2017 at 9:02 AM, Chan Lee <chanlee...@gmail.com> wrote: > My apologies. The doc site has been updated now. > -- *Mars Hall 415-818-7039 Customer Facing Architect Salesforce Platform / Heroku San Francisco, California <http://smart.sal

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

s that the infrastructure, communications, and decision >> making process have stabilized in a manner consistent with other >> successful >> ASF projects. While incubation status is not necessarily a reflection of >> the completeness or stability of the code, it does indicate that the >> project has yet to be fully endorsed by the ASF. >> >> > -- *Mars Hall 415-818-7039 Customer Facing Architect Salesforce Platform / Heroku San Francisco, California

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

tell <apurt...@apache.org> > > * Chan Lee <chan...@apache.org> > > * Donald Szeto <don...@apache.org> > > * Felipe Oliveira <fel...@apache.org> > > * James Taylor <jtay...@apache.org> > >

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

<emergentor...@apache.org> > > * Andrew Kyle Purtell <apurt...@apache.org> > > * Chan Lee <chan...@apache.org> > > * Donald Szeto <don...@apache.org> > > * Felipe Oliveira <fel...@apache.org> > >

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

+1 binding I checked: - build, train, deploy, & batchpredict - complete Elasticsearch 5.x functionality - Binaries work directly for Heroku deployment Such an exciting release! Thank you Chan, *Mars On Sun, Sep 17, 2017 at 11:31 AM, Chan Lee wrote: > > > This is the

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

> > Votes are tied to tag/commit by ASF convention, so a new RC and vote will > > be required. > > > > On Fri, Sep 15, 2017 at 10:57 AM Mars Hall <mars.h...@salesforce.com> > > wrote: > > > > > I just opened a release notes PR against apache

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

I just opened a release notes PR against apache:release/0.12.0, because that seems to be the right place. Chan, will that work okay with the release process? On Fri, Sep 15, 2017 at 10:20 AM, Mars Hall <mars.h...@salesforce.com> wrote: > Also, I'd love to directly link the PIO-* issu

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

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

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

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

[jira] [Created] (PIO-121) Authentication for Engine's HTTP API

Mars Hall created PIO-121: - Summary: Authentication for Engine's HTTP API Key: PIO-121 URL: https://issues.apache.org/jira/browse/PIO-121 Project: PredictionIO Issue Type: Improvement

Re: JIRAs to include in 0.12 Release

Wow, so many resolved issues, so much progress! Thank you for sharing this list Chan. [PIO-120] Process hangs if Elasticsearch is not available during train (pending) https://issues.apache.org/jira/browse/PIO-120 Would one of you folks review this simple fix PR? The, I'll merge it to make

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

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

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

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

Re: Graduation to TLP

Please continue to include me as a committer and PMC member. After some deliberation, I cannot take on further responsibility as VP at this time. *Mars On Tue, Sep 5, 2017 at 10:32 AM, Donald Szeto wrote: > Thanks for the clarification Pat! It always help to have Apache

Re: Graduation to TLP

gt; have a target version set to 0.12.0-incubating for graduation. 0.12.0 will > contain cleanups for minor license and copyright issues that were pointed > out in previous releases by IPMC. > > Let me know what you think. > > Regards, > Donald > > -- *Mars Hall 415-818-7039 Customer Facing Architect Salesforce Platform / Heroku San Francisco, California

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

[ https://issues.apache.org/jira/browse/PIO-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall resolved PIO-115. --- Resolution: Fixed > Cache name-to-ID lookups for Storage app &

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

[ https://issues.apache.org/jira/browse/PIO-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall resolved PIO-114. --- Resolution: Fixed > Elasticsearch 5.x StorageClient basic HTTP authenticat

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

[ https://issues.apache.org/jira/browse/PIO-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall resolved PIO-106. --- Resolution: Fixed > Elasticsearch 5.x StorageClient should reuse RestCli

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

[ https://issues.apache.org/jira/browse/PIO-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall updated PIO-114: -- External issue URL: https://github.com/apache/incubator-predictionio/pull/421 > Elasticsearch 5.x StorageCli

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

[ https://issues.apache.org/jira/browse/PIO-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall updated PIO-114: -- Description: Add optional username-password configuration for the new Elasticsearch 5 client; in {{conf/pio

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

Mars Hall created PIO-114: - Summary: Elasticsearch 5.x StorageClient basic HTTP authentication Key: PIO-114 URL: https://issues.apache.org/jira/browse/PIO-114 Project: PredictionIO Issue Type: New

Re: August 2017 Release

g> wrote: > > Hey Mars, > > Is this the PR in question? > https://github.com/apache/incubator-predictionio/pull/372 > > Regards, > Donald > > On Thu, Aug 3, 2017 at 11:49 AM, Mars Hall <m...@heroku.com> wrote: > >> Hit an Authenticated Elastic

Re: August 2017 Release

hade rule, but it is clearly breaking the authenicated Elasticsearch functionality. Any ideas how to solve this? *Mars ( <> .. <> ) > On Aug 3, 2017, at 11:02, Donald Szeto <don...@apache.org> wrote: > > On Thu, Aug 3, 2017 at 10:07 AM, Mars Hall <m...@heroku.c

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

[ https://issues.apache.org/jira/browse/PIO-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall updated PIO-111: -- External issue URL: https://github.com/apache/incubator-predictionio/pull/418 > Document pio batchpred

[jira] [Created] (PIO-109) Customizable HTTP server configuration

Mars Hall created PIO-109: - Summary: Customizable HTTP server configuration Key: PIO-109 URL: https://issues.apache.org/jira/browse/PIO-109 Project: PredictionIO Issue Type: Improvement

Re: New PMC member and committer: Mars Hall

Thank you Donald, I'm honored & excited to officially join the project! *Mars ( <> .. <> ) > On Jul 28, 2017, at 12:01, Donald Szeto <don...@apache.org> wrote: > > Hi all, > > The Project Management Committee (PMC) for Apache PredictionIO (incubating)

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

[ https://issues.apache.org/jira/browse/PIO-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall updated PIO-106: -- Description: When using the proposed [PIO-105 Batch Predictions|https://issues.apache.org/jira/browse/PIO-105

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

Mars Hall created PIO-105: - Summary: Batch Predictions Key: PIO-105 URL: https://issues.apache.org/jira/browse/PIO-105 Project: PredictionIO Issue Type: New Feature Components: Core

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

[ https://issues.apache.org/jira/browse/PIO-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall updated PIO-102: -- External issue URL: https://github.com/apache/incubator-predictionio/pull/406 Description: Using

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

Mars Hall created PIO-102: - Summary: ESEngineInstances `getAll` results out of order (Elasticsearch 5.x) Key: PIO-102 URL: https://issues.apache.org/jira/browse/PIO-102 Project: PredictionIO Issue

[jira] [Commented] (PIO-96) Storage corrupted by sharing databases between engines with different storage configs

[ https://issues.apache.org/jira/browse/PIO-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079272#comment-16079272 ] Mars Hall commented on PIO-96: -- Yes Kenneth, the same storage config can be used for (per my example

[jira] [Commented] (PIO-96) Storage corrupted by sharing databases between engines with different storage configs

[ https://issues.apache.org/jira/browse/PIO-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070626#comment-16070626 ] Mars Hall commented on PIO-96: -- Data corruption is an issue, we've seen it happen five times for various local

[jira] [Created] (PIO-96) Storage corrupted by sharing databases between engines with different storage configs

Mars Hall created PIO-96: Summary: Storage corrupted by sharing databases between engines with different storage configs Key: PIO-96 URL: https://issues.apache.org/jira/browse/PIO-96 Project: PredictionIO

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

[ https://issues.apache.org/jira/browse/PIO-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall updated PIO-94: - Description: We get intractable errors from some `queries.json` requests, like this one without a stacktrace: {code

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

[ https://issues.apache.org/jira/browse/PIO-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall updated PIO-94: - Description: We get intractable errors from some `queries.json` requests, like this one without a stacktrace

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

[ https://issues.apache.org/jira/browse/PIO-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall updated PIO-94: - Description: We get intractable errors from some `queries.json` requests, like this one without a stacktrace

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

[ https://issues.apache.org/jira/browse/PIO-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mars Hall updated PIO-94: - Description: We get intractable errors from some `queries.json` requests, like this one without a stacktrace

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

Mars Hall created PIO-94: Summary: Query parsing may throw intractable errors Key: PIO-94 URL: https://issues.apache.org/jira/browse/PIO-94 Project: PredictionIO Issue Type: Bug Components

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

Mars Hall created PIO-72: Summary: In `pio-shell` jdbc.StorageClient cannot be loaded Key: PIO-72 URL: https://issues.apache.org/jira/browse/PIO-72 Project: PredictionIO Issue Type: Bug

Re: New product manager: Sara Asher

Bravo Sara!  PredictionIO is fortunate to have you!!! *Mars ( <> .. <> ) On Wed, May 17, 2017 at 09:00 Donald Szeto > wrote: Hi all, The Project Management Committee (PMC) for Apache PredictionIO (incubating) has asked Sara Asher to become a

Re: New product manager: Sara Asher

Bravo Sara!  PredictionIO is fortunate to have you!!! On Wed, May 17, 2017 at 09:00 Donald Szeto wrote: > Hi all, > > The Project Management Committee (PMC) for Apache PredictionIO > (incubating) has asked Sara Asher to become a product manager, and we are > pleased to

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

My non-binding vote for rc2! [X] +1, accept RC as the official 0.11.0 release [ ] -1, do not accept RC as the official 0.11.0 release because... *Mars ( <> .. <> ) > On Apr 9, 2017, at 21:29, Steven Yan wrote: > > [X] +1, accept RC as the official 0.11.0 release >

Re: Remove engine registration

o production where a pre-existing PIO binary is available, but that seems like a risky practice for long-running systems. Thanks for listening, *Mars Hall Customer Facing Architect Salesforce App Cloud / Heroku San Francisco, California > On Sep 16, 2016, at 10:42, Donald Szeto <don...@ap