Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
For framework supported policy managers, the rules of mapping history service to policy manager can be baked into code. For 3rd party impls, a simple config approach may suffice.
Ideally querying the HistoryLoggingService class should also work but that requires ripping out AppContext ( AppContext is in tez-dag, the logging interfaces need to be in tez-api ). Another approach would be via serviceloaders/pluggable factories that given a conf/history logging class construct and return back a policy manager.