[
https://issues.apache.org/jira/browse/SENTRY-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129341#comment-16129341
]
Vamsee Yarlagadda commented on SENTRY-1885:
-------------------------------------------
I guess we have been using it as a unique property for the SENTRY_PATH_CHANGE
table.
https://github.com/apache/sentry/blob/master/sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/provider/db/service/model/package.jdo#L300
SENTRY-1803 allows duplicates to be saved. If that is the case, it would also
violate the above constraint right. Should we have to relax it as well?
> Remove unused NOTIFICATION_ID from the SENTRY_PATH_CHANGE table
> ---------------------------------------------------------------
>
> Key: SENTRY-1885
> URL: https://issues.apache.org/jira/browse/SENTRY-1885
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Sergio Peña
>
> I noticed while working on SENTRY-1803 that the SENTRY_PATH_CHANGE table has
> an unused column named NOTIFICATION_ID. I think this was used before to get
> the latest notification id processed, but now that process was moved to the
> SENTRY_HMS_NOTIFICATION_ID table.
> I think we should remove this unused column to avoid confusions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
