Changes Analysis

Commit SHA: d35604b
Comparing To SHA: d8e4583

API Changes

Summary

└─┬Paths
  ├─┬/_plugins/_ml/_train/{algorithm_name}
  │ └─┬POST
  │   └─┬Extensions
  │     └──[➕] x-version-added (4679:24)
  ├─┬/_plugins/_ml/_predict/{algorithm_name}/{model_id}
  │ └─┬POST
  │   └─┬Extensions
  │     └──[➕] x-version-added (4642:24)
  └─┬/_plugins/_ml/_train_predict/{algorithm_name}
    └─┬POST
      └─┬Extensions
        └──[➕] x-version-added (4661:24)

• Total Changes: 3
• Additions: 3

Report

The full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/12893382825/artifacts/2463396033

API Coverage

Hello!
I quickly checked few versions, at least it should be > 2.1
Maybe I'm wrong somewhere
But I think just in case it's necessary to add tests of other versions specifically for ML

Hello! I quickly checked few versions, at least it should be > 2.1 Maybe I'm wrong somewhere But I think just in case it's necessary to add tests of other versions specifically for ML

I tried to set up a 1.3 OpenSearch cluster and run the test, and it seems that the tests for train, predict, train and predict APIs passed.

Hello! I quickly checked few versions, at least it should be > 2.1 Maybe I'm wrong somewhere But I think just in case it's necessary to add tests of other versions specifically for ML

I tried to set up a 1.3 OpenSearch cluster and run the test, and it seems that the tests for train, predict, train and predict APIs passed.

Great, I apologize for my excessive OCD. I was also trying OS 1.3 with Docker Compose, which we have in the ML folder, and it wouldn't start on these versions, so I thought there might be an error here. Most likely, in the future, if we introduce 1.3 and test on them, we will have to redo the Docker Compose we have there now

Great, I apologize for my excessive OCD. I was also trying OS 1.3 with Docker Compose, which we have in the ML folder, and it wouldn't start on these versions, so I thought there might be an error here. Most likely, in the future, if we introduce 1.3 and test on them, we will have to redo the Docker Compose we have there now

No problem at all! I I referenced the Docker Compose from here, which potentially more accurate :)

Spec Test Coverage Analysis