----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/62136/#review184757 -----------------------------------------------------------
sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HiveNotificationFetcher.java Lines 98 (patched) <https://reviews.apache.org/r/62136/#comment260964> Why can't we leave this to HMSFollower to handle this? sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HiveNotificationFetcher.java Lines 186 (patched) <https://reviews.apache.org/r/62136/#comment260965> Same here. - Vamsee Yarlagadda On Sept. 6, 2017, 10:50 p.m., Sergio Pena wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/62136/ > ----------------------------------------------------------- > > (Updated Sept. 6, 2017, 10:50 p.m.) > > > Review request for sentry, Alexander Kolbasov and Vamsee Yarlagadda. > > > Bugs: sentry-1928 > https://issues.apache.org/jira/browse/sentry-1928 > > > Repository: sentry > > > Description > ------- > > The patch is closing the HMS connections on the HiveNotificationFetcher if > any Exception occurrs. The HMSFollower has also code to close the connection > on any Exception, but I do it for legacy reasons as I think it is not > required anymore. The HMSFollower needs some refactoring, though. > > > Diffs > ----- > > > sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HMSFollower.java > d4feb380fa0f3bd5f237609a107295a2d23eae3b > > sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HiveNotificationFetcher.java > 4d329921bb4bc540992084687726155cb0373f0f > > > Diff: https://reviews.apache.org/r/62136/diff/1/ > > > Testing > ------- > > > Thanks, > > Sergio Pena > >
