julianhyde commented on issue #1593: [CALCITE-3513] Unify TableFunction implementor's NullPolicy and its behavior URL: https://github.com/apache/calcite/pull/1593#issuecomment-576458128 This is good discussion, but can if you are changing the specification, can you move any conclusions over to the JIRA case? I think that table functions should behave the same as regular functions with regard to null arguments. IIRC, there are annotations that you can put against a UDF to control whether a null argument means a null result. If so, those annotations should also apply to table functions. I agree with @vlsi that if a table function returns null it should be interpreted in SQL as an empty relation. (Vladimir, did you check what happens if a table function returns null and it is an argument to a consuming table function? I would guess that the consuming table function sees an empty, but not null, argument.)
---------------------------------------------------------------- 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] With regards, Apache Git Services
