Heli Wang

That is accurate. We don't have a use case for MS SQL at Uber, but it is certainly within the scope of this project to expand our supported dialects. And...

@etrabelsi As a general high-level approach, start with copying one of the dialect parsers similar to Redshift/Spark SQL, and modifying the language features as the respective SQL documentation says. The...

Hey there! Thanks for giving this a whirl! Right now, we don't have a python wrapper available, but it's certainly a tooling we want. In the meantime, have you looked...

Hey @tuulos , Yes, we intend to support resolving aliases in column access, we have table alias resolution but it looks like this particular case slipped under the radar. This...

I believe if you want to develop queryparser, you will need to use stack. However, if you want to just use queryparser in a Haskell environment, there are [packages on...

re: #54 we'll want to support dialect versions for all our dialects, since everything changes eventually =)

Thanks for looking into this. I've been away from this project for a while, but I can certainly help get a PR in. It sounds like the PR would be...

This is already captured in parsing, just needs to add to the usage analysis.

Hello, Queryparser supports Hive lateral view query, and has simple support for UDF functions. Lateral view query is defined here: https://github.com/uber/queryparser/blob/master/src/Database/Sql/Type/Query.hs#L158 Queryparser currently supports parsing function names, but doesn't have...

Column lineage, if i remember correctly, isn't currently implemented, and all the original authors (myself included) are not active on this project. However, if you're interested in contributing, I can...