wardlican commented on PR #3764:
URL: https://github.com/apache/amoro/pull/3764#issuecomment-3284193114

   > > To distinguish between the master-slave mode and the master-slave mode, 
the newly added master-slave mode should not affect the original logic. The 
master-slave mode will make more logical changes in TableServcie.
   > 
   > Will the two implementations be merged in the future? In the long run, the 
horizontally-scalable version is likely to become the default. If we do expect 
a single unified implementation eventually, we could simply switch between the 
two code paths with a config flag today instead of introducing a full SPI 
framework. After all, TableService is not intended to be opened up for 
third-party plug-ins down the road.
   > 
   > WDYT @zhoujinsong @Aireed
   
   Yes, the design here needs to decide whether to implement compatible logic 
through configuration in DefaultTableService.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to