Kush
Kush
@sravankorumilli do have this prioritized at the moment or are we planning to do it?
Does this issue include having an execution env like airflow? Because rest is already working I guess?
How are we planning to handle the authn/z of the request?
This looks neat, so it's like if the user has explicitly provided a schema, we will assume auto-detect is disabled?
Sure, let's get the ball rolling for v1. ## Questions as a user > Where can I see the job run details, including compiled assets ? Job run details should...
Can you give an example for this?
What exactly is broken in current behaviour? I thought users just create a new job in new namespace and delete the existing one?
Why is `Even assigning all the replay requests to a different pool at the scheduler level is not an option now` not an easy solution for now? Can you elaborate?
Oh yeah, sorry I forgot this limitation, my bad. Thanks!
@flashmob Are you still planning to finish this PR? I see you have invested quite some time but then the motivation died down? 😄 We need you back.