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] Opensearch 2.3 400 Bad Request: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type] #5516

Closed
ahmednassar opened this issue Dec 11, 2022 · 3 comments
Labels
bug Something isn't working untriaged

Comments

@ahmednassar
Copy link

Describe the bug
I'm getting the below error with AWS opensearch_2.3, I tried to follow the fix in BUG but it does not work.

I confirmed the override_main_response_version as shown below,

aws opensearch describe-domain-config --domain-name opensearch-domain-1|grep override_main_response_version
                "override_main_response_version": "true",

@ahmednassar ahmednassar added bug Something isn't working untriaged labels Dec 11, 2022
@dblock
Copy link
Member

dblock commented Dec 12, 2022

The type parameter has been removed in OpenSearch 2.0. See https://opensearch.org/docs/2.0/breaking-changes/ and #1940. I'll close this issue, but happy to help if you're still stuck -
what are you using to write data (it needs to be compatible with OpenSearch 2.x)?

@dblock dblock closed this as completed Dec 12, 2022
@lehmat
Copy link

lehmat commented Dec 14, 2022

Hi @dblock

I encountered the same error while following AWS guide to send cloudwatch logs to opensearch (on different account with VPC peering) HERE

It seems the "default" lambda that you delpoy directly from cloudwatch subscription filter (UI generated) holds the _type which breaks it:

image

I can confirm that removing the line in the image (or commenting it) fixes the issue

@dblock
Copy link
Member

dblock commented Dec 15, 2022

Thank @lehmat, I'll try to track this down. If you haven't opened a customer support ticket with AWS you should. They have a path to track all this stuff too.

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

No branches or pull requests

3 participants