Re: August 2017 Release

2017-08-04 Thread Mars Hall 
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  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  wrote:
> 
>> Hit an Authenticated Elasticsearch 5.x problem on the current develop
>> branch.
>> 
>> I just tested the HEAD of develop by performing:
>> 
>>  ./make-distribution.sh \
>>-Dscala.version=2.11.8 \
>>-Dspark.version=2.1.0 \
>>-Dhadoop.version=2.7.3 \
>>-Delasticsearch.version=5.1.1
>> 
>> Then, tried build/train/deploy of our Universal Recommender template.
>> 
>> Locally, it makes it through train to the point when it saves to
>> Elasticsearch, failing with:
>> 
>>> Exception in thread "main" java.lang.NoSuchMethodError:
>> org.elasticsearch.client.RestClient.performRequest(
>> Ljava/lang/String;Ljava/lang/String;Ljava/util/Map;[Lorg/
>> apache/http/Header;)Lorg/elasticsearch/client/Response;
>>>  at org.template.EsClient$.createIndex(EsClient.scala:132)
>>>  at org.template.EsClient$.hotSwap(EsClient.scala:218)
>>>  at org.template.URModel.save(URModel.scala:86)
>> 
>> I tried deploying it to Heroku as well, and it fails much earlier when
>> simply connecting to Elasticsearch:
>> 
>>> remote: Exception in thread "main" 
>>> org.elasticsearch.client.ResponseException:
>> HEAD https://xx.us-east-1.bonsaisearch.net:443/pio_meta: HTTP/1.1 401
>> Unauthorized
>>> remote:   at org.elasticsearch.client.RestClient$1.completed(
>> RestClient.java:311)
>>> remote:   at org.elasticsearch.client.RestClient$1.completed(
>> RestClient.java:300)
>>> remote:   at shadeio.data.http.concurrent.BasicFuture.completed(
>> BasicFuture.java:119)
>>> remote:   at shadeio.data.http.impl.nio.client.
>> DefaultClientExchangeHandlerImpl.responseCompleted(
>> DefaultClientExchangeHandlerImpl.java:177)
>>> remote:   at shadeio.data.http.nio.protocol.
>> HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:
>> 436)
>>> remote:   at shadeio.data.http.nio.protocol.
>> HttpAsyncRequestExecutor.responseReceived(HttpAsyncRequestExecutor.java:
>> 309)
>>> remote:   at shadeio.data.http.impl.nio.
>> DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.
>> java:255)
>> 
>> 
>> These issues were previously found to be caused by this shade rule:
>>  https://github.com/apache/incubator-predictionio/blob/
>> develop/storage/elasticsearch/build.sbt#L42
>> 
>> It looks like the shaded package does not actually use the new
>> authentication code.
>> 
>> Chan Lee mentioned to me that he was only able to make the TravisCI build
>> pass by adding this shade 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  wrote:
>>> 
>>> On Thu, Aug 3, 2017 at 10:07 AM, Mars Hall  wrote:
>>> 
 I just opened a PR to add docs for batch predict.
 
 Moving forward with the 0.12.0 release sounds great. Today, I will pull
 develop and see how it's working with the Heroku buildpack.
 
>>> 
>>> Awesome. Thanks!
>>> 
>>> 
> On Aug 3, 2017, at 00:37, takako shimamoto 
>> wrote:
> 
> I think it's almost ready, and now we just have to update the current
> documentation.
> The deadline of several unresolved issues for Target Version/s:
> 0.12.0-incubating is extended, right?
 
>>> 
>>> Yes. Let's extend those that have not started working if there's no
>>> objection.
>> 
>>

Re: August 2017 Release

2017-08-04 Thread Donald Szeto 
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  wrote:

