sql: Fix Seg Faults when parsing complex queries

[kchledowski]

Problem

SQL Parser is not able to parse some of the queries, mainly more complex ones. Apparently it runs out of stack memory.

Given a troublesome SQL query:

• With 1 MB stack size (default on Linux x64) the parsing fails with 139 error code.
• With 2 MB stack size (default on macOS ARM64) the parsing is successful.

Closes: #3973

Solution

OpenLineage is currently using sqlparser (https://docs.rs/sqlparser) v0.50.0 from a custom fork.
Testing showed that starting with v0.52.0, the issue is gone.
The solution is to migrate to the latest version of sqlparser, which is v0.59.0

One-line summary:

sql: Fix Seg Faults when parsing complex queries

Checklist

• You've signed-off your work
• Your pull request title follows our guidelines
• Your changes are accompanied by tests (if relevant)
• Your change contains a small diff and is self-contained
• You've updated any relevant documentation (if relevant)
• Your comment includes a one-liner for the changelog about the specific purpose of the change (not required for changes to tests, docs, or CI config)
• You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
• You've added a header to source files (if relevant)

---

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2025 contributors to the OpenLineage project

[JDarDagran]

Would it be possible to add some more complex example in tests that fails now and is fixed with this PR?

[kchledowski]

Would it be possible to add some more complex example in tests that fails now and is fixed with this PR?

To make such test reliable, it would have to be forced to run with 1 MB stack size somehow. I guess it should be possible to spawn a new thread with 1 MB stack size and run a test in it, I'll look into it

[mobuchowski]

IDK if it's worth spending time doing that. Bump of dependency is good enough reason for me to merge that :)

[JDarDagran]

That's totally fine. I was rather asking for it hoping it's a small task to do.