[
https://issues.apache.org/jira/browse/SOLR-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421953#comment-13421953
]
Hoss Man commented on SOLR-3674:
--------------------------------
Fix is to use a "query" analyzer that uses KeywordTokenizerFactory, or use the
{{"\{!term\}"}} QParser
I'll add some tests demonstrating usecase and update javadocs and example.
> PathHierarchyTokenizerFactory needs better docs, tests, and example config
> --------------------------------------------------------------------------
>
> Key: SOLR-3674
> URL: https://issues.apache.org/jira/browse/SOLR-3674
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 3.1, 4.0-ALPHA
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 4.0
>
>
> As noted by Alok Bhandari on the solr-user mailing list, the example
> configuration of PathHierarchyTokenizerFactory (in both the example
> schema.xml and in the factory javadocs) is not very useful to most people
> because it uses the tokenizer both at index and at query time.
> So a query like {{q=text_path_field:"/aaa/bbb/ccc"}} will not only match
> "/aaa/bbb/ccc" and "/aaa/bbb/ccc/ddd" but also "/aaa/" and "/aaa/xxxx" which
> is not likely what people expect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
