Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Workbench: error message is not returned properly #586

Open
dai-chen opened this issue Apr 24, 2020 · 5 comments
Open

Workbench: error message is not returned properly #586

dai-chen opened this issue Apr 24, 2020 · 5 comments

Comments

@dai-chen
Copy link
Member

Currently the workbench seems showing "[Index name]: no response" for any error.

@dai-chen
Copy link
Member Author

For example, the SQL plugin throws semantic exception for the unknown field number in index accounts. However, the error message is not returned to customer properly.

SELECT ABS(number) FROM accounts LIMIT 5;

Accounts: no response

@penghuo
Copy link
Contributor

penghuo commented May 4, 2020

+1

Query

SELECT NotExistName, MAX(FlightDelayMin)
FROM kibana_sample_data_flights
GROUP BY DestCityName

Result in sql-kibana is unexpected

Kibana_sample_data_flights
group: no response

Result in devtools is expected

{
  "error": {
    "reason": "Invalid SQL query",
    "details": "Field [NotExistName] cannot be found or used here.",
    "type": "SemanticAnalysisException"
  },
  "status": 400
}

@chloe-zh
Copy link
Member

chloe-zh commented May 4, 2020

Duplicated issue with amazon-archives/sql-workbench#16

@chloe-zh chloe-zh transferred this issue from amazon-archives/sql-workbench Jul 17, 2020
@chloe-zh chloe-zh changed the title Plugin error message is not returned properly Workbench: error message is not returned properly Jul 17, 2020
@matanrabi
Copy link

@dai-chen Was this issue resolved?
I'm getting the same problems while working with kibana SQL work bench

@dai-chen
Copy link
Member Author

@matanrabi Sorry I got it wrong about PR #943. I just confirmed with @chloe-zh. The fix in this PR is only on rc3 branch now. We need to merge this to develop branch.

@dai-chen dai-chen reopened this Jan 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants