[
https://issues.apache.org/jira/browse/SOLR-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168994#comment-15168994
]
Jason Gerlowski commented on SOLR-8725:
---------------------------------------
For context, this was initially changed in SOLR-8308. You can read up on the
rationale/discussion there. To summarize, there were some issues with cores
becoming inaccessible after being renamed, when the new name contained quirky
characters. When enforcement was put in, the regex as written to match
existing Solr "recommendations", which suggest that identifiers should only
contain alphanumerics, periods, and underscores.
There's been some pushback on treating hyphens as invalid, particularly on
SOLR-8110, and on SOLR-8642. I think the current consensus is that this
behavior will be changed in SOLR-8110.
> Invalid name error with core names with hyphens
> -----------------------------------------------
>
> Key: SOLR-8725
> URL: https://issues.apache.org/jira/browse/SOLR-8725
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.5
> Reporter: Chris Beer
>
> In SOLR-8642, hyphens are no longer considered valid identifiers for cores
> (and collections?). Our solr instance was successfully using hyphens in our
> core names, and our affected cores now error with:
> marc-profiler_shard1_replica1:
> org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
> Invalid name: 'marc-profiler_shard1_replica1' Identifiers must consist
> entirely of periods, underscores and alphanumerics
> Before starting to rename all of our collections, I wonder if this decision
> could be revisited to be backwards compatible with previously created
> collections.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
