Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a TABLE_RENAME SNS Message Type #382

Merged
merged 1 commit into from
Feb 19, 2020

Conversation

raveeram
Copy link
Contributor

  • Today, Rename events are clubbed into the TABLE_UPDATE message type. This will help downstream event consumers (like Microbots) avoid processing irrelevant Update messages.

@@ -313,28 +317,39 @@ public void notifyOfTableUpdate(final MetacatUpdateTablePostEvent event) {
Metrics.CounterSNSNotificationTableUpdate.getMetricName());
}

private UpdateTableMessage createUpdateTableMessage(
private UpdateOrRenameTableMessageBase createUpdateorRenameTableMessage(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel it's better to have two methods createUpdateTableMessage() and createRenameTableMessage(), each of them will call this createUpdateorRenameTableMessage() with the corresponding message type.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Zhen. Normally I'd prefer the same, but in this case, the difference is just a statement (given the somewhat large method signature). I figured this should suffice as a middle-ground.

Copy link
Contributor

@zhljen zhljen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor refactor comments, others look good to me.

@raveeram raveeram merged commit bddcf08 into Netflix:master Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants