DanielLeens commented on issue #11249: URL: https://github.com/apache/seatunnel/issues/11249#issuecomment-4861292306
Thanks for volunteering to help on this. This still looks like a reasonable enhancement request, but I would keep the first implementation boundary quite tight: support inline JSON scalar extraction in the current SQL transform path, and make the null / missing-path / invalid-JSON behavior explicit in tests. Since @MohamedFazil1406 is already assigned here, I would suggest treating that as the single active owner for the first PR so we do not end up with overlapping implementations. If you would still like to help, coordinating on test coverage, docs, or a follow-up slice would be a good path. For the initial PR, the most important things are: 1. keep the scope limited to the current SQL transform rather than mixing in a broader SQL-engine redesign 2. cover ordinary scalar-expression positions like `SELECT`, `CASE WHEN`, and filters 3. lock down behavior for null input, missing path, and invalid JSON/path with unit tests That should give us a much easier review path than trying to solve every JSON-SQL compatibility case at once. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
