Refactor TableMerge to make it easier to add new merge strategies

Description

In looking over the code and looking over our inventory of possible merge strategies and potential targets (Hive, Phoenix, Kudu, S3, ADLS,...) , I can see a long list of merge strategies coming so it would be nice to make adding and maintaining and unit testing individual strategies easier and cleaner.

Environment

None

Assignee

Unassigned

Reporter

Douglas Moore

Labels

Reviewer

None

Story point estimate

None

Components

Priority

Medium