tree 6bf3e5cfe1f5a837a0d59d27b68e5e9df866b0bf
parent 906a704c5546a984a03e10f18f38f1506e4196ad
author Abhishek Agarwal <1477457+abhishekagarwal87@users.noreply.github.com> 1625135588 +0530
committer GitHub <noreply@github.com> 1625135588 +0530
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJg3ZnkCRBK7hj4Ov3rIwAAPUkIACKO6IoHcCASja/NltDy+B6g
 3mK8/J5aar8i2BHVrGbtuufYt2X34Uq7XUNDsf+eFXqPvyjbv4BBOOXdXwG9ZY+F
 cmipH9nzuJqU5QWa5m7YzahZ5eVF7IBC2O6Mujlloxk61cJIi3bZ/TzXklCZg919
 WcrHKqmICxd2GZroEuASxySAigZ0jQeQMkMzLG+3FenHLS+DrX9jTsdn1O0mQmE9
 e34im5IT8hLLknoOvtIkAj3CYVsctQsJSz1El4tkLipU3o9TLAmZqVnaPq8AtN5c
 ZcMWxnSjfSDq7vZHJ0qujFqzTqu7HVvHDqa7dd7CaxQEazfaegpL66nppjaqjrs=
 =vL5j
 -----END PGP SIGNATURE-----
 

Replace Processing ExecutorService with QueryProcessingPool (#11382)

This PR refactors the code for QueryRunnerFactory#mergeRunners to accept a new interface called QueryProcessingPool instead of ExecutorService for concurrent execution of query runners. This interface will let custom extensions inject their own implementation for deciding which query-runner to prioritize first. The default implementation is the same as today that takes the priority of query into account. QueryProcessingPool can also be used as a regular executor service. It has a dedicated method for accepting query execution work so implementations can differentiate between regular async tasks and query execution tasks. This dedicated method also passes the QueryRunner object as part of the task information. This hook will let custom extensions carry any state from QuerySegmentWalker to QueryProcessingPool#mergeRunners which is not possible currently.