You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2016/04/19 19:55:25 UTC

[jira] [Updated] (SOLR-8990) UI: query links from the "Top Terms" table on the Schema Browser page should use the "term" parser

     [ https://issues.apache.org/jira/browse/SOLR-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man updated SOLR-8990:
---------------------------
    Attachment: SOLR-8990.patch

here's a patch that seems to fix things.

I was a little that angular didn't seem to have a built in mechanism for URI escaping things when building links, and after a bit of googling suggested that defining a 1 line "filter" was the right course of action, i was still surprised that we didn't seem to have one defined - so this patch adds one.

Now even terms like this link correctly from schema browser to the query screen...

{noformat}
curl -H 'Content-Type: application/json' --data-binary '[{"id":"HOSS", "foo_s":"= < \\\""}]' 'http://localhost:8983/solr/techproducts/update?commit=true'
{noformat}

[~upayavira] - does this look good to you? is there a better way to do this?

> UI: query links from the "Top Terms" table on the Schema Browser page should use the "term" parser
> --------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-8990
>                 URL: https://issues.apache.org/jira/browse/SOLR-8990
>             Project: Solr
>          Issue Type: Bug
>          Components: UI
>            Reporter: Hoss Man
>         Attachments: SOLR-8990.patch
>
>
> If you are using a StrField, or a TextField with a Keyword tokenizer then it's very possible your indexed terms will include white space.
> But the links created  by the Schema Browser UI screen to serach for a term in the "Top Terms" list assume that just prepending hte term with the fieldname (ie: {{$fieldname + ":" $term}}) will be valid -- and instead they don't match the correct term.
> ----
> Example: 
> Load the {{example/films}} data into a "films" collection, and then load the Schema Browser page for the "genre" field...
> http://127.0.1.1:8983/solr/#/films/schema?field=genre
> The "Top Terms" list includes terms such as {{Rommance Film}} but clicking on this term takes you to this URL...
> http://127.0.1.1:8983/solr/#/films/query?q=genre:Romance%20Film
> ...which is just doing a search for "genre:Romance" OR "Film" (in the default field)
> Instead it should link to...
> http://127.0.1.1:8983/solr/#/gettingstarted/query?q=%7B!term+f=genre%7DRomance+Film



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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