Assigned
Status Update
No update yet.
Comments
va...@google.com
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.
What you expected to happen:
Requesting a streamlined method for configuring the Tez UI (specifically, the config/configs.js and potentially config/default-app-config.js files) through a dedicated classification within Dataproc's cluster properties.
Problem you have encountered:
Currently, Dataproc lacks a built-in mechanism to directly modify these Tez UI configuration files. Users have to manually modify configuration files using scripts. This feature request would eliminate the need for workarounds like modifying configuration files through scripts.
Other information (workarounds you have tried, documentation consulted, etc):
Expecting a tez-ui classification with parameters that can be modified. Entries from[0].
The latest script used to correct Tez UI bugs and configure the pipeline according to recommended work arounds from the Dataproc team and internal findings has been attached.
Preferably, an entry would be seen here[1].
Links:
[0]
[1]