[
https://issues.apache.org/jira/browse/SENTRY-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259857#comment-16259857
]
kalyan kumar kalvagadda edited comment on SENTRY-1999 at 11/22/17 1:26 PM:
---------------------------------------------------------------------------
Currently target version is update in below listed jira's. I'm updating them to
2.0.0
||Key||Summary||
|SENTRY-2058|CLONE - Set hadoop.tmp.dir to the maven build directory configured
on java.io.tmpdir|
|SENTRY-2047|isTableEmptyCore method in SentryStore has references to
MAuthzPathsMapping when it should be generic|
|SENTRY-2032|Leading Slashes need to removed when creating HMS path entries|
|SENTRY-2031|Add trigger mechanism for Sentry to pull full path snapshot from
HMS|
|SENTRY-2027|Create mechanism of delivering commands via WebUI|
|SENTRY-2014|Incorrect handling of HDFS paths with multiple slashes|
|SENTRY-1966|Improve logging of HMS sync data (paths and permissions) flowing
from Sentry to NameNode|
|SENTRY-1932|Improve logging for HMSPath|
|SENTRY-1915|Sentry is doing a lot of work to convert list of paths to HMSPaths
structure|
|SENTRY-1909|Improvements for memory usage when full path snapshot is sent from
Sentry to NN|
|SENTRY-1892|Reduce memory consumption of HMSPath$Entry and TPathEntry|
|SENTRY-1863|SENTRY-1829 Update Sentry website to reflect 1.8.0 release|
|SENTRY-1862|SENTRY-1829 Create 1.8.0 artifacts. sign and upload to sentry
package repo|
|SENTRY-1853|Add the log level access mechanism|
|SENTRY-1852|Refactor HMSFollower without renaming file|
|SENTRY-1851|SENTRY-872 Revert HMSFollower refactoring change|
|SENTRY-1847|SENTRY-1838 Integrate sentry with Hive 2.0.0|
|SENTRY-1843|SENTRY-1838 Fork sentry-binding-hive-follower package to support
Hive 2.x|
|SENTRY-1825|SENTRY-872 Dropping a Hive database/table doesn't cleanup the
permissions associated with it|
|SENTRY-1696|SENTRY-872 Expose time spent creating the initial snapshot as a
metric|
was (Author: kkalyan):
Currently target version is update in below listed jira's. I. updating them to
2.0.0
||Key||Summary||
|SENTRY-2058|CLONE - Set hadoop.tmp.dir to the maven build directory configured
on java.io.tmpdir|
|SENTRY-2047|isTableEmptyCore method in SentryStore has references to
MAuthzPathsMapping when it should be generic|
|SENTRY-2032|Leading Slashes need to removed when creating HMS path entries|
|SENTRY-2031|Add trigger mechanism for Sentry to pull full path snapshot from
HMS|
|SENTRY-2027|Create mechanism of delivering commands via WebUI|
|SENTRY-2014|Incorrect handling of HDFS paths with multiple slashes|
|SENTRY-1966|Improve logging of HMS sync data (paths and permissions) flowing
from Sentry to NameNode|
|SENTRY-1932|Improve logging for HMSPath|
|SENTRY-1915|Sentry is doing a lot of work to convert list of paths to HMSPaths
structure|
|SENTRY-1909|Improvements for memory usage when full path snapshot is sent from
Sentry to NN|
|SENTRY-1892|Reduce memory consumption of HMSPath$Entry and TPathEntry|
|SENTRY-1863|SENTRY-1829 Update Sentry website to reflect 1.8.0 release|
|SENTRY-1862|SENTRY-1829 Create 1.8.0 artifacts. sign and upload to sentry
package repo|
|SENTRY-1853|Add the log level access mechanism|
|SENTRY-1852|Refactor HMSFollower without renaming file|
|SENTRY-1851|SENTRY-872 Revert HMSFollower refactoring change|
|SENTRY-1847|SENTRY-1838 Integrate sentry with Hive 2.0.0|
|SENTRY-1843|SENTRY-1838 Fork sentry-binding-hive-follower package to support
Hive 2.x|
|SENTRY-1825|SENTRY-872 Dropping a Hive database/table doesn't cleanup the
permissions associated with it|
|SENTRY-1696|SENTRY-872 Expose time spent creating the initial snapshot as a
metric|
> Sanitize issues that are outstanding for 2.0.0 release
> ------------------------------------------------------
>
> Key: SENTRY-1999
> URL: https://issues.apache.org/jira/browse/SENTRY-1999
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Labels: release
> Fix For: 2.0.0
>
>
> Make sure all resolved issues have fix version and make sure all Jiras with
> fix version 2.0.0 are committed or moved out.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
