You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GET /_data_frame/transforms/a_transform_that_doesn't_exist
Does not return a 404 instead an empty response is returned. More dubiously the log is filled with many error messages
[2019-03-13T16:23:01,545][ERROR][o.e.t.TransportService ] [node-0] failed to handle exception for action [indices:data/read/get[s]], handler [org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler/org.elasticsearch.action.support.single.shard.TransportSingleShardAction$AsyncSingleAction$2@72a4f821]
java.lang.RuntimeException: Failed to load data frame transform configuration for transform [test-get]
[2019-03-13T16:23:01,545][WARN ][o.e.x.c.s.SchedulerEngine] [node-0] listener failed while handling triggered event [data_frame/transforms/schedule_test-get]
java.lang.NullPointerException: null
at org.elasticsearch.xpack.dataframe.transforms.DataFrameTransformTask$ClientDataFrameIndexer.maybeTriggerAsyncJob(DataFrameTransformTask.java:272) ~[?:?]
at org.elasticsearch.xpack.dataframe.transforms.DataFrameTransformTask.triggered(DataFrameTransformTask.java:189) ~[?:?]
Caused by: java.lang.RuntimeException: Failed to load data frame transform configuration for transform [test-get]
And finally after thousands of lines the cause
Caused by: org.elasticsearch.ResourceNotFoundException: Transform with id [test-get] could not be found
at org.elasticsearch.xpack.dataframe.persistence.DataFrameTransformsConfigManager.lambda$getTransformConfiguration$3(DataFrameTransformsConfigManager.java:106) ~[?:?]
The text was updated successfully, but these errors were encountered:
GET /_data_frame/transforms/a_transform_that_doesn't_exist
Does not return a 404 instead an empty response is returned. More dubiously the log is filled with many error messages
And finally after thousands of lines the cause
The text was updated successfully, but these errors were encountered: