[I] Flush out direction for end to end writes using Row or InternalRow [hudi]

["hudi-bot (via GitHub)" <gi...@apache.org>]

hudi-bot opened a new issue, #17377:
URL: https://github.com/apache/hudi/issues/17377

   Flush out direction for end to end writes using Row or InternalRow
   
   ## JIRA info
   
   - Link: https://issues.apache.org/jira/browse/HUDI-9035
   - Type: Sub-task
   - Parent: https://issues.apache.org/jira/browse/HUDI-9019
   - Fix version(s):
     - 1.1.0


-- 
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@hudi.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Flush out direction for end to end writes using Row or InternalRow [hudi]

["rangareddy (via GitHub)" <gi...@apache.org>]

rangareddy commented on issue #17377:
URL: https://github.com/apache/hudi/issues/17377#issuecomment-5351241034

   This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-9035).
   
   **Findings: a direction/decision task rather than a defect - nothing to verify in code.**
   
   The GitHub body restates the title with no proposal, options, or decision criteria, so there is nothing here to validate or hand to a contributor. The right outcome is a written direction - a `dev@` thread or an RFC - not a patch.
   
   Worth flagging that this decision is load-bearing for other open work. #17341 (HUDI-8749, "Deprecate clustering with row writer") is explicitly blocked on the same question: its description asks *"is it even required since we are going w/ new FG reader flow now?"*, and on `master` the row-writer clustering path is still the default (`MultipleSparkJobExecutionStrategy.java:109` reads `hoodie.datasource.write.row.writer.enable` defaulting to `true`). Until the Row / InternalRow direction is settled, that ticket cannot move either.
   
   The JIRA is marked In Progress with an assignee, so there may be context not captured in this issue. Could that be summarised here, even briefly - the options under consideration and what would decide between them? That would let the dependent tickets be scoped.
   
   Keeping this open.
   


-- 
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@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org