[
https://issues.apache.org/jira/browse/HIVE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654552#action_12654552
]
Joydeep Sen Sarma commented on HIVE-134:
----------------------------------------
i disagree.
the whole idea with serde is that these are opaque to hive except for the
functional interfaces exposed via the serde interface. as u can see - the
interfaces don't currently have any information about 'options' that the serde
may use. Hence we pass the jobconf to the serde so that it can get whatsoever
it pleases.
i don't see the point of this jira. we are trying to create a more strongly
coupled system. in order to do what Raghu is saying - now we will need another
interface in the serde to get the list of required options, and then extract
them from the jobconf and then pass those in. what good will this serve? why
are we making it even harder to write serdes?
what real and existing problem are we trying to solve here?
> job conf being passed to serde (initialize)
> -------------------------------------------
>
> Key: HIVE-134
> URL: https://issues.apache.org/jira/browse/HIVE-134
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Serializers/Deserializers
> Reporter: Namit Jain
>
> Currently, job conf is being passed to serde - serde should not need job
> conf. Anyway, properties is being passed around which can contain any
> name/value pairs.
> Once jira-127 is committed, this should be done in a follow-up
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
