lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henrik (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-8110) Start enforcing field naming recomendations in next X.0 release?
Date Tue, 29 Mar 2016 08:29:25 GMT

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

Henrik edited comment on SOLR-8110 at 3/29/16 8:29 AM:
-------------------------------------------------------

Upon upgrading from 5.4.0 to 5.5.0 I got this:

{code}project-lms_shard5_replica2: org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
Invalid name: 'project-lms_shard5_replica2' Identifiers must consist entirely of periods,
underscores and alphanumerics{code}

Is it possible to enable support for dashes with a JVM arg (or something else)?  Or is there
a simple way of renaming a whole lot of solrcloud instances?  We have about 20 collections
across 30 servers that are affected by this.


was (Author: monti):
Upon upgrading from 5.4.0 to 5.5.0 I got this:

project-lms_shard5_replica2: org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
Invalid name: 'project-lms_shard5_replica2' Identifiers must consist entirely of periods,
underscores and alphanumerics

Is it possible to enable support for dashes with a JVM arg (or something else)?  Or is there
a simple way of renaming a whole lot of solrcloud instances?  We have about 20 collections
across 30 servers that are affected by this.

> Start enforcing field naming recomendations in next X.0 release?
> ----------------------------------------------------------------
>
>                 Key: SOLR-8110
>                 URL: https://issues.apache.org/jira/browse/SOLR-8110
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>         Attachments: SOLR-8110.patch, SOLR-8110.patch
>
>
> For a very long time now, Solr has made the following "recommendation" regarding field
naming conventions...
> bq. field names should consist of alphanumeric or underscore characters only and not
start with a digit.  This is not currently strictly enforced, but other field names will not
have first class support from all components and back compatibility is not guaranteed.  ...
> I'm opening this issue to track discussion about if/how we should start enforcing this
as a rule instead (instead of just a "recommendation") in our next/future X.0 (ie: major)
release.
> The goals of doing so being:
> * simplify some existing code/apis that currently use hueristics to deal with lists of
field and produce strange errors when the huerstic fails (example: ReturnFields.add)
> * reduce confusion/pain for new users who might start out unaware of the recommended
conventions and then only later encountering a situation where their field names are not supported
by some feature and get frustrated because they have to change their schema, reindex, update
index/query client expectations, etc...



--
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


Mime
View raw message