[
https://issues.apache.org/jira/browse/SOLR-6368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095414#comment-14095414
]
Erik Hatcher commented on SOLR-6368:
------------------------------------
#2 is my recommendation. Conflating analysis and query parsing is tricky
business. To have a comparable query parser testing page, it's not
(necessarily) about a specific field or type, but rather a query, a query
parser, and potentially many other parameters. For example, for dismax, you
need to specify qf at least, and likely you'd want pf and other parameters in
there to see how they work.
Personally, I like simply going to
/select?rows=0&defType=dismax&qf=fields...&debug=true and looking at that
output. Putting something like that into the admin UI would indeed be handy
though.
> Analysis UI should factor in a QueryParser
> ------------------------------------------
>
> Key: SOLR-6368
> URL: https://issues.apache.org/jira/browse/SOLR-6368
> Project: Solr
> Issue Type: Improvement
> Reporter: Varun Thacker
> Priority: Minor
>
> When I type in a query it gets parsed differently at search time (
> debug=query) than what I sees in the Analysis tab.
> I will happen when my queries are phrase queries, and has query time
> shingles/ multi word synonyms. The reason being the Analyzer sees it as 1
> token when doing a regular search VS multiple tokens when seeing it via the
> Analysis -> Field Value ( Query ) text box
> There could be two options -
> 1. In Admin UI -> Analysis -> Field Value ( Query ) text box we should also
> provide another text box for 'defType'. And the query gets parsed via the
> QParser specified. Briefly looking at FieldAnalysisRequestHandler it's not
> obvious to me if this is possible though.
> 2. Add another tab in the Admin UI which shows how a query gets parsed given
> the QueryParser
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
