Create a PathHierarchyFilter [LUCENE-5459]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Lucene currently provides a PathHierarchyTokenizer which is good assuming the input is already how it should be while there are situations where the "path" to be split in multiple path tokens has to be changed / analyzed before so that it'd be useful to have the PathHierarchy capabilities also as a second step, for filtering stuff.
---
Migrated from [LUCENE-5459](https://issues.apache.org/jira/browse/LUCENE-5459) by Tommaso Teofili (@tteofili), updated May 09 2016
Contributor guide
Research direction
Start by reading the existing PathHierarchyTokenizer and related analysis components to understand how path tokens are currently produced. Determine the intended behavior for analyzing or changing a path before applying PathHierarchy capabilities, including the expected filtering contract and coverage needed to define completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100