-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Add metadata to configuration exceptions #27728
Copy link
Copy link
Closed
Labels
:Distributed/Ingest NodeExecution or management of Ingest PipelinesExecution or management of Ingest Pipelines>enhancementhelp wantedadoptmeadoptme
Description
... instead of using headers.
Similarly to #27724, there is some exception metadata that is included in headers rather than using addMetadata(), introduced in #19318.
elasticsearch/core/src/main/java/org/elasticsearch/ingest/ConfigurationUtils.java
Lines 346 to 354 in 2e36f19
| if (processorType != null) { | |
| exception.addHeader("processor_type", processorType); | |
| } | |
| if (processorTag != null) { | |
| exception.addHeader("processor_tag", processorTag); | |
| } | |
| if (propertyName != null) { | |
| exception.addHeader("property_name", propertyName); | |
| } |
Under the umbrella of #27672, it'd be preferable to use addMetadata() to reduce the number of ways that clients have to handle errors.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Distributed/Ingest NodeExecution or management of Ingest PipelinesExecution or management of Ingest Pipelines>enhancementhelp wantedadoptmeadoptme
Type
Fields
Give feedbackNo fields configured for issues without a type.