[
https://issues.apache.org/jira/browse/RANGER-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam resolved RANGER-4321.
------------------------------------
Resolution: Resolved
> RangerMDCFilter is not working as defined in RANGER-4024
> ---------------------------------------------------------
>
> Key: RANGER-4321
> URL: https://issues.apache.org/jira/browse/RANGER-4321
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Prashant Satam
> Assignee: Prashant Satam
> Priority: Major
> Fix For: 3.0.0
>
>
> As mentioned in RANGER-4024, the expected behavior is:
> when request-id is added in log pattern and RangerMDCFilter is enabled via
> property,
> when the request header contains request-id, request-id should be available
> in all the ranger admin logs. I tried to enable RangerMDCFilter by adding in
> web.xml, but it did not work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
