Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/441
Also, this PR is from `develop` branch to `master`, but AFAIK this project
does not use `master`. So, it seems to be committed directly to the mainline
already.
---
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/441
I do not understand what this PR does.
Does this pull request fix that SparkException or cause it?
Is this a problem using Spark 2.2 and `pio batchpredict
Awesome! The docs for Batch Predict are finally live:
https://predictionio.incubator.apache.org/batchpredict/
On Mon, Oct 2, 2017 at 3:57 PM, Donald Szeto <don...@apache.org> wrote:
> Mars, it's fixed now.
>
> Re: https://issues.apache.org/jira/browse/INFRA-15208
>
> On Mon
"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
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
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
tell <apurt...@apache.org>
> > * Chan Lee <chan...@apache.org>
> > * Donald Szeto <don...@apache.org>
> > * Felipe Oliveira <fel...@apache.org>
> > * James Taylor <jtay...@apache.org>
> >
<emergentor...@apache.org>
> > * Andrew Kyle Purtell <apurt...@apache.org>
> > * Chan Lee <chan...@apache.org>
> > * Donald Szeto <don...@apache.org>
> > * Felipe Oliveira <fel...@apache.org>
> >
+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 <chanlee...@gmail.com
Github user mars closed the pull request at:
https://github.com/apache/incubator-predictionio/pull/435
---
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/435
Merged to
[release-0.12.0](https://github.com/apache/incubator-predictionio/tree/release/0.12.0)
by @chanlee514
---
Sorry I didn't catch this before RC1. Thank you Chan.
On Fri, Sep 15, 2017 at 12:35 PM, Chan Lee <chanlee...@gmail.com> 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/
> re
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
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
[
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
> >
> > 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
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
0.12.0.
https://github.com/apache/incubator-predictionio/pull/432
*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 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
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/428
ð looks good
---
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!
---
[
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
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
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/401
Yes @BrianOn99, I do believe [class loading for pio-shell is
fixed](https://github.com/apache/incubator-predictionio/blob/develop/bin/pio-shell#L59)
for the next release, or if you
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 <don...@apache.org> wrote:
> Thanks for the clarification Pat! It always help to ha
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/401
Hi @BrianOn99,
Adding that `--jars` option to `pio-shell` command is the right solution,
and then the "No suitable driver found" error can be solved by adding the
es look like.
Let's graduate. +1
*Mars
On Wed, Aug 30, 2017 at 15:21 Pat Ferrel <p...@occamsmachete.com> wrote:
> I have had several people tell me they want to wait until PIO is not
> incubating before using it. This even after explaining that “incubating”
> has m
[
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 &
[
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
[
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
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/421
I will resolve these conflicts today and then merge this PR.
---
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
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/425
Great Scala-style improvements here, @takezoe. Great to see this gardening
of the codebase ð¤
I'm wondering, in [PIO-110](https://issues.apache.org/jira/browse/PIO-110
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/421
ð
---
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
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/421
Based on these [Scala Concurrency/Thread Safety
docs](https://twitter.github.io/scala_school/concurrency.html#danger), I
believe simply annotating `@volatile` will cause
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/424
Thanks for your feedback @dszeto. I've addressed the code style & JIRA
issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio/pull/424
Implement Storage app & channel name-to-ID cache
When stress testing the Universal Recommender with high-concurrency
HTTP/REST queries, we observed that Elasticsearch tra
Github user mars commented on a diff in the pull request:
https://github.com/apache/incubator-predictionio/pull/421#discussion_r134630517
--- Diff:
storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/StorageClient.scala
---
@@ -18,27 +18,84
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/421
Cheers @takezoe I addressed all your Scala style & usage suggestions. Still
need to take care of the threadsafety issue with the singleton client.
---
If your project is se
[
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
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio/pull/421
Elasticsearch singleton client with authentication
Fixes both [PIO-106](https://issues.apache.org/jira/browse/PIO-106) &
[PIO-114](https://issues.apache.org/jira/browse/PIO
Github user mars closed the pull request at:
https://github.com/apache/incubator-predictionio/pull/420
---
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
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/420
Closing in favor of
https://github.com/apache/incubator-predictionio/pull/421
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/372
Closing in favor of
https://github.com/apache/incubator-predictionio/pull/421
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
[
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
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
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/420
Seem to solve this [long ago reported Elasticsearch connection
issue](https://github.com/elastic/elasticsearch/issues/3647)
---
If your project is set up for it, you can reply
Github user mars commented on a diff in the pull request:
https://github.com/apache/incubator-predictionio/pull/420#discussion_r132601642
--- Diff:
storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESEvaluationInstances.scala
---
@@ -110,28
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio/pull/420
[PIO-106] Elasticsearch 5.x StorageClient should reuse RestClient
Implements [PIO-106](https://issues.apache.org/jira/browse/PIO-106)
This PR moves to a singleton Elasticsearch
Yes that is the PR. When I checked out develop yesterday, I though it was
already merged. Apologies for my confusion.
I'd like to see if I can get that merged for the release. Looking into it now.
*Mars
( <> .. <> )
> On Aug 4, 2017, at 12:46, Donald Szeto <don...@apache.or
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
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio/pull/418
batchpredict docs
JIRA [PIO-111](https://issues.apache.org/jira/browse/PIO-111)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
[
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
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
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)
[
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
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/412
@takezoe thank you for the feedback. As a relatively-new Scala programmer I
really appreciate this kind of review.
I am a bit hesitant to make these changes. I'm trying
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio/pull/412
Batch Predictions
JIRA issue [PIO-105](https://issues.apache.org/jira/browse/PIO-105)
Provides a new `pio batchpredict` command.
Reads from multi-object JSON input
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
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio/pull/401
Back in May, we fixed an intermittent class loading problem by [making a
change to stabilize the
classpath](https://github.com/mars/incubator-predictionio/commit
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio/pull/406
[PIO-102] Fix ESEngineInstances `getAll` results out of order
(Elasticsearch 5.x)
Fix for [PIO-102](https://issues.apache.org/jira/browse/PIO-102)
You can merge this pull request
[
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
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
[
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
[
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
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
Github user mars commented on a diff in the pull request:
https://github.com/apache/incubator-predictionio/pull/394#discussion_r122527314
--- Diff: common/src/main/resources/application.conf ---
@@ -9,3 +9,7 @@ spray.can {
verbose-error-messages
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio/pull/394
Extend request timeout for REST API
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
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio/pull/393
Fix to show stacktrace for errors thrown in `queries.json` REST API
We were getting intractable errors from `queries.json` requests, like this
one without a stacktrace
[
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
[
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
[
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
[
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
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
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
Bravo Sara! PredictionIO is fortunate to have you!!!
*Mars
( <> .. <> )
On Wed, May 17, 2017 at 09:00 Donald Szeto <don...@apache.org
<mailto:don...@apache.org>> wrote:
Hi all,
The Project Management Committee (PMC) for Apache PredictionIO (incubating) has
as
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
Github user mars commented on a diff in the pull request:
https://github.com/apache/incubator-predictionio/pull/371#discussion_r113494975
--- Diff: storage/s3/build.sbt ---
@@ -0,0 +1,44 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
Github user mars commented on a diff in the pull request:
https://github.com/apache/incubator-predictionio/pull/372#discussion_r112755776
--- Diff:
storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/StorageClient.scala
---
@@ -18,27 +18,66
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio/pull/372
Elasticsearch basic HTTP authentication
Add optional username-password configuration for the new Elasticsearch 5
client; in `pio-env.sh` config:
```bash
# Optional basic
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 <steven@salesforce.com> wrote:
>
> [X] +1, accept RC as
Github user mars commented on the issue:
https://github.com/apache/incubator-predictionio-template-skeleton/pull/5
I've been trying to support `DataSourceTest` using an in-memory H2
database. Unfortunately, that's currently failing with:
```
[info] DataSourceTest
GitHub user mars opened a pull request:
https://github.com/apache/incubator-predictionio-template-skeleton/pull/5
Example Tests
This skeleton repo seems to be the authoritative starting point for
creating a new engine. Since testing is a great way to improve collaboration
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
84 matches
Mail list logo