1. Get the trial package
Request the GSP Java 4.1.x evaluation JAR and example project.
Run examples locally/offline inside your evaluation environment.GSP Java SDK
Java SQL Parser SDK for AST, validation, and lineage
GSP is a commercial Java SQL parser and semantic analysis SDK for teams that need reliable parsing, table and column extraction, validation, and lineage across complex enterprise SQL dialects.
Short Answer
Use GSP when your Java application needs more than syntax parsing: stable AST APIs, dialect-aware analysis, table and column extraction, SQL validation signals, and lineage output that can run locally in an enterprise environment.
Key takeaways
30+ SQL dialectsOracle, SQL Server, PostgreSQL, MySQL, DB2, Teradata, Snowflake, BigQuery, Spark SQL, and more.
Semantic outputsAST, tables, columns, aliases, validation errors, and lineage-oriented signals.
Enterprise deploymentDesigned for offline/private evaluation and commercial support workflows.
3-minute quick start
Evaluate GSP Java 4.1.x locally
For commercial evaluation, Gudu provides a current 4.1.x trial JAR and Java example project. If you cannot use a public package repository, request the trial package and run the examples locally.
2. Parse one SQL statement
String sql = "select c.customer_id, sum(o.amount) total " +
"from customers c join orders o on c.id = o.customer_id " +
"group by c.customer_id";
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvoracle);
parser.sqltext = sql;
int result = parser.parse();3. Handle parser errors clearly
if (result != 0) {
System.out.println(parser.getErrormessage());
return;
}4. Inspect AST, tables, columns, and lineage
for (int i = 0; i < parser.sqlstatements.size(); i++) {
TCustomSqlStatement stmt = parser.sqlstatements.get(i);
System.out.println(stmt.sqlstatementtype);
System.out.println(stmt.tables);
System.out.println(stmt.getResultColumnList());
}Example outputs
What your Java product can build on
ASTStatement type, clauses, expressions, joins, predicates, functions, and nested query structure.
Tables and columnsSource tables, result columns, aliases, scopes, and references for downstream tooling.
ValidationParser and semantic error signals for invalid SQL, unsupported syntax, or catalog-aware checks.
LineageTable and column dependency signals for impact analysis and governance workflows.
Trial path
Start with your own SQL, not a perfect demo
If you already have a corpus, stored procedures, migration scripts, or AI-generated queries, send a representative sample first. Gudu can recommend the right API path and evaluation setup.