[
https://issues.apache.org/jira/browse/SOLR-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318367#comment-14318367
]
Erick Erickson commented on SOLR-6997:
--------------------------------------
While this fix is easy enough, I'm -1 on it. The fact that Solr allows it is
not the same as supporting it. From the ref guide:
"Field names should consist of alphanumeric or underscore characters only and
not start with a digit"
I would vastly prefer to go the opposite way, fail any names that didn't follow
the rule above. Unfortunately, that would break existing installations and
require re-indexing, which is much too onerous. Historically I think supporting
"non-standard" field names was more an accident than intentional.
As far as query parsing is concerned, I'd be a bit afraid of this popping out
somewhere and messing up the NOT operator.
> Support distributed 'facet on same field different ways'
> --------------------------------------------------------
>
> Key: SOLR-6997
> URL: https://issues.apache.org/jira/browse/SOLR-6997
> Project: Solr
> Issue Type: Bug
> Components: faceting
> Affects Versions: 4.10.3
> Reporter: Pablo Queixalos
> Priority: Minor
> Labels: distributed_search
> Fix For: 4.10.4, 5.0
>
> Attachments:
> 0001-SEA-1284-field-facet-local-param-parsing-fails-on-fi.patch,
> 0001-honor-facet-field-local-params.patch
>
>
> SOLR-1351 brought the ability to facet on the same field differently using
> local parameters but distributed process ({{FacetComponent::FieldFacet}})
> does not honor local params from _facet string_.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
