Re: Storing Elasticsearch configuraton and deploying new clusters

2014-08-05 Thread David Pilato 
I would prefer having a script file which do everything you need than storing 
mappings in config/

I find scripts more flexible. You can create index with specific settings, add 
mapping, inject some data...


My 2 cents.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


Le 5 août 2014 à 23:43, Hayden Muhl  a écrit :

We've been using Solr for the past several months, but have been considering 
Elasticsearch recently.

One think I can't quite wrap my head around is how to keep track of 
Elasticsearch cluster configuration. Solr is largely based on config files 
written in XML. These are very straight forward to handle. You store them in 
your repository, and when deploying a new system, you drop the config files in 
the right places and start up Solr.

Elasticsearch configuration all seems to happen via the API. If I set up a 
cluster for QA, and get it configured the way I want, how would I then go about 
deploying a production environment with the same configuration? What processes 
do people here use for deploying new environments?
-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/8DED0EB4-0BCB-4EFE-984D-AFCD54C648BA%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Re: Storing Elasticsearch configuraton and deploying new clusters

2014-08-05 Thread Mark Walkom 
You can store mappings on the filesystem -
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-conf-mappings.html

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com


On 6 August 2014 10:03, Hayden Muhl  wrote:

> I was thinking more in terms of things like mappings. The only way of
> setting up mappings that I can find is via the API. If I've set up and
> tested a particular way of indexing and querying my documents on a QA
> system, I want to set my production system up the same way. What is your
> process for doing this?
>
>
> On Tue, Aug 5, 2014 at 4:45 PM, Mark Walkom 
> wrote:
>
>> There are some settings you can set via the API, but not all.
>> The docs are pretty indepth so check out
>> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html
>>
>> Regards,
>> Mark Walkom
>>
>> Infrastructure Engineer
>> Campaign Monitor
>> email: ma...@campaignmonitor.com
>> web: www.campaignmonitor.com
>>
>>
>> On 6 August 2014 07:43, Hayden Muhl  wrote:
>>
>>>  We've been using Solr for the past several months, but have been
>>> considering Elasticsearch recently.
>>>
>>> One think I can't quite wrap my head around is how to keep track of
>>> Elasticsearch cluster configuration. Solr is largely based on config files
>>> written in XML. These are very straight forward to handle. You store them
>>> in your repository, and when deploying a new system, you drop the config
>>> files in the right places and start up Solr.
>>>
>>> Elasticsearch configuration all seems to happen via the API. If I set up
>>> a cluster for QA, and get it configured the way I want, how would I then go
>>> about deploying a production environment with the same configuration? What
>>> processes do people here use for deploying new environments?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "elasticsearch" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to elasticsearch+unsubscr...@googlegroups.com.
>>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "elasticsearch" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/elasticsearch/RDbwZSPSII0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> elasticsearch+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/CAGqgWec_r_o%3De9RQq3Hjk6sUcdv2%2BA_NoM%2BDPr5jTbJMg1tmSw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAEM624avLLZSqNp6U22q4h-FyrCuc9s%2Bamx1N-8do71jvGhqUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Storing Elasticsearch configuraton and deploying new clusters

2014-08-05 Thread Hayden Muhl 
I was thinking more in terms of things like mappings. The only way of
setting up mappings that I can find is via the API. If I've set up and
tested a particular way of indexing and querying my documents on a QA
system, I want to set my production system up the same way. What is your
process for doing this?


On Tue, Aug 5, 2014 at 4:45 PM, Mark Walkom 
wrote:

> There are some settings you can set via the API, but not all.
> The docs are pretty indepth so check out
> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: ma...@campaignmonitor.com
> web: www.campaignmonitor.com
>
>
> On 6 August 2014 07:43, Hayden Muhl  wrote:
>
>> We've been using Solr for the past several months, but have been
>> considering Elasticsearch recently.
>>
>> One think I can't quite wrap my head around is how to keep track of
>> Elasticsearch cluster configuration. Solr is largely based on config files
>> written in XML. These are very straight forward to handle. You store them
>> in your repository, and when deploying a new system, you drop the config
>> files in the right places and start up Solr.
>>
>> Elasticsearch configuration all seems to happen via the API. If I set up
>> a cluster for QA, and get it configured the way I want, how would I then go
>> about deploying a production environment with the same configuration? What
>> processes do people here use for deploying new environments?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to elasticsearch+unsubscr...@googlegroups.com.
>>
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "elasticsearch" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/elasticsearch/RDbwZSPSII0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAGqgWec_r_o%3De9RQq3Hjk6sUcdv2%2BA_NoM%2BDPr5jTbJMg1tmSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Storing Elasticsearch configuraton and deploying new clusters

2014-08-05 Thread Mark Walkom 
There are some settings you can set via the API, but not all.
The docs are pretty indepth so check out
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com


On 6 August 2014 07:43, Hayden Muhl  wrote:

> We've been using Solr for the past several months, but have been
> considering Elasticsearch recently.
>
> One think I can't quite wrap my head around is how to keep track of
> Elasticsearch cluster configuration. Solr is largely based on config files
> written in XML. These are very straight forward to handle. You store them
> in your repository, and when deploying a new system, you drop the config
> files in the right places and start up Solr.
>
> Elasticsearch configuration all seems to happen via the API. If I set up a
> cluster for QA, and get it configured the way I want, how would I then go
> about deploying a production environment with the same configuration? What
> processes do people here use for deploying new environments?
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Storing Elasticsearch configuraton and deploying new clusters

2014-08-05 Thread Hayden Muhl 
We've been using Solr for the past several months, but have been 
considering Elasticsearch recently.

One think I can't quite wrap my head around is how to keep track of 
Elasticsearch cluster configuration. Solr is largely based on config files 
written in XML. These are very straight forward to handle. You store them 
in your repository, and when deploying a new system, you drop the config 
files in the right places and start up Solr.

Elasticsearch configuration all seems to happen via the API. If I set up a 
cluster for QA, and get it configured the way I want, how would I then go 
about deploying a production environment with the same configuration? What 
processes do people here use for deploying new environments?

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.