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

ASF subversion and git services commented on SOLR-16409:
--------------------------------------------------------

Commit 52e0350f6bad2f535cc10e21ae9e230539600552 in solr's branch 
refs/heads/pr/1067 from wlam183
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=52e0350f6ba ]

Merge branch 'main' into SOLR-16409


> Admin UI - Expose all highlighting parameters in the Query UI
> -------------------------------------------------------------
>
>                 Key: SOLR-16409
>                 URL: https://issues.apache.org/jira/browse/SOLR-16409
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Admin UI
>            Reporter: Jeanie Lam
>            Assignee: Eric Pugh
>            Priority: Minor
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Currently, the Query UI only exposes some [common highlighting 
> parameters|https://solr.apache.org/guide/solr/latest/query-guide/highlighting.html#common-highlighter-parameters]
>  and do not expose any parameters that are specific to certain highlighting 
> implementation(s).
> In [https://github.com/apache/solr/pull/768#issuecomment-1217894430], 
> [~epugh] suggested we could try exposing all common parameters and grouped 
> the specific ones under collapsible lists
> {quote}I'd be interested in seeing what the Query UI would look like if we 
> actually exposed all the Common parameters, and introduced new check boxes 
> for Unified, Original, and FastVector.... I'm supposing that the logic in the 
> Query Admin UI would pretty much all be pretty boilerplate to do all of that.
> {quote}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to