Set system property for tests and update painless-getting-started

Author: mayya-sharipova

docs/painless/painless-getting-started.asciidoc

@@ -140,15 +140,6 @@ set a <<jvm-options,`jvm.option`>>
 `-Des.script.null_for_missing_value=true` on a node. If you do not enable
 this behavior, a deprecation warning is logged on start up.
 
-===== Multiple values
-
-Painless supports the following operations for multi-value numeric fields:
-
-- `doc['field'].min` - gets the minimum value
-- `doc['field'].max` - gets the maximum value
-- `doc['field'].sum` - gets the sum of the values
-- `doc['field'].avg` - gets the average of the values
-
 
 [float]
 ==== Updating Fields with Painless
@@ -388,6 +379,16 @@ Note: all of the `_update_by_query` examples above could really do with a
 as using any other query because script queries aren't able to use the inverted
 index to limit the documents that they have to check.
 
+[[multi-value-field-operations]]
+=== Multi-value field operations
+
+Painless supports the following operations for multi-value numeric fields:
+
+- `doc['field'].min` - gets the minimum value
+- `doc['field'].max` - gets the maximum value
+- `doc['field'].sum` - gets the sum of the values
+- `doc['field'].avg` - gets the average of the values
+
 [[modules-scripting-painless-dispatch]]
 === How painless dispatches functions
 

modules/parent-join/build.gradle

@@ -22,3 +22,6 @@ esplugin {
   classname 'org.elasticsearch.join.ParentJoinPlugin'
   hasClientJar = true
 }
+test.configure {
+  systemProperty 'es.script.null_for_missing_value', 'true'
+}

modules/percolator/build.gradle

@@ -36,3 +36,7 @@ dependencyLicenses {
 
 compileJava.options.compilerArgs << "-Xlint:-deprecation,-rawtypes"
 compileTestJava.options.compilerArgs << "-Xlint:-deprecation,-rawtypes"
+
+test.configure {
+    systemProperty 'es.script.null_for_missing_value', 'true'
+}

server/build.gradle

@@ -338,3 +338,7 @@ if (isEclipse == false || project.path == ":server-tests") {
   check.dependsOn integTest
   integTest.mustRunAfter test
 }
+
+test.configure {
+    systemProperty 'es.script.null_for_missing_value', 'true'
+}

x-pack/plugin/security/build.gradle

@@ -225,6 +225,7 @@ test {
      * other if we allow them to set the number of available processors as it's set-once in Netty.
      */
     systemProperty 'es.set.netty.runtime.available.processors', 'false'
+    systemProperty 'es.script.null_for_missing_value', 'true'
 }
 
 // xpack modules are installed in real clusters as the meta plugin, so