Skip to content

[ZEPPELIN-6742] Connect the Assistant frontend to conversation REST and WebSocket APIs - #5563

Open
voidmatcha wants to merge 2 commits into
apache:branch-seung-00-assistant-transport-clean-tempfrom
voidmatcha:voidmatcha/assistant-v2-6-transport
Open

voidmatcha wants to merge 2 commits into
apache:branch-seung-00-assistant-transport-clean-tempfrom
voidmatcha:voidmatcha/assistant-v2-6-transport

Conversation

@voidmatcha

@voidmatcha voidmatcha commented Oct 9, 2026 •

Copy link
Copy Markdown
Member

What is this PR for?

Connect the Assistant frontend to the conversation REST and WebSocket APIs. The transport provides conversation creation and retrieval, message sending, and response delivery for the UI.

This PR depends on server PR #5547, shared prerequisites #5558, and UI contracts #5561. Its temporary base contains exactly those changes. After a WebSocket disconnect, the transport shows an uncertain run state until the user reloads the saved history; it does not require a server-side running field.

What type of PR is it?

Feature

Todos

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-6742

How should this be tested?

Run from zeppelin-web-angular/:

npm run build-project:sdk
npm run typecheck:react
npm --prefix projects/zeppelin-react test -- src/entities/assistant/model/assistantTransport.spec.ts

Also verify the REST and WebSocket integration against the final API contract from server PR #5547.

Screenshots (if appropriate)

N/A

Questions:

  • Does the license files need to update? No
  • Is there breaking changes for older versions? No
  • Does this needs documentation? No

@voidmatcha
voidmatcha changed the base branch from temp/seung-00/assistant-transport-base to branch-seung-00-assistant-transport-base-temp October 9, 2026 01:35
@voidmatcha voidmatcha closed this Oct 9, 2026
@voidmatcha voidmatcha reopened this Oct 9, 2026
@voidmatcha
voidmatcha force-pushed the voidmatcha/assistant-v2-6-transport branch 2 times, most recently from 2aaa236 to b75de05 Compare October 9, 2026 09:09
@voidmatcha
voidmatcha changed the base branch from branch-seung-00-assistant-transport-base-temp to branch-seung-00-assistant-transport-clean-temp October 9, 2026 09:09
@voidmatcha
voidmatcha force-pushed the voidmatcha/assistant-v2-6-transport branch from b75de05 to c470802 Compare October 9, 2026 09:13
@voidmatcha

Copy link
Copy Markdown
Member Author

This PR connects the frontend to the conversation REST API and WebSocket run events. After a connection loss, the user can reload saved history; the transport does not require a server-side running field.

The current diff is +1,460/-1 across four files. Excluding the 800 lines of tests, the review diff is +660/-1. There is no lockfile change.

This PR depends on #5547, #5558, and #5561. Its temporary base contains those prerequisites without the separate server fixes. Reviews can proceed against this diff; after the prerequisites merge, I will rebase and retarget the PR to master, then verify the final API contract and CI before merging.

@voidmatcha
voidmatcha force-pushed the branch-seung-00-assistant-transport-clean-temp branch from b772a8d to 9f119fc Compare October 10, 2026 00:50
@voidmatcha
voidmatcha force-pushed the voidmatcha/assistant-v2-6-transport branch from 0c3b303 to c41de73 Compare October 10, 2026 00:50
@voidmatcha
voidmatcha force-pushed the branch-seung-00-assistant-transport-clean-temp branch from 9f119fc to b0b71a0 Compare October 10, 2026 08:27
@voidmatcha
voidmatcha force-pushed the voidmatcha/assistant-v2-6-transport branch from c41de73 to 3af8991 Compare October 10, 2026 08:27
@voidmatcha
voidmatcha force-pushed the branch-seung-00-assistant-transport-clean-temp branch from b0b71a0 to fc57755 Compare October 10, 2026 08:37
@voidmatcha
voidmatcha force-pushed the voidmatcha/assistant-v2-6-transport branch from 3af8991 to 3bcb8e2 Compare October 10, 2026 08:37

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant