Greenplum SQL Parser for Java and .NET
General SQL Parser (GSP) parses Greenplum 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, available for Java and .NET.
Greenplum SQL that GSP parses
CREATE TABLE sales (id INT, region TEXT, amt NUMERIC)
DISTRIBUTED BY (id); Need us to check your own Greenplum SQL? Send a sample.
Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvgreenplum);
parser.sqltext = sql; // the Greenplum 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.dbvgreenplum);
parser.sqltext = sql; // the Greenplum 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 Greenplum
- DISTRIBUTED BY clauses
- External tables
- CREATE FUNCTION bodies
- psql slash commands
- SET variables
- Procedural SQL: PL/pgSQL-style function bodies (CREATE FUNCTION) and DECLARE blocks
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Greenplum.
Recent Greenplum parser updates
- 2026-06-09 [PostgreSQL, Greenplum, Redshift] '/' on a line is division
- 2026-03-13 [Greenplum, Snowflake] Fix syntax parsing issues
- 2026-01-11 Delegate GaussDB and Greenplum parsing to VendorParsers
Full history in the release notes.
Greenplum resources
- Greenplum syntax reference — dialect documentation
- Greenplum keyword compatibility — every keyword, and whether it can be an identifier
- Greenplum 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
Does GSP parse Greenplum stored procedures and procedural SQL?
Yes. GSP parses PL/pgSQL-style function bodies (CREATE FUNCTION) and DECLARE 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 Greenplum database connection to validate SQL?
No. GSP validates Greenplum 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 Greenplum grammar?
GSP uses a dedicated hand-tuned grammar for Greenplum — not a generic SQL grammar with flags. The parser recognizes 519 Greenplum keywords and knows which 466 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the Greenplum parser from C# / .NET?
Yes. The .NET edition parses Greenplum 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 Greenplum SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Greenplum scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.