You are viewing a plain text version of this content. The canonical link for it is here.

Posted to solr-user@lucene.apache.org by Chris Ulicny <cu...@iq.media> on 2017/12/06 13:43:35 UTC

SOLR-10272

Hi all,

We are currently in the process of testing out solr 7.1, and I was running
into some strange issues with config upload and collection creation. After
some digging, I found SOLR-10272 which makes the configName parameter
necessary for collection creation, but all of our scripts for 6.X used the
old default behavior of matching collection name to the config set. The
resulting behavior was overwriting all of our named configs in zookeeper
with "_default" when the collections were created.

I am curious as to whether overwriting an _existing_ config with the
"_default" one was intended or not when the change was made. If it was, the
documentation for CREATE in the Collections API could do with an update,
because it currently seems to me at least like the behavior hasn't actually
changed from the 6.X behavior.

Thanks,
Chris

Re: SOLR-10272

Posted by Chris Ulicny <cu...@iq.media>.

Thanks Shawn,

That's great to hear. I'm glad the overwriting behavior is being reverted.

On Wed, Dec 6, 2017 at 10:33 AM Shawn Heisey <ap...@elyograg.org> wrote:

> On 12/6/2017 6:43 AM, Chris Ulicny wrote:
> > I am curious as to whether overwriting an _existing_ config with the
> > "_default" one was intended or not when the change was made. If it was,
> the
> > documentation for CREATE in the Collections API could do with an update,
> > because it currently seems to me at least like the behavior hasn't
> actually
> > changed from the 6.X behavior.
>
> See the discussion here:
>
> https://issues.apache.org/jira/browse/SOLR-11624
>
> The fix for this issue is planned for the 7.3 release.
>
> Thanks,
> Shawn
>
>

Re: SOLR-10272

Posted by Shawn Heisey <ap...@elyograg.org>.

On 12/6/2017 6:43 AM, Chris Ulicny wrote:
> I am curious as to whether overwriting an _existing_ config with the
> "_default" one was intended or not when the change was made. If it was, the
> documentation for CREATE in the Collections API could do with an update,
> because it currently seems to me at least like the behavior hasn't actually
> changed from the 6.X behavior.

See the discussion here:

https://issues.apache.org/jira/browse/SOLR-11624

The fix for this issue is planned for the 7.3 release.

Thanks,
Shawn