SQL dialect
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, 38 dialects, Java and .NET.
Example
Greenplum SQL that GSP parses
CREATE TABLE sales (id INT, region TEXT, amt NUMERIC)
DISTRIBUTED BY (id);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());
}The .NET edition exposes the same API in C# — see the C# quick start.
Coverage
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.
Actively maintained
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.
Go deeper
Greenplum resources
- Greenplum syntax reference — dialect documentation
- Greenplum keyword compatibility — every keyword, and whether it can be an identifier
- Java quick start — Maven/Gradle setup and first parse
- C# quick start — NuGet setup for .NET
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 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 (NuGet package gudusoft.gsqlparser, .NET Standard 2.0) exposes the same API surface as the Java edition, so every Greenplum parsing feature on this page works in C# and VB.NET.
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.