Tal Levy 33b9e2065b no null values in ingest configuration error messages (#20616) ... The invalid ingest configuration field name used to show itself, even when it was null, in error messages. Sometimes this does not make sense. e.g. ```[null] Only one of [file], [id], or [inline] may be configure``` vs. ```Only one of [file], [id], or [inline] may be configure``` The above deals with three fields, therefore this no one property responsible.		2016-09-29 11:34:52 +02:00
..
aggs-matrix-stats	Switch aggregation registration for push to pull	2016-08-16 09:08:36 -04:00
ingest-common	no null values in ingest configuration error messages (#20616)	2016-09-29 11:34:52 +02:00
lang-expression	Upgrade to Lucene 6.2.0	2016-08-24 17:26:28 -04:00
lang-groovy	Fix wrong logger usages	2016-09-21 14:45:28 +02:00
lang-mustache	Add profile and explain parameters to template API	2016-09-19 17:52:13 +02:00
lang-painless	Fix String concatentation bug.	2016-09-21 15:49:56 -07:00
percolator	Remove AnalysisService and reduce it to a simple name to analyzer mapping (#20627)	2016-09-23 08:53:50 +02:00
reindex	Make reindex-from-remote ignore unknown fields	2016-09-26 00:55:46 +02:00
transport-netty3	Remove duplicate methods in ByteSizeValue (#20560)	2016-09-20 14:07:23 +02:00
transport-netty4	Remove duplicate methods in ByteSizeValue (#20560)	2016-09-20 14:07:23 +02:00
build.gradle	Build: Remove old maven deploy support (#20403)	2016-09-19 15:10:41 -07:00