Github user softwaredoug commented on a diff in the pull request:
https://github.com/apache/lucene-solr/pull/275#discussion_r153369232
--- Diff: solr/core/src/java/org/apache/solr/schema/FieldType.java ---
@@ -905,6 +905,7 @@ protected void checkSupportsDocValues() {
protected static final String ENABLE_GRAPH_QUERIES =
"enableGraphQueries";
private static final String ARGS = "args";
private static final String POSITION_INCREMENT_GAP =
"positionIncrementGap";
+ protected static final String SCORE_OVERLAPS = "scoreOverlaps";
--- End diff --
I have been thinking a lot about this!
- Solr currently exposes per-field query configuration as a fieldType
param, not query time (see [autoGeneratePhraseQueries and
enableGraphQueries](https://lucene.apache.org/solr/guide/6_6/field-type-definitions-and-properties.html#general-properties).
- Solr doesn't yet have a way to pass per-field configuration at query time
(my email about multiple analyzers proposes one system for doing this)
To do the latter, ideally you'd have an API that could let you see multiple
views/configs on the same field, such as the following which would search two
query-time versions of the actor field
`q=action movies&qf=actor_syn actor_nosyn^10 title
text&defType=edismax&qf.actor_nosyn.field=actor&qf.actor_nosyn.analyzer=without_synonyms&qf.actor_syn.field=actor&qf.actor_syn.analyzer=with_synonyms&qf.actor_syn&scoreOverlaps=pick_best`
I think this sort of syntax could be extremely powerful, and deal with the
ability to configure multiple query time analyzers. But a bridge too far for
this PR...
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
