I have looked into this issue as well. yml is a loose standard. Other
projects have created ways to incorporate "include" files, but there
is nothing in the official specification for them. Creating a
mechanism for include files should not be too hard, the question is if
you want to diverege from the original yml spec.
My reasoning for using a separate file is that the analysis portion of
the yml file changing for more often than the rest. It would be easier
to keep track/distribute of changes in a smaller file.
On Wed, Sep 19, 2012 at 7:25 AM, Jaap Taal email@example.com wrote:
The default elasticsearch.yml is quite extensive with lots of config, which
is great because you can easily add config params to your node.
However for our project we need to add filters and analyzers to the
index.analysis "object" in elasticsearch.yml.
This makes the elasticsearch.yml a bit confusing as lot's of the file are
about how elasticsearch runs.
I want to put the index.analysis stuff in a different file for clarity. Is
it possible to do so?