kz930 opened a new pull request, #7518:
URL: https://github.com/apache/texera/pull/7518

   ### What changes were proposed in this PR?
   
   Backport of #7327 to `release/v1.2`, superseding #7401. That PR's branch 
lives on `apache/texera` rather than a fork, so the conflict resolution could 
not be pushed to it.
   
   The operator change is #7327's, unchanged. Network Graph built its node set 
with `set(sources + destinations)`; on two pandas Series `+` is element-wise, 
so the set held each source glued to its destination rather than the union of 
the two columns. This takes the union in first-appearance order.
   
   The cherry-pick's one conflict was `NetworkGraphOpDescSpec.scala`, which 
does not exist on `release/v1.2` — it was created on main by #5640, which was 
never backported. Resolving that modify/delete by taking the whole file, which 
is what #7401 carries, brings across three cases asserting the assertion text 
names the empty field. This branch still has a bare `assert(source.nonEmpty)`, 
so those three fail here: running #7401's branch as it stands gives three 
passed and three failed. This backport instead carries only the case #7327 
added, so what lands is the one-line operator fix and the test that pins it.
   
   ### Any related issues, documentation, discussions?
   
   Backport of #7327. Originally linked #7325. Supersedes #7401, which can be 
closed.
   
   ### How was this PR tested?
   
   `NetworkGraphOpDescSpec` on this branch: one case, passing. Reverting the 
operator line leaves it failing. `WorkflowOperator/scalafmtCheckAll` and 
`WorkflowOperator/scalafixAll --check` are both clean.
   
   The operator change is byte-identical to #7327, where it was verified by 
dumping and executing the generated module over rows carrying known edges.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Opus 5)
   


-- 
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]

Reply via email to