1.5 KiB
| layout | title | parent | nav_order | redirect_from | |
|---|---|---|---|---|---|
| default | Troubleshooting | SQL and PPL | 88 |
|
Troubleshooting
The SQL plugin is stateless, so troubleshooting is mostly focused on why a particular query fails.
The most common error is the dreaded null pointer exception, which can occur during parsing errors or when using the wrong HTTP method (POST vs. GET and vice versa). The POST method and HTTP request body offer the most consistent results:
POST _plugins/_sql
{
"query": "SELECT * FROM my-index WHERE ['name.firstname']='saanvi' LIMIT 5"
}
If a query isn't behaving the way you expect, use the _explain API to see the translated query, which you can then troubleshoot. For most operations, _explain returns OpenSearch query DSL. For UNION, MINUS, and JOIN, it returns something more akin to a SQL execution plan.
Example request
POST _plugins/_sql/_explain
{
"query": "SELECT * FROM my-index LIMIT 50"
}
Example response
{
"from": 0,
"size": 50
}
Index mapping verification exception
If you see the following verification exception, make sure the index in your query isn't an index pattern and doesn't have multiple types:
{
"error": {
"reason": "There was internal problem at backend",
"details": "When using multiple indices, the mappings must be identical.",
"type": "VerificationException"
},
"status": 503
}
If these steps don't work, submit a Github issue here.