Google BigQuery SQL Parser for Java
General SQL Parser (GSP) parses Google BigQuery with a dedicated, hand-tuned grammar — full AST access, offline syntax validation, formatting, rewriting, and column-level data lineage, including complete procedural SQL support. One commercial SDK — Google BigQuery is available in the Java edition.
Google BigQuery SQL that GSP parses
SELECT name, item.sku, SUM(item.qty) AS qty
FROM `proj.dataset.orders`,
UNNEST(items) AS item
GROUP BY name, item.sku;Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvbigquery);
parser.sqltext = sql; // the Google BigQuery SQL above
if (parser.parse() == 0) {
System.out.println(parser.sqlstatements.size() + " statement(s) parsed");
} else {
System.out.println(parser.getErrormessage());
}Java edition only. The .NET library has no Google BigQuery grammar, so this dialect cannot be parsed from C# or VB.NET. See the .NET SQL Parser SDK for the dialects it does cover.
What GSP handles in Google BigQuery
- UNNEST of arrays
- STRUCT and ARRAY access
- EXPORT DATA
- CREATE MODEL (BigQuery ML)
- MERGE WHEN NOT MATCHED BY SOURCE
- Procedural SQL: BigQuery scripting: CREATE PROCEDURE, DECLARE variables, and BEGIN...EXCEPTION blocks
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Google BigQuery.
Recent Google BigQuery parser updates
- 2026-06-05 [BigQuery] Fix bitwise shift vs AND precedence
- 2026-05-25 [BigQuery] Fix UNNEST CTE star lineage crash
- 2026-05-17 [MSSQL, BigQuery] MERGE WHEN NOT MATCHED BY SOURCE
Full history in the release notes.
Google BigQuery resources
- Google BigQuery syntax reference — dialect documentation
- Google BigQuery keyword compatibility — every keyword, and whether it can be an identifier
- Google BigQuery capability data (JSON) — measured construct-by-construct parse coverage, machine-readable
- Java quick start — Maven/Gradle setup and first parse
Common questions
Does GSP parse Google BigQuery stored procedures and procedural SQL?
Yes. GSP parses BigQuery scripting: CREATE PROCEDURE, DECLARE variables, and BEGIN...EXCEPTION blocks into a full AST — procedure bodies become real statement trees you can traverse, not opaque text blocks. This is what makes lineage and impact analysis work inside procedural code.
Do I need a live Google BigQuery database connection to validate SQL?
No. GSP validates Google BigQuery 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 Google BigQuery grammar?
GSP uses a dedicated hand-tuned grammar for Google BigQuery — not a generic SQL grammar with flags. The parser recognizes 271 Google BigQuery keywords and knows which 269 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the Google BigQuery parser from C# / .NET?
Not currently. Google BigQuery is a Java-edition dialect — the .NET library ships 15 dedicated grammars and Google BigQuery is not one of them, so there is no C# code path for it. Everything else on this page describes the Java SDK. If you need Google BigQuery in .NET, email info@sqlparser.com; customer demand is how dialects get prioritized for the .NET port.
Can GSP extract column-level lineage from Google BigQuery SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Google BigQuery scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.