You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Raymond Xu (Jira)" <ji...@apache.org> on 2022/03/30 06:16:00 UTC

[jira] [Commented] (HUDI-3321) HFileWriter, HFileReader and HFileDataBlock should avoid hardcoded key field name

    [ https://issues.apache.org/jira/browse/HUDI-3321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514455#comment-17514455 ] 

Raymond Xu commented on HUDI-3321:
----------------------------------

Discussed with [~shivnarayan] we need this when we want to support hfile as base file. cc [~guoyihua]


> HFileWriter, HFileReader and HFileDataBlock should avoid hardcoded key field name
> ---------------------------------------------------------------------------------
>
>                 Key: HUDI-3321
>                 URL: https://issues.apache.org/jira/browse/HUDI-3321
>             Project: Apache Hudi
>          Issue Type: Improvement
>          Components: code-quality, metadata
>            Reporter: Manoj Govindassamy
>            Assignee: Ethan Guo
>            Priority: Major
>             Fix For: 0.11.0
>
>
> Today HFileReader has the hardcoded key field name for the schema. This key field is used by HFileWriter, HFileDataBlock for HFile key dedupliacation feature. When users want to use the HFile format, this hard coded key field name can be preventing the usecase. We need a way to pass in the writer/reader/query configs to the HFile storage layer so as to use the right key field name. 
>  
> Related: HUDI-2763



--
This message was sent by Atlassian Jira
(v8.20.1#820001)