keith-turner edited a comment on pull request #2096: URL: https://github.com/apache/accumulo/pull/2096#issuecomment-842460992
> My understanding of the original idea to create an "external" compactions, was to create them "external" to Accumulo... something Accumulo could "submit" work to do and not care about the implementation, and get back a new compacted file. That was never an explicit goal I had. To achieve this goal, thinking about the following. Currently the implementation of the coordinator and compactors components use a lot of internal Accumulo code. To move these to external repo would require refactoring them to use only API and SPI calls into Accumulo. To do this would require exposing a lot internal low level API/SPI calls related to compactions(not sure what these would be, that would need exploration). For this exercise to be useful these newly exposed API/SPI calls would have to be generally useful and not overfit (meaning the new API/SPI calls can only be used to implement the current design). To avoid overfitting, it seems we would need to have multiple other designs in mind that we could test against these new API/SPI calls to verify that we have not overfit. Is there another path other than what I have described? Does this path actually lower the complexity? I am not sure it would, I think the answer to that de pends on what these new API/SPI calls are. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
