FW: Solr 6.6.3: Cant create shard name with hyphen

-----Original Message-----
From: Jay Potharaju [mailto:jspotharaju@gmail.com]
Sent: 15 March 2018 10:54
To: solr-user@lucene.apache.org
Subject: Re: Solr 6.6.3: Cant create shard name with hyphen

nvm ....i see the first comment on the ticket ...that hypens are allowed but
not when it is the first character. It looks like 5.5 was the last version
where it was supported.
Thanks
Jay

Thanks
Jay Potharaju


On Wed, Mar 14, 2018 at 9:29 PM, Jay Potharaju <jspotharaju@gmail.com>
wrote:

> Thanks for the reply Shawn. Was this a recent change ? As per the
> ticket it was fixed in 6.0. Is this change(no hyphens as starting of
> name ) applicable to all 6x versions.
> Thanks
>
>
> > On Mar 14, 2018, at 6:25 PM, Shawn Heisey <apache@elyograg.org> wrote:
> >
> >> On 3/14/2018 6:20 PM, Jay Potharaju wrote:
> >> I am creating a new collection in solr 6.6.3 and it wont allow me
> create a
> >> shard with hyphen. This ticket(
> >> https://issues.apache.org/jira/browse/SOLR-8725) was closed earlier.
> But it
> >> is not working for me in 6.6.3.
> >> Upgrading from 5.3 to 6.6.3.
> >
> > I can get 6.6.3 to create cores/collections with a hyphen in the
> > name -- unless the hyphen is the first character.
> >
> > Names with hyphens as the first character are not allowed. This is
> > an example of a name that is likely to not work properly with all
> > Solr features. It is extremely unlikely that this rule will be changed.
> >
> > I can see from previous email you've sent to the list that you have
> > asked about SolrCloud, so I'm betting you're running in cloud mode.
> >
> > If you were in standalone mode, then I would say that you can
> > probably override this behavior by creating the index with an
> > allowed name, stopping Solr, renaming directories, editing
> > core.properties files, and starting Solr back up ... but if you're
> > in cloud mode, the names are also in ZooKeeper. There are no easy
> > tools that I know of for editing the ZK database.
> >
> > You are free to change the source code to remove the restrictions
> > that have been added ... but those restrictions were put in place
> > for good reason. Even if you manage to create an index with a name
> > that's currently not allowed, that name might have problems with at
> > least one Solr feature.
> >
> > Thanks,
> > Shawn
> >
>