, there is actually no way to create a core or a
collection from the API, with a defined-at-once configset, without having to
do some CLI commands on the remote server?
Thanks for your reply,
Ben
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solrcloud-1-server-1-configset
On 12/7/2015 9:46 AM, bengates wrote:
> If I understand well, there is actually no way to create a core or a
> collection from the API, with a defined-at-once configset, without having to
> do some CLI commands on the remote server?
With SolrCloud, the only step that requires commandline is
ailable through the API.
Best,
Erick
On Sat, Dec 5, 2015 at 12:56 AM, bengates <benga...@aliceadsl.fr> wrote:
> I understand.
>
> How to do this via the API?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solrcloud-1-server-1-configs
I understand.
How to do this via the API?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solrcloud-1-server-1-configset-multiple-collections-multiple-schemas-tp4243584p4243737.html
Sent from the Solr - User mailing list archive at Nabble.com.
anks,
Ben
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solrcloud-1-server-1-configset-multiple-collections-multiple-schemas-tp4243584.html
Sent from the Solr - User mailing list archive at Nabble.com.
ction2* (verified by GETting
>/http://my.remote.addr:8983/solr/collection2/schema/fields/)
>
>How to prevent this behavior, since my collections have *different kind of
>datas*, and may have the same field names but not the same types?
>
>Thanks,
>Ben
>
>
>
>--
&g
