Currently, only the application_id parameter of the configuration file can be read when starting the sqlgateway server, which causes all users to use the same yarn-session, which causes a single application_id to carry too many jobs, and it is inconvenient to distinguish and manage different users. between jobs.I have already implemented this part of the function, I don't know when the community will discuss it sometimes
Currently, only the application_id parameter of the configuration file can be read when starting the sqlgateway server, which causes all users to use the same yarn-session, which causes a single application_id to carry too many jobs, and it is inconvenient to distinguish and manage different users. between jobs.I have already implemented this part of the function, I don't know when the community will discuss it sometimes