[
https://issues.apache.org/jira/browse/HUDI-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402961#comment-17402961
]
ASF GitHub Bot commented on HUDI-648:
-------------------------------------
liujinhui1994 commented on pull request #3312:
URL: https://github.com/apache/hudi/pull/3312#issuecomment-903460163
> @liujinhui1994 Thank you for raising this. Quite useful for debugging. Can
you please resolve the conflicts?
This is actually not used for debugging. There may be some wrong records in
the production environment. Users of these records expect a way to trace back
to facilitate the location of specific problems.
Ok i will handle the conflict
--
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]
> Implement error log/table for Datasource/DeltaStreamer/WriteClient/Compaction
> writes
> ------------------------------------------------------------------------------------
>
> Key: HUDI-648
> URL: https://issues.apache.org/jira/browse/HUDI-648
> Project: Apache Hudi
> Issue Type: New Feature
> Components: DeltaStreamer, Spark Integration, Writer Core
> Reporter: Vinoth Chandar
> Assignee: liujinhui
> Priority: Major
> Labels: pull-request-available, sev:normal, user-support-issues
> Attachments: image-2021-03-03-11-40-21-083.png
>
>
> We would like a way to hand the erroring records from writing or compaction
> back to the users, in a separate table or log. This needs to work generically
> across all the different writer paths.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
