You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@xzdandy What happens if the table already exists? This raised an issue that I did not notice before. I was using if_not_exists in the load executor. In mat executor, we can use handle_if_not_exists because the catalog entry is created in the mat executor. But this is not the case for the load operator, the catalog entry is created before the load executor. I think we shall choose one way for both of them. And update the mat, load design, and this creates (e.g., doc what happens the table exists, remove **kwargs, add a call to check whether a table exists or can we use read to do it?)
The text was updated successfully, but these errors were encountered:
Thanks Gaurav. Noticed in the EXPLAIN PR, #444 (comment) The binder is called. If that's the case, the catalog entry can not be created in the binder. All "permanent" changes need to be done in the executor.
@xzdandy What happens if the table already exists? This raised an issue that I did not notice before. I was using if_not_exists in the load executor. In mat executor, we can use handle_if_not_exists because the catalog entry is created in the mat executor. But this is not the case for the load operator, the catalog entry is created before the load executor. I think we shall choose one way for both of them. And update the mat, load design, and this creates (e.g., doc what happens the table exists, remove **kwargs, add a call to check whether a table exists or can we use read to do it?)
The text was updated successfully, but these errors were encountered: