lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Matheis (steffkes) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3820) Solr Admin Query form is missing some edismax request parameters
Date Thu, 13 Sep 2012 08:08:08 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454724#comment-13454724
] 

Stefan Matheis (steffkes) commented on SOLR-3820:
-------------------------------------------------

I'll see what i can do here - adding new fields is normally not a problem, a bit tricky are
the two checkboxes .. because right now, all settings which are (f.e.) facet related are named
facet.foo, facet.bar and so on - so it's easy to remove (or even, not add) them to the query
params .. but stopwords & lowercaseOperators are very generic :/

The first Idea was to loop over all "main" options and only allow sub-options if the parent
is checked .. but not sure if this works for all cases, so have to figure that out

bq. The ability to set field name aliases is also missing: f.myalias.qf=realfield.
Hum yes, right .. what about a textfield which is 1:1 used in the query-string, will that
be okay? 
                
> Solr Admin Query form is missing some edismax request parameters
> ----------------------------------------------------------------
>
>                 Key: SOLR-3820
>                 URL: https://issues.apache.org/jira/browse/SOLR-3820
>             Project: Solr
>          Issue Type: Bug
>          Components: web gui
>    Affects Versions: 4.0-BETA
>            Reporter: Jack Krupansky
>             Fix For: 4.0
>
>
> The following edismax parameters are missing from the Solr Admin Query form:
> uf - User Fields
> pf2 - bigram phrase boost fields
> pf3 - trigram phrase boost fields
> ps2 - phrase slop for bigram phrases
> ps3 - phrase slop for trigram phrases
> boost - multiplicative boost function
> stopwords - remove stopwords from mandatory "matching" component (true/false, defaults
to true)
> lowercaseOperators - Enable lower-case "and" and "or" as operators (true/false, defaults
to true)
> The ability to set field name aliases is also missing: f.myalias.qf=realfield.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message