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/06/27 16:38:00 UTC
[jira] [Commented] (SENTRY-1815) Send new HMS snapshots to HDFS
requesting an old generation ID
[ https://issues.apache.org/jira/browse/SENTRY-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065080#comment-16065080 ]
Na Li commented on SENTRY-1815:
-------------------------------
[~spena] will this cover the scenario in Sentry-1784? Will this cover the scenario that some changes are removed before NN gets them?
> Send new HMS snapshots to HDFS requesting an old generation ID
> --------------------------------------------------------------
>
> Key: SENTRY-1815
> URL: https://issues.apache.org/jira/browse/SENTRY-1815
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Fix For: sentry-ha-redesign
>
>
> This is part of the work for SENTRY-1760.
> A new DB definition is already created that contains a generation ID for new HMS snapshots (SENTRY-1805). This new generation ID is persisted and code is implemented to read and update paths with a current generation ID (SENTRY-1781).
> This patch will these new HMS snapshots to HDFS whenever HDFS requests an old generation ID.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)