[
https://issues.apache.org/jira/browse/SENTRY-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063967#comment-16063967
]
Vadim Spector commented on SENTRY-1712:
---------------------------------------
To be precise, sentry-1520 leads to triggering full snapshots first between HMS
and Sentry, and, once it is complete, between Sentry and NN.
[~akolb] - Sentry-1520 was to address HMS and Sentry getting out of sync - if
they are out of sync, then Sentry and NN are certainly out of sync as well, so
fixing out-of-sync had to be a 2-stage process.
Therefore, I am a bit confused by the description of this JIRA - "Right now,
there is no way to manually force Sentry to get full snapshot." Sentry-1520 is
just such a mechanism.
Further clarification by [~LinaAtAustin] "sentry-1712 is about to force sentry
to get HMS full snapshot from HMS metastore" makes sense - it is indeed
different from Sentry-1520, but then perhaps the Description needs to be fixed
accordingly? Reductionist implementation would be a) trigger full HMS update to
MetastorePlugin with this JIRA, and b) use Sentry-1520 to propagate this change
further to Sentry and then NN, but that's, of course, not the only way to
implement it.
> Add capability to force Sentry to get full snapshot from HMS
> ------------------------------------------------------------
>
> Key: SENTRY-1712
> URL: https://issues.apache.org/jira/browse/SENTRY-1712
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Na Li
> Priority: Minor
> Fix For: sentry-ha-redesign
>
>
> Right now, there is no way to manually force Sentry to get full snapshot.
> We need to add this capability. That gives us more power to handle error
> condition and enable testing.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
