Github user dsmiley commented on the issue:
https://github.com/apache/lucene-solr/pull/531
Code changes seem good; I'll look closer and run tests.
PathHierarchyTokenizerFactory _might_ eventually be used at query time if
we had a syntax to say "get me all my ancestors". But given it's conditional
based on syntax, it can't easily go into the query analyzer, so I think it's
better to leave the query time chain simple/direct and we do this stuff when
looking at the syntax. I know this has evolved recently from where we were.
In this issue I removed PathHierarchyTokenizer from the index side because I
feel it's better to err on lighter-weight indexing at the expense of slower
queries since I think it's very likely a very low cost for what I think are
typical use-cases.
RE issue to discuss the syntax: yes a subtask of SOLR-12298. no hurry on
that one
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
