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

Christos Malliaridis commented on SOLR-8071:
--------------------------------------------

I am closing this ticket as it's parent was already closed. New options are now 
explored in the New UI and proposed via our current design proposals in 
[Figma|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=2-100&t=eixJKaZsYD5vsT3s-1].

If you have any ideas feel free to add comments there (as it is easier to take 
them into account together with anything else that is about to change), or 
leave a comment here, or migrate this ticket to an issue (not sub-task) to 
track separately.

> Rethink Query interface in admin UI
> -----------------------------------
>
>                 Key: SOLR-8071
>                 URL: https://issues.apache.org/jira/browse/SOLR-8071
>             Project: Solr
>          Issue Type: Sub-task
>          Components: Admin UI
>    Affects Versions: 5.3.1
>            Reporter: Shawn Heisey
>            Priority: Major
>
> Note from Upayavira on SOLR-7666:
> {quote}
> I agree that the query tab is difficult in that it expects you to know what 
> all these options mean. I'd love to see a new take on the query tab - a bit 
> more akin to what /browse does - a more traditional query interface. But it'd 
> take quite some thinking as to how to make it generic and work across all 
> datasets.
> Please do create a new ticket for this. I'm thinking about a "query builder" 
> that allows you to pick from a list of fields to query, then type in terms 
> you want to query from those fields, and it spits out a query string, much 
> like the query UI currently spits out a URL.
> {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