[ https://issues.apache.org/jira/browse/SOLR-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745675#action_12745675 ]
Hoss Man commented on SOLR-1373: -------------------------------- bq. Anything that's commonly used should be in Solr's equivalent of advanced search Agreed ... but there is a risk that some "common" options aren't ubiqutious, so if we add them to the form people could get confused if a param doesn't work because the request handler they are using doesn't support it in the case of fq, i think the pros outway the cons ... that's why i committed your patch. bq. I'm curious why we're not interested in making a more advanced UI? i don't remember anyone saying that ... i just don't think hardcoding a bunch of params into form.jsp is the way to go. i'd love to see a good UI that could inspect the solr conifuration and display the appropriate options in a GUI -- ala the wiki page i mentioned (but aparently didn't link to) ... http://wiki.apache.org/solr/MakeSolrMoreSelfService > Add filter query in solr/admin/form.jsp > --------------------------------------- > > Key: SOLR-1373 > URL: https://issues.apache.org/jira/browse/SOLR-1373 > Project: Solr > Issue Type: Improvement > Components: web gui > Affects Versions: 1.3 > Reporter: Jason Rutherglen > Assignee: Hoss Man > Priority: Trivial > Fix For: 1.4 > > Attachments: SOLR-1373.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > The full interface needs a filter query text field. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.