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

REP-45 Add option to delete replication data through UI #60

Merged
merged 9 commits into from
Apr 3, 2019

Conversation

peterhuffer
Copy link
Contributor

@peterhuffer peterhuffer commented Mar 29, 2019

What does this PR do?

Closed #52 to open against 0.2.x. I will apply comments from that PR.

  • Fixes an issue in the UI where clicking the save configuration button twice quickly would save 2 configurations with the same name
  • Adds option to delete replicated data when deleting a configuration. Only data replicated from another node to the local node will be deleted.
  • Add a scheduled deleter that checks for deleted configurations and cleans them up (runs every minute)
  • Add checks for deleting orphaned replication items (replication items without corresponding configurations or metacards).

Who is reviewing it (please choose AT LEAST two reviewers that need to approve the PR before it can get merged)?

@clockard @paouelle @kcover @mcalcote

How should this be tested? (List steps with links to updated documentation)

Make sure /solr can be accessed to check replication items.

  • Replicate and verify deleting data along with the replication.
  • Replicate and delete a config (preserve data). Delete a metacard and verify its corresponding replication item entry gets cleaned up.

Any background context you want to provide?

What are the relevant tickets?

Fixes #45

Screenshots (if appropriate)

image

Checklist:

  • Documentation Updated
  • Update / Add Unit Tests
  • Update / Add Integration Tests

@peterhuffer
Copy link
Contributor Author

Pushed up changes for comments on #45

try {
persistentStore.get(ReplicatorConfigImpl.class, configId);
persistentStore.get(ReplicatorConfigImpl.class, id);
} catch (NotFoundException | ReplicationPersistenceException e) {
Copy link
Contributor

Choose a reason for hiding this comment

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

we might want the ReplicationPersistenceException to bubble out, rather than just returning false when we actually don't know. Same goes for this method in the SiteManagerImpl

Copy link
Contributor

@paouelle paouelle left a comment

Choose a reason for hiding this comment

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

Minor comments left.

@Mock CatalogFramework catalogFramework;

@Before
public void setup() {
Copy link
Contributor

Choose a reason for hiding this comment

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

❓ Why use a setup method her as opposed to just putting this in the attribute initialization above?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No reason in particular.

Copy link
Member

@clockard clockard left a comment

Choose a reason for hiding this comment

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

Approving but the remaining "Beta" reference should be removed

@@ -43,7 +43,7 @@ const HelpDialog = props => {
return (
<Dialog open={open} onClose={handleClose} maxWidth='md'>
<DialogTitle variant='h6' id='help-dialog-title'>
{'Welcome to the Project Charleston BETA'}
Copy link
Member

Choose a reason for hiding this comment

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

This removes it from the welcome dialog but not the navbar at the top of the page. Looks like there is one more removal needed

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Whoops, removed.

@clockard
Copy link
Member

clockard commented Apr 2, 2019

Manually verified functionality ✅

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.

5 participants