cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berenguer Blasi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12598) BailErrorStragery alike for ANTLR grammar parsing
Date Fri, 02 Sep 2016 06:51:21 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Berenguer Blasi updated CASSANDRA-12598:
----------------------------------------
    Description: 
CQL parsing is missing a mechanism similar to http://www.antlr.org/api/Java/org/antlr/v4/runtime/BailErrorStrategy.html

This solves:
- Stopping parsing instead of continuing when we've got already an error which is wasteful.
- Any skipped java code tied to 'recovered' missing tokens might later cause java exceptions
(think non-init variables, non incremented integers (div by zero), etc.) which will bubble
up directly and will hide properly formatted error messages to the user with no indication
on what went wrong at all. Just a cryptic NPE i.e

  was:
CQL parsing is missing a mechanism similar to http://www.antlr.org/api/Java/org/antlr/v4/runtime/BailErrorStrategy.html

This solrves:
- Stopping parsing instead of continuing when we've got already an error, which is wasteful
- Any skipped java code tied to 'recovered' missing tokens might later cause java exceptions
(think non-init variables, non incremented integers (div by zero), etc.) which will bubble
up directly and will hide properly formatted error messages to the user with no indication
on what went wrong at all. Just a cryptic NPE i.e


> BailErrorStragery alike for ANTLR grammar parsing
> -------------------------------------------------
>
>                 Key: CASSANDRA-12598
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12598
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Berenguer Blasi
>             Fix For: 3.10
>
>
> CQL parsing is missing a mechanism similar to http://www.antlr.org/api/Java/org/antlr/v4/runtime/BailErrorStrategy.html
> This solves:
> - Stopping parsing instead of continuing when we've got already an error which is wasteful.
> - Any skipped java code tied to 'recovered' missing tokens might later cause java exceptions
(think non-init variables, non incremented integers (div by zero), etc.) which will bubble
up directly and will hide properly formatted error messages to the user with no indication
on what went wrong at all. Just a cryptic NPE i.e



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message