RussellSpitzer opened a new issue #1855:
URL: https://github.com/apache/iceberg/issues/1855
Since we delegate back to the Spark parser on parsing errors, any errors on
our extended methods will error out stating the command doesn't exist.
For example
```
== SQL ==
CALL m spark_catalog.system.migrate('default.table', ('foo' = 'bar'))
^^^
org.apache.spark.sql.catalyst.parser.ParseException:
mismatched input 'CALL' expecting {'(', 'ADD', 'ALTER', 'ANALYZE', 'CACHE',
'CLEAR', 'COMMENT', 'COMMIT', 'CREATE', 'DELETE', 'DESC', 'DESCRIBE', 'DFS',
'DROP', 'EXPLAIN', 'EXPORT', 'FROM', 'GRANT', 'IMPORT', 'INSERT', 'LIST',
'LOAD', 'LOCK', 'MAP', 'MERGE', 'MSCK', 'REDUCE', 'REFRESH', 'REPLACE',
'RESET', 'REVOKE', 'ROLLBACK', 'SELECT', 'SET', 'SHOW', 'START', 'TABLE',
'TRUNCATE', 'UNCACHE', 'UNLOCK', 'UPDATE', 'USE', 'VALUES', 'WITH'}(line 1, pos
0)
== SQL ==
CALL m spark_catalog.system.migrate('default.table', ('foo' = 'bar'))
^^^
```
When we should instead be reporting the parse specific error if we correctly
parse the beginning. In the above example either the typo "m" or the
"spark_catalog" since call doesn't have two things following it.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
