You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Field type mismatch: The field "my_field" is defined as "text" in the index, but a numerical type was used in the query.
Related component
Cluster Manager
To Reproduce
Create index: Use the API or management interface provided by opensearch to create a new index and define the field "my_field" as "text" type.
Import data: Import the data into the index, ensuring that the "my_field" field in the data contains a mixture of text and numerical values.
Execute Query: Attempt to execute query conditions on an index that contain numerical types, such as using range queries or numerical comparison operators.
Expected behavior
Problem of mismatched identification field types
Additional Details
none
The text was updated successfully, but these errors were encountered:
[Triage - attendees 12] @CCTV-six Thanks for creating this issue; however, it isn't being accepted due to not enough detail around the index configuration- such as the index mapping - without these details it is hard to know if this should be addressed or not. Please feel free to re-open after addressing the reason.
Describe the bug
Field type mismatch: The field "my_field" is defined as "text" in the index, but a numerical type was used in the query.
Related component
Cluster Manager
To Reproduce
Create index: Use the API or management interface provided by opensearch to create a new index and define the field "my_field" as "text" type.
Import data: Import the data into the index, ensuring that the "my_field" field in the data contains a mixture of text and numerical values.
Execute Query: Attempt to execute query conditions on an index that contain numerical types, such as using range queries or numerical comparison operators.
Expected behavior
Problem of mismatched identification field types
Additional Details
none
The text was updated successfully, but these errors were encountered: