Assigned
Status Update
No update yet.
Comments
va...@google.com
ja...@google.com
This feature request has been forwarded to the Data Fusion engineering team so that they may evaluate it. Note that there are no ETAs or guarantees of implementation for feature requests. All communication regarding this feature request is to be done here.
br...@homedepot.com
Struct support is being prioritized and can be tracked in open source by https://issues.cask.co/browse/CDAP-15349 .
ja...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
When querying all batch pipeline run successed status, I found that the succeeded value was not found for every successful run.
fetch dataflow_job ::
| window(1m)
| filter resource.job_name=~".*${jobNameFilter.value}.*"
| map add[status_label: val()], [count: 1]
| filter status_label="SUCCEEDED"
| group_by [status_label], sum(val())
| group_by requested_period(), .max
| every requested_period()
What you expected to happen:
I was expecting to see a count for every job which ran successfully.
Steps to reproduce:
Run a batch pipeline multiple times and this issue was showing up roughly 1 out of every 5 runs.
Other information (workarounds you have tried, documentation consulted, etc):