Apache Impala SQL Parser for Java and .NET
General SQL Parser (GSP) parses Apache Impala with a dedicated, hand-tuned grammar — full AST access, offline syntax validation, formatting, rewriting, and column-level data lineage. One commercial SDK, available for Java and .NET.
Apache Impala SQL that GSP parses
ALTER TABLE sales_data ADD PARTITION (year=2026, month=7); Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvimpala);
parser.sqltext = sql; // the Apache Impala SQL above
if (parser.parse() == 0) {
System.out.println(parser.sqlstatements.size() + " statement(s) parsed");
} else {
System.out.println(parser.getErrormessage());
} Parse it in C#
using gudusoft.gsqlparser;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvimpala);
parser.sqltext = sql; // the Apache Impala SQL above
if (parser.parse() == 0)
{
Console.WriteLine(parser.sqlstatements.size() + " statement(s) parsed");
}
else
{
Console.WriteLine(parser.Errormessage);
} Same grammar, .NET-idiomatic API — properties instead of Java getters. See the C# quick start or the .NET SQL Parser SDK.
What GSP handles in Apache Impala
- COMPUTE STATS
- PRIMARY/FOREIGN KEY in CREATE TABLE
- DROP TABLE ... PURGE
- External tables
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Apache Impala.
Recent Apache Impala parser updates
- 2026-06-02 [Impala] Parse PRIMARY KEY / FOREIGN KEY in CREATE TABLE
- 2026-06-02 [Impala] Attach ON condition to LEFT [OUTER] JOIN
- 2026-02-20 [Impala] Add PURGE keyword support for DROP TABLE
Full history in the release notes.
Apache Impala resources
- Apache Impala syntax reference — dialect documentation
- Apache Impala keyword compatibility — every keyword, and whether it can be an identifier
- Apache Impala capability data (JSON) — measured construct-by-construct parse coverage, machine-readable
- Java quick start — Maven/Gradle setup and first parse
- C# quick start — .NET setup and first parse
Common questions
Do I need a live Apache Impala database connection to validate SQL?
No. GSP validates Apache Impala syntax completely offline. You get error line and column positions, the offending token, and a hint — with no server, driver, or credentials involved.
How complete is the Apache Impala grammar?
GSP uses a dedicated hand-tuned grammar for Apache Impala — not a generic SQL grammar with flags. The parser recognizes 264 Apache Impala keywords and knows which 262 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the Apache Impala parser from C# / .NET?
Yes. The .NET edition parses Apache Impala with the same grammar, and the API is idiomatic .NET rather than a Java transliteration: where Java has parser.getErrormessage() and stmt.getResultColumnList(), C# has parser.Errormessage and stmt.ResultColumnList. The package id is gudusoft.gsqlparser, multi-targeting net10.0 and netstandard2.0, so .NET Framework 4.6.2+ hosts are covered too.
Can GSP extract column-level lineage from Apache Impala SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Apache Impala scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.