"SET" is very cheap - it only affects the client session on the Impala server that you're connected to. DDL operations are often more expensive because they require updating metadata globally. That can sometimes involve a bit of work (e.g. gather metadata about existing files on HDFS) or can involve the operation getting queued behind other metadata operations.
On Sun, May 20, 2018 at 4:09 AM, Fawze Abujaber <fawz...@gmail.com> wrote: > Hi Community, > > Does the DDL operations like alter, drop and create consume resources? and > does the set operations like set resource_pool=xxx also consume resources? > > Yes, i'm aware these operations are quick but once they are running from > interfaces like Hue or MSTR through ODBC it's running till it get timeout > .... which may exceed few minutes > > -- > Take Care > Fawze Abujaber >
