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?
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?
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?
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+unsubscribe@googlegroups.com.
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?
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+unsubscribe@googlegroups.com.
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?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
