168b448a0f
We've had some discussions around the user experience when using runtime fields. Although we do plan on having multiple runtime fields implementation (e.g. grok, lookup etc.) which could be exposed as different field types, we decided to expose all runtime fields under the same `runtime` type. At the moment, the only implementation will be through scripts, hence a `script` must be specified. In the future, there will be other ways to generate values for runtime fields besides scripts. This translates also to renaming the RuntimeScriptFieldMapper class to RuntimeFieldMapper . Relates to #59332 |
||
|---|---|---|
| .. | ||
| qa | ||
| src | ||
| build.gradle | ||