> Hit an Authenticated Elasticsearch 5.x problem on the current develop
> branch.
>
> I just tested the HEAD of develop by performing:
>
>   ./make-distribution.sh \
> -Dscala.version=2.11.8 \
> -Dspark.version=2.1.0 \
> -Dhadoop.version=2.7.3 \
> -Delasticsearch.version=5.1.1
>
> Then, tried build/train/deploy of our Universal Recommender template.
>
> Locally, it makes it through train to the point when it saves to
> Elasticsearch, failing with:
>
> > Exception in thread "main" java.lang.NoSuchMethodError:
> org.elasticsearch.client.RestClient.performRequest(
> Ljava/lang/String;Ljava/lang/String;Ljava/util/Map;[Lorg/
> apache/http/Header;)Lorg/elasticsearch/client/Response;
> >   at org.template.EsClient$.createIndex(EsClient.scala:132)
> >   at org.template.EsClient$.hotSwap(EsClient.scala:218)
> >   at org.template.URModel.save(URModel.scala:86)
>
> I tried deploying it to Heroku as well, and it fails much earlier when
> simply connecting to Elasticsearch:
>
> > remote: Exception in thread "main" 
> > org.elasticsearch.client.ResponseException:
> HEAD https://xx.us-east-1.bonsaisearch.net:443/pio_meta: HTTP/1.1 401
> Unauthorized
> > remote:   at org.elasticsearch.client.RestClient$1.completed(
> RestClient.java:311)
> > remote:   at org.elasticsearch.client.RestClient$1.completed(
> RestClient.java:300)
> > remote:   at shadeio.data.http.concurrent.BasicFuture.completed(
> BasicFuture.java:119)
> > remote:   at shadeio.data.http.impl.nio.client.
> DefaultClientExchangeHandlerImpl.responseCompleted(
> DefaultClientExchangeHandlerImpl.java:177)
> > remote:   at shadeio.data.http.nio.protocol.
> HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:
> 436)
> > remote:   at shadeio.data.http.nio.protocol.
> HttpAsyncRequestExecutor.responseReceived(HttpAsyncRequestExecutor.java:
> 309)
> > remote:   at shadeio.data.http.impl.nio.
> DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.
> java:255)
>
>
> These issues were previously found to be caused by this shade rule:
>   https://github.com/apache/incubator-predictionio/blob/
> develop/storage/elasticsearch/build.sbt#L42
>
> It looks like the shaded package does not actually use the new
> authentication code.
>
> Chan Lee mentioned to me that he was only able to make the TravisCI build
> pass by adding this shade 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  wrote:
> >
> > On Thu, Aug 3, 2017 at 10:07 AM, Mars Hall  wrote:
> >
> >> I just opened a PR to add docs for batch predict.
> >>
> >> Moving forward with the 0.12.0 release sounds great. Today, I will pull
> >> develop and see how it's working with the Heroku buildpack.
> >>
> >
> > Awesome. Thanks!
> >
> >
> >>> On Aug 3, 2017, at 00:37, takako shimamoto 
> wrote:
> >>>
> >>> I think it's almost ready, and now we just have to update the current
> >>> documentation.
> >>> The deadline of several unresolved issues for Target Version/s:
> >>> 0.12.0-incubating is extended, right?
> >>
> >
> > Yes. Let's extend those that have not started working if there's no
> > objection.
>
>

[GitHub] incubator-predictionio issue #387: Oracle databas supports

2017-08-04 Thread dszeto 
Github user dszeto commented on the issue:

https://github.com/apache/incubator-predictionio/pull/387
  
You will need to use `docker` commands to either read volumes that were 
attached to running containers. The test is designed to return non-zero exit 
code if any tests fail, so if you can run to the end with a zero exit code that 
would mean tests are passing.


---
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 #405: [PIO-63]Add incubator logo and disclaimer...

2017-08-04 Thread takezoe 
Github user takezoe commented on the issue:

https://github.com/apache/incubator-predictionio/pull/405
  
@dszeto I confirmed that my fix has been applied. Thanks for your help!


---
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-63) Fix incubator branding issues

2017-08-04 Thread ASF GitHub Bot (JIRA) 

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

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

Github user takezoe commented on the issue:

https://github.com/apache/incubator-predictionio/pull/405
  
@dszeto I confirmed that my fix has been applied. Thanks for your help!


> Fix incubator branding issues
> -
>
> Key: PIO-63
> URL: https://issues.apache.org/jira/browse/PIO-63
> Project: PredictionIO
>  Issue Type: Bug
>Affects Versions: 0.11.0-incubating
>Reporter: Donald Szeto
>Assignee: Naoki Takezoe
> Fix For: 0.12.0-incubating
>
>
> {quote}
> John D. Ament 
> Please review the branding guide here: 
> http://incubator.apache.org/guides/branding.html
> Specifically, we expect all podlings to show a logo (the actual logo has 
> changed) for the Incubator, and include a disclaimer (the same release 
> disclaimer) on the website.  I can find neither on your website.
> {quote}



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