Closed dolfinus closed 3 months ago
Name | Link |
---|---|
Latest commit | 49bcd9c59d8b99179c909d9bfddb6206a49b62ad |
Latest deploy log | https://app.netlify.com/sites/peppy-sprite-186812/deploys/66b0e33537083f0008684c02 |
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 85.47%. Comparing base (
94ec22e
) to head (49bcd9c
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Problem
After upgrading to 0.48 opening some job details lead to 404 errors. This is because I have job names with slashes, like
my/session/name
, resulting API query to look like this:http://localhost:8080/api/v1/namespaces/yarn%3A%2F%2Fsomecluster/jobs/my/session/name.execute_insert_into_hadoop_fs_relation_command
But it should be:
http://localhost:8080/api/v1/namespaces/yarn%3A%2F%2Fsomecluster/jobs/my%2Fsession%2Fname.execute_insert_into_hadoop_fs_relation_command
Same could be applied to dataset, tag or field names.
Solution
One-line summary:
Urlencode job, dataset, tag and field names while sending API request.
Checklist
CHANGELOG.md
(Depending on the change, this may not be necessary)..sql
database schema migration according to Flyway's naming convention (if relevant)