Pinging @elastic/es-core-features (:Core/Features/Ingest)

@elasticmachine ok to test

@elasticmachine update branch

@gaobinlong, after running the tests on this one, it appears that one of the new tests (https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+pull-request-bwc/6187/testReport/junit/org.elasticsearch.backwards/MixedClusterClientYamlTestSuiteIT/test__p0_bulk_90_pipeline_One_request_has_pipeline_and_another_not_/) is failing. Could you take a look at that one?

@danhermann, maybe because we have not done the backport, so the new yaml test executes failed when there is a mixed cluster. I'm not clear about how to handle this situation, maybe we can remove the new yaml test and only execute the newly added unit test ?

@gaobinlong, ah, right. I was not paying attention to the fact that it was a backwards compatibility test that failed. If you will add the following lines (including indentation) to the 90_pipeline.yml file right after "One request has pipeline and another not":

  - skip:
      version: " - 7.99.99"
      reason: "change after backporting"

That will skip the mixed cluster tests for now and then after I backport the change for earlier releases, I'll change that so that the mixed cluster tests include that for the appropriate releases.

@danhermann, I have done that, and all checks have passed yet.

@gaobinlong, great, thank you! I'll get this merged and backported.

@danhermann I think we can remove backport pending now. Right?

Finished the last backport to 7.x and removed "backport pending" label.