jacques-n commented on pull request #3188: URL: https://github.com/apache/iceberg/pull/3188#issuecomment-933941392
To further the point on resolved sql: there is also something weird when working with table references and it not being clear if a reference is absolute or relative. For example, if I create a view when my current schema is `<root>.s1` and the sql for the view is something along the lines of `select * from t1`. Imagine in this situation that initially there is a `<root>.t1` but not a `<root>.s1.t1`. In this case, the view will initially bind to `<root>.t1`. Let's then imagine I create table (or view) called `<root>.s1.t1`. If you apply resolution rules at view consumption times, it will resolve to `<root>.s1.t1` even though that was not the intention. If you had saved the resolved sql at view creation time, it would remain point to `<root>.t1`. What is expected behavior in the case of a Iceberg view? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
