[
https://issues.apache.org/jira/browse/SOLR-11698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276265#comment-16276265
]
David Smiley commented on SOLR-11698:
-------------------------------------
Nice; I think the approach is a nice balance of using Solr's existing
mechanisms and being sufficient to get the job done. It's quite plausible to
imagine this working for not just edismax but the default lucene parser as
well. Perhaps above, {{f.text_synonym_autophrase.qf=text}} should be
{{f.text_synonym_autophrase.f=text}} so that it's not edismax specific? Many
of the query parsers use 'f' for field. And 'qf' suggests we could have a list
with boosts which is not intended here (right?).
For a moment I toyed with a hypothetical syntax of using local-params within qf
but it seemed not right since we strictly use local-params for query parsing,
which is not for this context (field list with options).
> Query-time per-field query settings (ie analyzers, autoGeneratePhraseQueries,
> etc)
> ----------------------------------------------------------------------------------
>
> Key: SOLR-11698
> URL: https://issues.apache.org/jira/browse/SOLR-11698
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Doug Turnbull
>
> This is an issue wrt to [this email
> chain](http://lucene.472066.n3.nabble.com/Multiple-Query-Time-Analyzers-in-Solr-td4364540.html)
> created to discuss the ability to change the query time analyzer in Solr,
> with input from [~solrtrey], [~dsmiley], [~steve_rowe], and [~mkhludnev]
> Specifically, we ended up with the following
> _
> it seems like there's some consensus around
> - Creating multiple named analyzers per field
> - Referencing those analyzers by name at query time somehow
> I would advocate for refactoring edismax (or making a new query parser) that
> would allow you to specify per-field query configuration. Then I would
> advocate refactoring some of the flags autoGeneratePhraseQueries, etc to this
> query-time config. Then we could follow suit using the same syntax to specify
> the analyzer to use at query time.
> Perhaps more generally these configuration items can stay on the fieldType,
> but a syntax could allow them to be overriden per field at query time?
> Finally, another requirement I would add would be the ability to specify the
> same field twice in qf, but configured to be queries two different ways.
> Perhaps a syntax like qf=title:config1 title:config2? Where config1 and
> config2 modify fieldType query flags? Like
> fieldConfig.config1.autoGeneratePhraseQuerise=false&ieldConfig.config1.queryAnalyzer=no_synonyms
> This sort of thing would in my opinion help both enhance the power of Solr,
> but with a more consistent vision around how field-specific query settings
> could be organized
> _
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
