-
Notifications
You must be signed in to change notification settings - Fork 138
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
Match query is not working in sql dev tools while its working in query workbench in opensearch #782
Comments
@Shivacharangoud Thanks for reporting the issue! Could you provide more details? Such as your test index, OpenSearch version etc. |
version:OpenSearch 1.2 |
Could you share the index mapping and some test data? Error stacktrace would be also helpful. Thanks! |
mappings:
available data in index:
|
i have an question which is not related to this issues. |
@dai-chen Removed the old version label from this issue. Please re-tag this issue with appropriate version. |
Will do. Thanks! |
@Shivacharangoud We've added more complete support for full text search functions including |
@dai-chen this seems to be broken when using JSON format type with match. CSV and standard responses work fine. running query: getting When tweaking to match MySQL standard with expected
I am getting
Any ideas? |
@EfChouTR From what you posted, the query was fallback to our legacy code. Just to confirm you ran each query with @acarbonetto Can someone help take a look? I forgot if we support relevancy search function with JSON format in v2 engine. Thanks! |
Correct. It will be helpful to know this ahead of time in the documentation, so we know what's supported and what isn't in each format type. |
SELECT * FROM contacts WHERE match(name, 'charan') ;
The above query is working in query workbench
But if I use the same query in dev tools. Using plugin not working
Example :
POST _plugins/_sql
{
"query":"SELECT * FROM contacts WHERE match(name, 'charan') ;"
}
The above one not working.
Can any help me out with this?
The text was updated successfully, but these errors were encountered: