Colin Goodheart-Smithe eab5ceb9de Makes `m` case sensitive in TimeValue ... The reason for this change is that currently if a user specifies e.g.`2M` meaning 2 months as a time value instead of throwing an exception explaining that time units in months are not supported (due to months having variable time spans) we instead will parse this to 2 minutes. This could be surprising to a user and could mean put a lot of load on the cluster performing a task that was never intended and whose results will be useless anyway. It is generally accepted that `m` indicates minutes and `M` indicates months with time values so this is consistent with the expectations a user might have around specifying time units. A concrete example of where this causes issues is in the decay score function which uses TimeValue to parse the scale and offset parameters of the decay into millisecond values to use in the calculation. Relates to #19619		2016-07-28 11:27:24 +01:00
..
src	Makes `m` case sensitive in TimeValue	2016-07-28 11:27:24 +01:00
build.gradle	Move netty transport and http into a module	2016-07-11 22:21:29 +02:00