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

[BUG] Default model id not working for nested field #738

Closed
yuye-aws opened this issue May 8, 2024 · 2 comments
Closed

[BUG] Default model id not working for nested field #738

yuye-aws opened this issue May 8, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@yuye-aws
Copy link
Member

yuye-aws commented May 8, 2024

What is the bug?

Here is the discussion from the forum: https://forum.opensearch.org/t/set-up-default-model-id-for-neural-query-enricher-with-nested-knn-field/19217

How can one reproduce the bug?

Follow steps in: https://forum.opensearch.org/t/set-up-default-model-id-for-neural-query-enricher-with-nested-knn-field/19217

What is the expected behavior?

We need to support default model id for nested field.

What is your host/environment?

Operating system, version.

Do you have any screenshots?

If applicable, add screenshots to help explain your problem.

Do you have any additional context?

Add any other context about the problem.

@yuye-aws yuye-aws added bug Something isn't working untriaged labels May 8, 2024
@dblock
Copy link
Member

dblock commented Jun 24, 2024

Catch All Triage - 1 2 3 4 5 6

@dblock dblock removed the untriaged label Jun 24, 2024
@vibrantvarun
Copy link
Member

duplicate issue with #813. As 813 is fixed, we can mark this as closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants