I am building a bunch of self-contained ES examples in different
directories. I am trying to figure out the easiest way to point ES to
various locations with minimum absolute paths hardcoded.
Is there a way to point one variable to some sort of home for
everything (elasticsearch.yml, logging.yml, data, logs, etc) to be
relative to that? Or using relative directories in the
elasticsearch.yml in a way that I could just clone that directory
structure to a new example.
I have tried elasticsearch -Des.config and it picks up my config file
but the default paths do not change and are still within ES's install
directory. Relative paths also seem to be relative to the install.
I guess I can do an environmental variable as a common root, but I
would still need to repeat that to point at my config file directly
anyway, right? I am hoping to reduce the call to one simple command
line to switch between examples.
On 13 October 2014 03:03, Alexandre Rafalovitch arafalov@gmail.com wrote:
Hello,
I am building a bunch of self-contained ES examples in different
directories. I am trying to figure out the easiest way to point ES to
various locations with minimum absolute paths hardcoded.
Is there a way to point one variable to some sort of home for
everything (elasticsearch.yml, logging.yml, data, logs, etc) to be
relative to that? Or using relative directories in the
elasticsearch.yml in a way that I could just clone that directory
structure to a new example.
I have tried elasticsearch -Des.config and it picks up my config file
but the default paths do not change and are still within ES's install
directory. Relative paths also seem to be relative to the install.
I guess I can do an environmental variable as a common root, but I
would still need to repeat that to point at my config file directly
anyway, right? I am hoping to reduce the call to one simple command
line to switch between examples.
On 13 October 2014 03:03, Alexandre Rafalovitch arafalov@gmail.com wrote:
Hello,
I am building a bunch of self-contained ES examples in different
directories. I am trying to figure out the easiest way to point ES to
various locations with minimum absolute paths hardcoded.
Is there a way to point one variable to some sort of home for
everything (elasticsearch.yml, logging.yml, data, logs, etc) to be
relative to that? Or using relative directories in the
elasticsearch.yml in a way that I could just clone that directory
structure to a new example.
I have tried elasticsearch -Des.config and it picks up my config file
but the default paths do not change and are still within ES's install
directory. Relative paths also seem to be relative to the install.
I guess I can do an environmental variable as a common root, but I
would still need to repeat that to point at my config file directly
anyway, right? I am hoping to reduce the call to one simple command
line to switch between examples.
You can use the same binaries, but if you setup multiple configs pointing
to different data directories then you can leverage -Des.config pointing to
each config and then run multiple instances.
On 13 October 2014 03:03, Alexandre Rafalovitch arafalov@gmail.com
wrote:
Hello,
I am building a bunch of self-contained ES examples in different
directories. I am trying to figure out the easiest way to point ES to
various locations with minimum absolute paths hardcoded.
Is there a way to point one variable to some sort of home for
everything (elasticsearch.yml, logging.yml, data, logs, etc) to be
relative to that? Or using relative directories in the
elasticsearch.yml in a way that I could just clone that directory
structure to a new example.
I have tried elasticsearch -Des.config and it picks up my config file
but the default paths do not change and are still within ES's install
directory. Relative paths also seem to be relative to the install.
I guess I can do an environmental variable as a common root, but I
would still need to repeat that to point at my config file directly
anyway, right? I am hoping to reduce the call to one simple command
line to switch between examples.
Regards,
Alex.
--
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.
To view this discussion on the web visit
--
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.
To view this discussion on the web visit
But I think, that's what I am not seeing the exact clarity.
-Des.config does not seem to affect the location of data and log
directories. So, they have to be set individually in the
elasticsearch.yml that the es.config points to. If I leave them as
default, they are relative to the ES binary, that is to say -
centralized.
I can set them as relative directories (just checked), but then they
are relative to the directory I am running the start command from,
which is not terribly stable unless I lock down the exact run
sequence.
You can use the same binaries, but if you setup multiple configs pointing to
different data directories then you can leverage -Des.config pointing to
each config and then run multiple instances.
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.