[
https://issues.apache.org/jira/browse/RANGER-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hbprotoss updated RANGER-3160:
------------------------------
Description:
RecursivePathResourceMatcher init variable _valueWithoutSeparator_ and
_valueWithSeparator_ in function isMatch(), which will lead to a race condition
that when the matcher is used for the first time and there are multiple threads
try to match the resource, _valueWithSeparator_ will be null in some scenario,
and match fails.
A patch is attached below based on master branch
was:RecursivePathResourceMatcher init variable _valueWithoutSeparator_ and
_valueWithSeparator_ in function isMatch(), which will lead to a race condition
that when the matcher is used for the first time and there are multiple threads
try to match the resource, _valueWithSeparator_ will be null in some scenario
> RecursivePathResourceMatcher race condition
> -------------------------------------------
>
> Key: RANGER-3160
> URL: https://issues.apache.org/jira/browse/RANGER-3160
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 2.1.0
> Reporter: hbprotoss
> Priority: Major
> Attachments:
> 0001-fix-RecursivePathResourceMatcher-race-condition.patch
>
>
> RecursivePathResourceMatcher init variable _valueWithoutSeparator_ and
> _valueWithSeparator_ in function isMatch(), which will lead to a race
> condition that when the matcher is used for the first time and there are
> multiple threads try to match the resource, _valueWithSeparator_ will be null
> in some scenario, and match fails.
>
> A patch is attached below based on master branch
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
