Andy
Andy
Currently, we expose "gauge" metrics for data job termination statuses, which we can then use to moonitor the operability of data jobs deployed in kubernetes clusters. This works fine for...
**What is the feature request? What problem does it solve?** Currently, we face issues when installing Versatile Data Kit on some platforms (e.g., Windows), which creates poor user experience. Building...
**Describe the bug** As part of https://github.com/vmware/versatile-data-kit/pull/769, the click dependency in vdk-core and vdk-control-cli was updated to 8.X. The merge was successfull and no exceptions were raised. However, the vdk-control-cli's...
**Describe the bug** As of pip version 22.0, vdk-core's CI/CD fails due to a dependency issue. The issue is caused by pip's dependency resolver, trying to backtrack one of vdk-core's...
**What is the feature request? What problem does it solve?** Extend Versatile Data Kit functionality to support sharing of job properties between data jobs. This would be useful in cases...
**What is the feature request? What problem does it solve?** Currently, when a data job fails with an User Error, and the error is caught by the Control Service and...
**What is the feature request? What problem does it solve?** Currently, there are two job builder directories in the Control Service project, one which is used, https://github.com/vmware/versatile-data-kit/tree/main/projects/control-service/projects/job-builder , and another...
**What is the feature request? What problem does it solve?** Currently, the quickstart-vdk package is build both as a package, and a docker image for different purposes. As it is...
**What is the feature request? What problem does it solve?** Currently, most of the projects are not released with a CHANGELOG, which makes it difficult to know what changes were...
VDK_ATTEMPT_ID not accessible from within data job code or not changing when a job pod is restarted
**What is the feature request? What problem does it solve?** By definition, the attempt_id should change on every job execution attempt (i.e., every time a job is re-tried in full)...