Repository navigation
SQL: fix CLI tests failures due to unconsumed output - #145967
Conversation
wrong management of exceptions with no stack trace
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
|
Hi @luigidellaquila, I've created a changelog YAML for you. |
🔍 Preview links for changed docs⏳ Building and deploying preview... View progress This comment will be updated with preview links when the build is complete. |
ℹ️ Important: Docs version tagging👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version. We use applies_to tags to mark version-specific features and changes. Expand for a quick overviewWhen to use applies_to tags:✅ At the page level to indicate which products/deployments the content applies to (mandatory) What NOT to do:❌ Don't remove or replace information that applies to an older version 🤔 Need help?
|
SQL client always assumed to receive a stack trace for remote failures. This is no longer true with authentication exceptions after the introduction of API key auth.
The result was that the CLI did not consume the output properly.
Fixes: #143645
Fixes: #143646