Oh, I see. This option is available only on system level. I don't see any reason to abandon it for users (not admins) and session level.
@Artem Do you plan to do the change? Have you created the correspondent ticket? Kind regards Vitalii On Wed, Jan 20, 2021 at 8:36 AM Abhishek Girish <[email protected]> wrote: > Hey Vitalii, > > I had requested Artem to use the Dev list as it relates to making changes > to the Drill code. He is a Developer and is planning on making / has made > changes to support updates at session level. > > Regards, > Abhishek > > On Mon, Jan 18, 2021 at 1:23 PM Vitalii Diravka <[email protected]> > wrote: > > > Hi Artem, > > > > You can set both options. But it will be stored in the Persistence Store, > > so the option will be preserved between Drill sessions. > > Please check all info about difference system and session settings > levels: > > https://drill.apache.org/docs/alter-system/ > > > > Also please use user mailing list ([email protected]) for this type > of > > questions: > > https://drill.apache.org/mailinglists/ > > > > > > Kind regards > > Vitalii > > > > > > On Wed, Nov 4, 2020 at 3:14 PM Artem Trush <[email protected]> wrote: > > > > > Hi Drill Devs! > > > I have a question about the "output_batch_size" option. Is it safe to > > > change the scope of this parameter from system to both system and > > > session level? If not, what can happen? > > > The problem arose due to a performance issue in certain queries and > > > changing this option helps. But due to the fact that it is setted at > > > the system level, all executable queries began to absorb more memory > > > and as a result - out of memory issue. So, the solution to the problem > > > is to allow users to change this parameter at the session level to > > > affect only certain queries, without affecting all others at the > > > system. > > > > > >
