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 "mike st. john" <ms...@gmail.com> on 2013/11/09 03:39:01 UTC

creating collections dynamically.

Is there any way to create collections dynamically.


Having some issues using collections api, need to pass dataDir etc to the
cores  doesn't seem to
work correctly?


thanks.

msj

Re: creating collections dynamically.

Posted by "mike st. john" <ms...@gmail.com>.

thanks shawn,  i'll give it a try.


msj


On Fri, Nov 8, 2013 at 10:29 PM, Shawn Heisey <so...@elyograg.org> wrote:

> On 11/8/2013 7:39 PM, mike st. john wrote:
>
>> Is there any way to create collections dynamically.
>>
>>
>> Having some issues using collections api, need to pass dataDir etc to the
>> cores  doesn't seem to
>> work correctly?
>>
>
> You can't pass dataDir with the collections API. It is concerned with the
> entire collection, not individual cores. With SolrCloud, you really
> shouldn't be trying to override those things.  One reason you might want to
> do this is that you want to share one instanceDir with all your cores.
>  This is basically unsupported with SolrCloud, because the config is in
> zookeeper, not on the disk.  The dataDir defaults to $instanceDir/data.
>
> If you *really* want to go against recommendations and control all the
> directories yourself, you can build the cores using the CoreAdmin API
> instead of the Collections API.  The wiki page on SolrCloud has some
> details on how to do this.
>
> Thanks,
> Shawn
>
>

Re: creating collections dynamically.

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

On 11/8/2013 7:39 PM, mike st. john wrote:
> Is there any way to create collections dynamically.
>
>
> Having some issues using collections api, need to pass dataDir etc to the
> cores  doesn't seem to
> work correctly?

You can't pass dataDir with the collections API. It is concerned with 
the entire collection, not individual cores. With SolrCloud, you really 
shouldn't be trying to override those things.  One reason you might want 
to do this is that you want to share one instanceDir with all your 
cores.  This is basically unsupported with SolrCloud, because the config 
is in zookeeper, not on the disk.  The dataDir defaults to 
$instanceDir/data.

If you *really* want to go against recommendations and control all the 
directories yourself, you can build the cores using the CoreAdmin API 
instead of the Collections API.  The wiki page on SolrCloud has some 
details on how to do this.

Thanks,
Shawn