Allow setting job name when using StatementSet

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Allow setting job name when using StatementSet

Yuval Itzchakov
Hi,

Currently when using StatementSet, the name of the job is autogenerated by the runtime:

image.png

Is there any reason why there shouldn't be an overload that allows the user to explicitly specify the name of the running job?
--
Best Regards,
Yuval Itzchakov.
Reply | Threaded
Open this post in threaded view
|

Re: Allow setting job name when using StatementSet

Nicolaus Weidner
Hi Yuval,

I am not familiar with the Table API, but in the fragment you posted, the generated job name is only used as default if configuration option pipeline.name is not set. Can't you just set that to the name you want to have?

Best wishes,
Nico

On Mon, Jun 7, 2021 at 10:09 AM Yuval Itzchakov <[hidden email]> wrote:
Hi,

Currently when using StatementSet, the name of the job is autogenerated by the runtime:

image.png

Is there any reason why there shouldn't be an overload that allows the user to explicitly specify the name of the running job?
--
Best Regards,
Yuval Itzchakov.
Reply | Threaded
Open this post in threaded view
|

Re: Allow setting job name when using StatementSet

JING ZHANG
I agree with Nico, I just add the link of pipeline.name here.

Nicolaus Weidner <[hidden email]> 于2021年6月7日周一 下午11:46写道:
Hi Yuval,

I am not familiar with the Table API, but in the fragment you posted, the generated job name is only used as default if configuration option pipeline.name is not set. Can't you just set that to the name you want to have?

Best wishes,
Nico

On Mon, Jun 7, 2021 at 10:09 AM Yuval Itzchakov <[hidden email]> wrote:
Hi,

Currently when using StatementSet, the name of the job is autogenerated by the runtime:

image.png

Is there any reason why there shouldn't be an overload that allows the user to explicitly specify the name of the running job?
--
Best Regards,
Yuval Itzchakov.
Reply | Threaded
Open this post in threaded view
|

Re: Allow setting job name when using StatementSet

Yuval Itzchakov
Yup, that worked. Thank you guys for pointing it out!

On Tue, Jun 8, 2021, 09:33 JING ZHANG <[hidden email]> wrote:
I agree with Nico, I just add the link of pipeline.name here.

Nicolaus Weidner <[hidden email]> 于2021年6月7日周一 下午11:46写道:
Hi Yuval,

I am not familiar with the Table API, but in the fragment you posted, the generated job name is only used as default if configuration option pipeline.name is not set. Can't you just set that to the name you want to have?

Best wishes,
Nico

On Mon, Jun 7, 2021 at 10:09 AM Yuval Itzchakov <[hidden email]> wrote:
Hi,

Currently when using StatementSet, the name of the job is autogenerated by the runtime:

image.png

Is there any reason why there shouldn't be an overload that allows the user to explicitly specify the name of the running job?
--
Best Regards,
Yuval Itzchakov.