[
https://issues.apache.org/jira/browse/SOLR-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999809#comment-13999809
]
Jan Høydahl commented on SOLR-6074:
-----------------------------------
There are still no well defined list of characters formally supported in field
names. Normally you're advised to stick to a-z0-9 as well as underscore or
dash, but it will most often work with a lot of strange chars, but you may see
some components fail while other works.
Some known limitation is e.g. spaces not allowed in function queries, and
fields cannot start with "-" since that will be parsed as NOT in a query etc
etc. I'm pretty sure that ":" will cause trouble in far more places than the
UI, so simply stay away from it.
Perhaps this JIRA should result in an updated documentation on supported field
name recommendation?
> Field names with colons doesn't work on the query screen on the web UI
> ----------------------------------------------------------------------
>
> Key: SOLR-6074
> URL: https://issues.apache.org/jira/browse/SOLR-6074
> Project: Solr
> Issue Type: Bug
> Components: web gui
> Affects Versions: 4.4
> Environment: linux debian testing / LL(ighthttpd)MP stack with drupal
> as the web frontend
> Reporter: Ariel Barreiro
> Priority: Minor
>
> I was looking into a search not working from the frontend and I wanted to
> check on how the data was inserted. I was unable to run any proper query that
> provides useful results other than *:*.
> Even more, when I followed the links from the schema browser from the Top
> Results for the field I was interested in querying, I was redirected to the
> query and again no results although there's obviously some because they
> appear as top results on the search page.
> By speaking with steffkes in #irc, he pointed out that the field name in
> question had a colon in its name, like:
> "fieldname:name"
> So the search ended up being
> q=fieldname:name:DATA
> He suggested to escape the colon as fieldname\:name, but that made no
> difference.
> In the end, there was a setting in the drupal plugin I am using
> (https://drupal.org/project/search_api_solr) that mentioned about cleaning
> the field ids to remove that colon in the field name, which I tried, and then
> I coiuld properly use the web ui to query results. New field name is
> fieldname$name.
> I quote a bit of the README from that module related to this:
> "This will change the Solr field names used for all
> fields whose Search API identifiers contain a colon (i.e., all nested
> fields)
> to support some advanced functionality, like sorting by distance, for which
> Solr is buggy when using field names with colons.
> "
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
