You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "zhangshenghang (via GitHub)" <gi...@apache.org> on 2026/07/01 00:33:02 UTC
[PR] [Fix][Transform-V2] Parse custom LLM array string response [seatunnel]
zhangshenghang opened a new pull request, #11235:
URL: https://github.com/apache/seatunnel/pull/11235
### Purpose
Fixes #9998. Custom LLM responses can return `choices[0].message.content` as a string that itself contains a JSON array, such as `["value"]`. The transform previously treated that value as a plain string, so users saw the array literal in the output column.
### Changes
- Parse custom LLM string responses as a JSON list when possible.
- Keep plain string responses as a single output value.
- Avoid parsing the same custom response multiple times.
- Add unit coverage for OpenAI-compatible custom responses whose content is a JSON array string.
### Validation
- `./mvnw -pl seatunnel-transforms-v2 -DskipIT -Dskip.spotless=true -Dtest=LLMRequestJsonTest test`
- `./mvnw spotless:apply`
- `./mvnw -q -DskipTests verify`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [Fix][Transform-V2] Parse custom LLM array string response [seatunnel]
Posted by "davidzollo (via GitHub)" <gi...@apache.org>.
davidzollo merged PR #11235:
URL: https://github.com/apache/seatunnel/pull/11235
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [Fix][Transform-V2] Parse custom LLM array string response [seatunnel]
Posted by "DanielLeens (via GitHub)" <gi...@apache.org>.
DanielLeens commented on PR #11235:
URL: https://github.com/apache/seatunnel/pull/11235#issuecomment-4854221966
Thanks for the update. I rechecked the current head against the latest `dev`, and the source-level blockers from my previous Daniel review still stand on this branch.
- base branch: `dev`
- head SHA: `5e4fcfdf8b7839a4adefe5734e0d0c1e6bf79216`
- compare status: `diverged`
- ahead_by: `1`
- behind_by: `8`
- CI / merge gate snapshot: `Build FAILURE`
The current failing CI signal does not look actionable on top of this stale head yet, so the lowest-cost next step is to sync with the latest `dev` and rerun CI first. If anything still fails after the sync, I am happy to take another look on top of the updated head.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org