[
https://issues.apache.org/jira/browse/FALCON-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Yadav updated FALCON-823:
------------------------------
Attachment: FALCON-823-v2.patch
Removed the dead code. It shouldn't have been there, my apologies.
{quote}
Looks like StringAlgorithm is the default. Can the original
RadixTree::find(key) be retained along with a RadixTree::find(key, algorithm)
{quote}
Done. Looks better now. Thanks!
{quote}
Can test be added to really test that the capability works end to end?
{quote}
Already have. I have added unit tests for various types of matching scenarios
in testFindUsingRegex for the regex algorithm and testSubstringPathFind,
testStringSplitFind for the StringAlgorithm matches. I have augmented them
further for some more scenarios. Do you see any cases which I might have missed
in tests?
> Add path matching ability
> --------------------------
>
> Key: FALCON-823
> URL: https://issues.apache.org/jira/browse/FALCON-823
> Project: Falcon
> Issue Type: Sub-task
> Components: general
> Reporter: Ajay Yadav
> Assignee: Ajay Yadav
> Attachments: FALCON-823-v2.patch, FALCON-823.patch
>
>
> Add ability to match paths against the keys stored in the store.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
