Skip to content
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

[ElasticSearch] Change: use simplejson for better error descriptions #1438

Merged
merged 1 commit into from Dec 6, 2016
Merged

[ElasticSearch] Change: use simplejson for better error descriptions #1438

merged 1 commit into from Dec 6, 2016

Conversation

adamlwgriffiths
Copy link
Contributor

The standard json library only provides an error
that the json failed to parse (“No JSON object could be decoded”).
simplejson provides actual character and line numbers
along with an expected character in it's errors.
This makes writing elasticsearch queries much easier.

I have only applied this to the ElasticSearch query runner.
There are other modules that could use it for error-checking queries (MongoDB, etc).

screen shot 2016-12-01 at 11 41 46 am

The standard json library only provides an error
that the json failed to parse.
simplejson provides actual character and line numbers
along with an expected character in it's errors.
This makes writing elasticsearch queries much easier.
@arikfr arikfr changed the title Use simplejson for better error descriptions. [Elasticsearch] Change: use simplejson for better error descriptions Dec 6, 2016
@arikfr arikfr changed the title [Elasticsearch] Change: use simplejson for better error descriptions [ElasticSearch] Change: use simplejson for better error descriptions Dec 6, 2016
@arikfr arikfr merged commit fcd623e into getredash:master Dec 6, 2016
@arikfr
Copy link
Member

arikfr commented Dec 6, 2016

Thanks.

dairyo pushed a commit to KiiCorp/redash that referenced this pull request Mar 1, 2019
[ElasticSearch] Change: use simplejson for better error descriptions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants