pvary

Thanks for the detailed answer @flyrain! This really helps to have a clear understanding of the tasks at hand. I would like to share my thoughts about 2 points: >...

Thanks @jackye1995 for highlighting the properties which we need to handle! I have not know about the `write.object-storage.path` before. Do I understand correctly that this is a `LocationProvider` specific parameter...

Why just get the root for the data/metadata from the LocationProvider? Why not expose these methods instead: ``` // initialize the provider with the root paths and the `useRelativePath` config,...

@wecharyu: Mostly LGTM. I would like to see @nrg4878's opinion as well, since he is more knowledgeable around HMS. Thanks, Peter

Very nice work @dengzhhu653! Could we add BeeLine to the examples, so the user could start to run queries immediately? Will we officially provide an already built image for the...

It would be good to create unit tests to define the expected behaviour and prevent changes in it

Do we have SQL support for this? If yes, then we might want to write a query test for it. Also, please rebase, to fix the failing test. Thanks, Peter

We should check around the security here. I just realized that changing the resource URIs could allow to inject malicious code under a function, so in most live clusters this...

> Hi @pvary thanks for your concern. It is indeed important to do authorization for operating UDF. But I do not think it should be an admin privilege for the...

As @kbendick mentioned, there should be an exception in the logs for the application. It would be great to check the application log for `job_1659792265699_0058`. Also it would be great...