keith-turner edited a comment on pull request #2096: URL: https://github.com/apache/accumulo/pull/2096#issuecomment-842394039
> it seems that the way the external compactions are exposed through to the user in the compaction configuration is through the specially named externalQueue, which seems to be a special feature of the default compaction service. Is that correct? Its a feature of the default compaction planner, not the default compaction service. Each compaction service has a configured planner that decides what to compact where. The [default compaction planner](https://github.com/apache/accumulo/blob/3983cd23629789c1ed0020d01fdd968eabfe590f/core/src/main/java/org/apache/accumulo/core/spi/compaction/DefaultCompactionPlanner.java#L73) accepts the config externalQueue. It then takes this information and calls the SPI method [getExternalExecutor](https://github.com/apache/accumulo/blob/3983cd23629789c1ed0020d01fdd968eabfe590f/core/src/main/java/org/apache/accumulo/core/spi/compaction/ExecutorManager.java#L38). Anyone could write a compaction planner that uses external queues by calling this same SPI method. The planners configuration could work any way the author likes. -- 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]
