[
https://issues.apache.org/jira/browse/SENTRY-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nachiket Vaidya updated SENTRY-1604:
------------------------------------
Description:
When the query is:
{noformat}
alter table test_b partition (bbb = '111', aaa='222', ccc='333') rename to
partition (bbb = 'r1', aaa='r2', ccc='r3')
{noformat}
Update:
{noformat}
| 8375 | 8371 | 1469487373 | ALTER_PARTITION | test_a
| test_b
|
{"timestamp":1469487373,"servicePrincipal":"","server":"","table":"test_b","db":"test_a","values":{"111",
"222", "333"},"eventType":"ALTER_PARTITION"}
{noformat}
We need to provide more info in notification entry.
Currently, message factory for alter partition does not store new partition
values. It just stores old values. For alter partition with partition change,
we need both values.
In this fix, sentry message factory stores also new partition values in alter
partition message in addition to old values. Added unit test cases for the same.
Added new field "newValues" to store new partition values in
SentryJSONAlterPartitionMessage.
was:
When the query is:
{noformat}
alter table test_b partition (bbb = '111', aaa='222', ccc='333') rename to
partition (bbb = 'r1', aaa='r2', ccc='r3')
{noformat}
Update:
{noformat}
| 8375 | 8371 | 1469487373 | ALTER_PARTITION | test_a
| test_b
|
{"timestamp":1469487373,"servicePrincipal":"","server":"","table":"test_b","db":"test_a","values":{"111",
"222", "333"},"eventType":"ALTER_PARTITION"}
{noformat}
We need to provide more info in notification entry.
Currently, message factory for alter partition does not store new partition
values. It just stores old values. For alter partition with partition change,
we need both values.
In this fix, sentry message factory stores also new partition values in alter
partition message in addition to old values. Added unit test cases for the same.
> Sentry JSON message factory: Need more information in alter partition event
> ---------------------------------------------------------------------------
>
> Key: SENTRY-1604
> URL: https://issues.apache.org/jira/browse/SENTRY-1604
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Nachiket Vaidya
> Assignee: Nachiket Vaidya
> Labels: patch-available
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1604.0-sentry-ha-redesign.patch,
> SENTRY-1604.1-sentry-ha-redesign.patch, SENTRY-1604.2-sentry-ha-redesign.patch
>
>
> When the query is:
> {noformat}
> alter table test_b partition (bbb = '111', aaa='222', ccc='333') rename to
> partition (bbb = 'r1', aaa='r2', ccc='r3')
> {noformat}
> Update:
> {noformat}
> | 8375 | 8371 | 1469487373 | ALTER_PARTITION | test_a
> |
> test_b |
> {"timestamp":1469487373,"servicePrincipal":"","server":"","table":"test_b","db":"test_a","values":{"111",
> "222", "333"},"eventType":"ALTER_PARTITION"}
>
> {noformat}
> We need to provide more info in notification entry.
> Currently, message factory for alter partition does not store new partition
> values. It just stores old values. For alter partition with partition change,
> we need both values.
> In this fix, sentry message factory stores also new partition values in alter
> partition message in addition to old values. Added unit test cases for the
> same.
> Added new field "newValues" to store new partition values in
> SentryJSONAlterPartitionMessage.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
