Conversation
making a backward compatible change
Codecov Report
@@ Coverage Diff @@
## master #9835 +/- ##
============================================
- Coverage 70.26% 64.26% -6.01%
- Complexity 4924 4976 +52
============================================
Files 1964 1913 -51
Lines 105055 102696 -2359
Branches 15907 15621 -286
============================================
- Hits 73822 66002 -7820
- Misses 26101 31916 +5815
+ Partials 5132 4778 -354
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 |
this as an argument
|
@Jackie-Jiang can you review this PR? can you also re-trigger the CI suite? The failed integration test runs fine locally. |
|
Suggest not changing the interface |
|
Spoke with @Jackie-Jiang offline. Closing this and will re-visit the pattern later. Tks! |
Passing
thisas an argument can lead to concurrency issues.Removing
TableDataManagerinstance fromTableUpsertMetadataManager#initinterface as it is not actually used.TableUpsertMetadataManageris created by theTableDataManager. Hence, any required data can be passed in directly without exposingthis.Note: Kept the change backward compatibility , although I don't see a reason why we can't just remove it. It is an internal API.
Label:
refactor