[jira] [Commented] (SENTRY-296) Sentry Service Client does not allow for connection pooling

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SENTRY-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390224#comment-14390224 ] 

Hadoop QA commented on SENTRY-296:
----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12708635/SENTRY-296.010.patch against master.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration
{color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/535/console

This message is automatically generated.

> Sentry Service Client does not allow for connection pooling
> -----------------------------------------------------------
>
>                 Key: SENTRY-296
>                 URL: https://issues.apache.org/jira/browse/SENTRY-296
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Lenni Kuff
>            Assignee: Colin Ma
>              Labels: grant/revoke
>         Attachments: SENTRY-296.001.patch, SENTRY-296.002.patch, SENTRY-296.003.patch, SENTRY-296.004.patch, SENTRY-296.005.patch, SENTRY-296.006.patch, SENTRY-296.007.patch, SENTRY-296.008.patch, SENTRY-296.009.patch, SENTRY-296.010.patch
>
>
> The Sentry Service Client does not allow for connection pooling because there is no way to:
> 1) Detect that a connection is broken
> 2) Re-open a broken connection
> This would allow for Sentry Service clients to implement connection pooling like:
> {code}
> if (!client.isOpen()) {
>   client.reopen();
> }
> {code}
> Currently, the only way to ensure connections are not broken is to open a new connection before every RPC.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)