Table Deprecation Plan

[trillhaa]

Is your feature request related to a problem? Please describe. Requesting to add a feature to support custom communications to downstream customers related to table events, in the instance of deprecation / migration / data quality issue etc.

Describe the solution you'd like As a table owner, I need the ability to send a communication to downstream customers in the scenario of deprecating a table. I shall be able to write a custom message with guidance on what is happening and by when a particular action needs to be completed.

Example

"Hello downstream customer, we are depreating table XYZ because of reason 123. You should migrate to table ABC by ETA. etc.."

As a table owner, I need the ability to choose between different notification types:

1. raising a ticket in internal ticketing system (most important)
2. Slack notification
3. Outlook email

I should be able to configure automatic followup reminders if a particular action hasn't been actioned or a ticket has not been resolved.

The feature should be able to detect relevant audience / downstream customers for the notification (e.g. based on "follower").

[harshach]

@vivekratnavel lets finish this in 0.11.1

[vivekratnavel]

We have completed the announcements feature that will ship in the 0.12 release. That covers most of the requirements listed in this issue. We will continue to work on email integration for notifications

[sureshms]

@vivekratnavel can you close this issue if the work is done and open a separate issue for email integration? Also, do we mark the table as deprecated so that people can filter for deprecation or is this just announcement alone? We can perhaps add some standard tags for the lifecycle of data that can include - deprecated, preview, etc.

[vivekratnavel]

Currently, we don't mark the table as deprecated. But, that is a good idea as well. I have created #6937 and #6939 to track these improvements.