Pelias scripts

Scripts (mostly written in groovy) that needs to be dropped in elasticsearch/config folder when used with pelias-api search queries that uses scripting.

Scripts are written to disk primarily to avoid dynamic scripting.

You could symlink this to your local elasticsearch config directory like so..

ln -s /path/to/pelias/scripts/scripts /path/to/elasticsearch/config/scripts	 

Or just place it in the config/scripts directory.

If these file were placed in the config/scripts directory of all of your Elasticsearch data nodes, then Elasticsearch will pick up the script within 60 seconds (configurable by changing watcher.interval in your elasticsearch.yml) and pre-compile it for use with future requests. You do need to ensure that the file is readable by the user running Elasticsearch! After writing this to disk, your configuration directory should look something like this:

config/
  elasticsearch.yml
  logging.yml
  scripts/
    population.groovy
    weights.groovy

Your script will not be usable until the script is loaded, at which point you will see something like this in your log file(s):

[2015-02-11 11:14:47,066][INFO ][script                   ] [The Hulk] compiling script file [/path/to/elasticsearch-1.4.3/config/scripts/population.groovy]
[2015-02-11 11:15:47,066][INFO ][script                   ] [The Hulk] compiling script file [/path/to/elasticsearch-1.4.3/config/scripts/weights.groovy]

Once the scripts has been loaded by all of your Elasticsearch data nodes, then you can begin to use it.

ubuntu

Your install should look like this:

/etc/elasticsearch$ ls -lah
total 36K
drwxr-xr-x   2 root root 4.0K Jun  5 16:37 .
drwxr-xr-x 174 root root  12K Aug 10 16:03 ..
-rw-r--r--   1 root root  14K Apr 27 11:22 elasticsearch.yml
-rw-r--r--   1 root root 2.0K Apr 27 11:22 logging.yml
lrwxrwxrwx   1 root root   31 Mar 18 14:17 scripts -> /var/www/pelias/scripts/scripts