Test docs for plugins

We weren't doing it before because we weren't starting the plugins.
Now we are.

The hardest part of this was handling the files the tests expect
to be on the filesystem. extraConfigFiles was broken.
This commit is contained in:
Nik Everett 2016-05-13 16:15:51 -04:00
parent 399d023715
commit 9c85569883
15 changed files with 130 additions and 83 deletions

View file

@ -53,8 +53,6 @@ you can use JavaScript as follows:
[source,js]
----
DELETE test
PUT test/doc/1
{
"num": 1.0
@ -96,8 +94,6 @@ you can use JavaScript as follows:
[source,js]
----
DELETE test
PUT test/doc/1
{
"num": 1.0
@ -129,7 +125,6 @@ GET test/_search
}
}
}
----
// CONSOLE
@ -145,7 +140,7 @@ You can save your scripts to a file in the `config/scripts/` directory on
every node. The `.javascript` file suffix identifies the script as containing
JavaScript:
First, save this file as `config/scripts/my_script.javascript` on every node
First, save this file as `config/scripts/my_script.js` on every node
in the cluster:
[source,js]
@ -157,8 +152,6 @@ then use the script as follows:
[source,js]
----
DELETE test
PUT test/doc/1
{
"num": 1.0
@ -185,9 +178,7 @@ GET test/_search
}
}
}
----
// CONSOLE
<1> The function score query retrieves the script with filename `my_script.javascript`.