Move collapsedZones from query parameters to request body

Christen

My team maintains a very large Dataiku project with 500+ flow zones. We intentionally keep this work in a single project so we can manage version control and promotion to automation nodes cleanly, without having to coordinate dependencies and changes across multiple projects.

Most of our work is done through the API, but we still need to use the Dataiku UI at times, and that is where we run into performance issues.

Because the project flow is so large, we typically want most flow zones to remain collapsed, since we usually work in only one or two zones at a time. However, using the "Collapse all" option in the Flow UI causes a 431 Request Header Fields Too Large error on:

/dip/api/flow/recipes/get-graph-serialized

The list of flow zones we have is so large that it makes the request URL too long when we collapse all flow zones.

For large projects, it would be a major usability improvement if collapsedZones were not sent as a query parameter but instead passed in the request body.

Michael Grayson

Hi Christian, I've moved your post from the "Community Feedback" area to the "Product Ideas" area where it will be more relevant.

Community Feedback is for feedback on the Community itself, sorry that wasn't clear.