You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2017/04/21 21:17:04 UTC

[jira] [Resolved] (SENTRY-1707) Add unit test to check response from HiveMetaStoreClient.getNextNotification when there is no new notification at Hive meta store

     [ https://issues.apache.org/jira/browse/SENTRY-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Na Li resolved SENTRY-1707.
---------------------------
    Resolution: Won't Fix

Sergio is making code changes for HIVE-15761 to return response with empty set to be more reliable. 

He cannot reproduce the null response on the Hive side even with no new updates in HMS. 

Hive returns null response only when query from HMS has exception. We don't know what exception happened when Hao was testing. 

He added unit test at Hive. So we don't need to add unit test in sentry for this case. 


> Add unit test to check response from HiveMetaStoreClient.getNextNotification when there is no new notification at Hive meta store
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SENTRY-1707
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1707
>             Project: Sentry
>          Issue Type: Test
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Na Li
>            Assignee: Na Li
>              Labels: test
>
> Hive meta store returns null response when there is no new notification. Thrift throws exception with this null response, and calling HiveMetaStoreClient.getNextNotification gets this exception. 
> The desired behavior is that Hive meta store returns normal response with set event. And the events set is empty. 
> This bug is tracked in https://issues.apache.org/jira/browse/HIVE-15761
> We need to add a unit test to expose this bug in Hive meta store. And Hive team can easily verify the fix with this unit test.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)