You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We traverse the dataflow and find all of the sinks and replace them with WebSinks
Then on the frontend, we request the /v1/pipelines/{pipeline_id}/jobs/{job_id}/output API which makes a request to the controller to stream the job outputs.
This then merges all of the outputs into a single result table, which can be pretty hard to parse.
Instead we should separate out the outputs for each query (possibly into separate tabs in the UI) and allow distinguishing which operator they came from the in API.
The text was updated successfully, but these errors were encountered:
Currently the preview experience works like this:
Then on the frontend, we request the
/v1/pipelines/{pipeline_id}/jobs/{job_id}/output
API which makes a request to the controller to stream the job outputs.This then merges all of the outputs into a single result table, which can be pretty hard to parse.
Instead we should separate out the outputs for each query (possibly into separate tabs in the UI) and allow distinguishing which operator they came from the in API.
The text was updated successfully, but these errors were encountered: