RussellSpitzer commented on PR #11480: URL: https://github.com/apache/iceberg/pull/11480#issuecomment-2469050720
> Spark allows users to configure multiple extensions and each extension is allowed to inject its own SQL parser, there is a chance that the user configures multiple extensions that support `CALL` syntax, ideally, each extension should only intercept its supported procedure and leave others to the `delegate`. > > Currently, all Iceberg builtin procedures are under `system` namespace, which is guard by > > https://github.com/apache/iceberg/blob/81b3310ab469408022cc14af51257b7e8b36614f/spark/v3.5/spark/src/main/java/org/apache/iceberg/spark/BaseCatalog.java#L51 > > so I propose to add a simple rule to check the SQL before parsing Do we have an example of someone else using the CALL syntax? Just wondering since we invented it for Iceberg specifically. I think this is fine either way, just a little disappointing we are losing a good error message for a bad one. -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
