Sam Kleinman
Sam Kleinman
This feels similar to: https://github.com/dnschneid/crouton/issues/1514 I'd be willing to forgo the xiwi/crouton integration, but similarly can't really figure out how to rollback.
Interestingly enough, this seems to have the desired behavior (returning results in the correct order), which is really cool. Since we don't have a good way to assert about explain...
> We shouldn't expose a new dsl for datasource specific ordering. All pushdowns need to be handled in the optimizer. So the optimizer, as I'm sure you know, doesn't pass...
So I think the syntax in the table function is probably wrong, but "just write an optimizer plan to solve this generically" is definitely at the very least "making the...
In talking with @greyscaled, it became clear to us that we can drop all of the new configuration except the bucket name from the configuration options, because the access to...
This consistently fails because we can't consistently predict the schema of the results of the query based on the information we have.
When we can get dynamic loading of functions (including having ways of _not_ loading some functions in cloud, this could be an interesting thing to land.)
superseded by #3091 (for security reasons)
Should have followed up on this: - does this still happen? - is there a workaround? - `Schema error` makes me think that somehow the types in delta as we...
@melbourne2991 wanted to check in on this. Is there anything I can do to help you on this?