Hi Zuyu,
I understand your concern on non-availability of storage manager in
distributed case.
I am not sure I fully understand the following proposal:
> Could Foreman creates QueryManagers directly, instead of
PolicyEnforcer::admitQuery?
Can you elaborate?
Right now, storage manager is propagated from Foreman -> Policy Enforcer
-> Query Manager -> Query Context. Developing some kind of late binding
mechanism of storage manager can be one possible solution.
On 06/20/2016 12:42 PM, Zuyu Zhang wrote:
Hi Harshad,
I am working on the distributed query execution engine, and would like
to have a discussion regarding how both PolicyEnforcer and
QueryManager fit into the distributed case.
I was wondering if we could remove using StorageManager in
PolicyEnforcer. In other words, could Foreman creates QueryManagers
directly, instead of PolicyEnforcer::admitQuery?
The main concern is that like in Foreman, PolicyEnforcer will be
created in ForemanDistributed, which, however, does not have access to
StorageManager in the distributed case.
Any thoughts?
Cheers,
Zuyu
--
Thanks,
Harshad
