Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ML] Update Delete Inference Endpoint for dry_run and force options #2602

Merged
merged 6 commits into from
Jun 6, 2024

Conversation

maxhniebergall
Copy link
Contributor

Following on elastic/elasticsearch#109123 and elastic/elasticsearch#109384, this change updates the elasticsearch specification to include the dry_run and force options for the Delete Inference Endpoint API.

Copy link
Contributor

github-actions bot commented Jun 5, 2024

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.delete Missing test Missing test
inference.get 🔴 3/4 3/4
inference.inference Missing test Missing test
inference.put Missing test Missing test

You can validate these APIs yourself by using the make validate target.

Copy link
Contributor

github-actions bot commented Jun 5, 2024

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.delete Missing test Missing test
inference.get 🔴 3/4 3/4
inference.inference Missing test Missing test
inference.put Missing test Missing test

You can validate these APIs yourself by using the make validate target.

@maxhniebergall maxhniebergall requested a review from davidkyle June 5, 2024 17:22
Co-authored-by: David Kyle <[email protected]>
Copy link
Contributor

github-actions bot commented Jun 5, 2024

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.delete Missing test Missing test
inference.get 🔴 3/4 3/4
inference.inference Missing test Missing test
inference.put Missing test Missing test

You can validate these APIs yourself by using the make validate target.

Copy link
Contributor

github-actions bot commented Jun 6, 2024

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.delete Missing test Missing test
inference.get 🔴 3/4 3/4
inference.inference Missing test Missing test
inference.put Missing test Missing test

You can validate these APIs yourself by using the make validate target.

Copy link
Contributor

github-actions bot commented Jun 6, 2024

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.delete Missing test Missing test
inference.get 🔴 3/4 3/4
inference.inference Missing test Missing test
inference.put Missing test Missing test

You can validate these APIs yourself by using the make validate target.


export class Response {
body: AcknowledgedResponseBase
body: {
dryRunResult: DeleteInferenceEndpointResult
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does dryRunResult mean here? Should it be body: DeleteInferenceEndpointResult ?

* Acknowledged response. For dry_run, contains the list of ingest processors which reference the inference endpoint
*/
export class DeleteInferenceEndpointResult extends AcknowledgedResponseBase {
ingest_processors: Array<string>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the field is pipelines right? That's what I'm seeing in the response:

{
    "acknowledged": false,
    "pipelines": [
        "elser"
    ]
}


export class Response {
body: AcknowledgedResponseBase
body: {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm I think this should be:

export class Response {
  body: DeleteInferenceEndpointResult
}

I don't believe there's a dryRunResult field in the response.

@maxhniebergall
Copy link
Contributor Author

Clearly I don't fully understand what the correspondence between the java code and the specification is. I'm going to do some reading and come back to this.

Copy link
Contributor

github-actions bot commented Jun 6, 2024

Following you can find the validation results for the APIs you have changed.

API Status Request Response
inference.delete Missing test Missing test
inference.get 🔴 3/4 3/4
inference.inference Missing test Missing test
inference.put Missing test Missing test

You can validate these APIs yourself by using the make validate target.

@maxhniebergall maxhniebergall merged commit 27a75c7 into main Jun 6, 2024
6 checks passed
@maxhniebergall maxhniebergall deleted the updateDeleteInferenceEndpoint branch June 6, 2024 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants