You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current CQL parsing before migrating a CQL file only separates statements, tracks line numbers and removes comments.
There are many enhancements that would benefit from generating an AST from a cql file before migrating. The primary benefit would be syntax validation before executing a query. This would reduce the chance of partially migrating a CQL file that would require manual cleanup.
Other potential enhancements include:
formatter and linter features for developer experience
suggest rollback CQL to rollback from an error after partially migrating a CQL file
augmenting statements with an alternate keyspace for test isolation
There's an ANTLR crate that could be used with the cql3.0 grammar on antlr/grammars but it would probably be more fun to code a parser.
The text was updated successfully, but these errors were encountered:
The current CQL parsing before migrating a CQL file only separates statements, tracks line numbers and removes comments.
There are many enhancements that would benefit from generating an AST from a cql file before migrating. The primary benefit would be syntax validation before executing a query. This would reduce the chance of partially migrating a CQL file that would require manual cleanup.
Other potential enhancements include:
There's an ANTLR crate that could be used with the cql3.0 grammar on antlr/grammars but it would probably be more fun to code a parser.
The text was updated successfully, but these errors were encountered: