When submitting a job with collections on separate upstream backends, but with "crossbackend" feature enabled, the user still sees a validation warning about "Collections across multiple backends" because validation does not take the "crossbackend" job option into account.
When submitting a job with collections on separate upstream backends, but with "crossbackend" feature enabled, the user still sees a validation warning about "Collections across multiple backends" because validation does not take the "crossbackend" job option into account.
the auto-validation feature of the python client triggers this warning from
create_job
:The validation warning is not blocking at the moment, but unnecessary and confusing to the user