min-guk commented on PR #2273: URL: https://github.com/apache/systemds/pull/2273#issuecomment-2981151063
> I would handle this case similar to mismatching types on if/else branches where we force consistency. The new FType is just an extension of previous LOUT, FOUT to LOUT, FOUT-ROW, FOUT-COL Yes, I’ll approach this similarly to how we resolve conflicts in federated output types, such as mismatches in if/else branches where we enforce consistency. The key difference is that, in the previous case, conflicts couldn’t be detected during enumeration and were resolved only afterward by traversing the selected optimal federated plan. In contrast, this case requires resolving FType conflicts during FType propagation over the DAG, i.e., before enumeration and cost-based decisions. Since we don’t yet have cost information, we can’t rely on cost to guide the resolution. Instead, we may need to unify FTypes via broadcasting or define a priority order among FTypes and propagate the higher-priority one. -- 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]
