Make upsert metadata manager pluggable#9186
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9186 +/- ##
============================================
- Coverage 70.04% 68.45% -1.59%
- Complexity 5003 5005 +2
============================================
Files 1852 1854 +2
Lines 98760 98782 +22
Branches 15021 15025 +4
============================================
- Hits 69175 67625 -1550
- Misses 24709 26373 +1664
+ Partials 4876 4784 -92
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
...nt-local/src/main/java/org/apache/pinot/segment/local/upsert/TableUpsertMetadataManager.java
Outdated
Show resolved
Hide resolved
pinot-segment-local/src/main/java/org/apache/pinot/segment/local/upsert/RecordLocation.java
Outdated
Show resolved
Hide resolved
pinot-spi/src/main/java/org/apache/pinot/spi/config/table/UpsertConfig.java
Outdated
Show resolved
Hide resolved
|
Can the DedupManager be accomodated to implement this interface or should we do something else? IMO, it doesn't make sense to keep a seperate dedup config as as well as a seperate implementation with these changes. |
We may revisit the dedup after finishing the upsert improvement. IMO dedup won't share the same config or interface because they are different feature and trying to address different problems. The initial version of dedup shares a lot of code with upsert, but in the future we might want to handle them differently. |
|
Makes sense. Overall LGTM! |
TableUpsertMetadataManagerandPartitionUpsertMetadataManagerUpsertConfigfor custom class and properties:metadataManagerClassandproperties