mrhhsg commented on PR #69288: URL: https://github.com/apache/doris/pull/69288#issuecomment-6283027150
<!-- autopilot-response --> Reviewed the current review state at head `be394b4675c2df72f939406ee66e724d52b195c2`. - `PRR_kwDOBfSlxs8AAAABTBibMA` (Code Review, COMMENTED): reports no actionable findings. Its trace matches the code: the object is already open and waiting for a key, the removed `writeStartObject()` was rejected by the writer state machine, and the removed `writeEndObject()` closed the current object early; with the extra pair gone, the single remaining `writeEndObject()` closes the current object and enclosing objects can still emit their following members. The optional extension it mentions (additional null/container-value, multi-pair and const-shape combinations) is a coverage suggestion, not a defect; the changed path is already covered by the new BE rows and the ordered SQL cases. No code change is needed for it. - `IC_kwDOBfSlxs8AAAABdY8YwQ` (contribution checklist prompt): the PR description covers the requested points (problem and reproduction, root cause in `FunctionJsonbModify::write_json_value`, fix, behavior change and impact, test list). No new feature was added and no unrelated code was refactored. - `IC_kwDOBfSlxs8AAAABdY8eBA` (`/review`): the Code Review workflow completed for this head with no actionable finding, so there is nothing to fix from this comment. - `IC_kwDOBfSlxs8AAAABdZFJQA` (`run buildall`) and the following TPC-H / TPC-DS / ClickBench reports (`IC_kwDOBfSlxs8AAAABdbU2xA`, `IC_kwDOBfSlxs8AAAABdbhfWQ`, `IC_kwDOBfSlxs8AAAABdbnpOw`): benchmark runs for this head, informational only; no code action is required. - `IC_kwDOBfSlxs8AAAABdmr-tg` (`run beut`): BE UT passed for this head. Locally, the `FunctionJsonbTEST.*` suite (20 tests, including the new `JsonbModifyNestedMissingMemberKeepsFollowingSiblings`) was re-run on the head build and all tests passed. - `IC_kwDOBfSlxs8AAAABdmsCYQ` (`run external`) and `IC_kwDOBfSlxs8AAAABdmsGSw` (`run nonConcurrent`): pipeline trigger comments. The queued TeamCity builds are unrelated reruns; no code action is required here. - `IC_kwDOBfSlxs8AAAABdn3jKg` (BE UT coverage report): informational only. - The two earlier `<!-- autopilot-response -->` comments (`IC_kwDOBfSlxs8AAAABdZD3VA`, `IC_kwDOBfSlxs8AAAABdmndXg`): prior round summaries, kept for context. There are no inline review threads on this PR. No code changes were made in this round, and the branch head is unchanged at `be394b4675c2df72f939406ee66e724d52b195c2`. Could a human reviewer take another look and approve if the change looks good? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
