[
https://issues.apache.org/jira/browse/HIVE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654538#action_12654538
]
Joydeep Sen Sarma commented on HIVE-134:
----------------------------------------
why is this a concern?
i vaguely remember discussing this long time in the past - and don't quite
agree that this is a bug. table serde properties capture per-table
configuration. but there are session or global configurations that can affect
serde behavior. for example - suppose we add a new option to dynamicserde to do
type conversions on demand (just as an example). it maybe that we want to test
this strategy out - the way we would control it is by passing the configuration
object in and controlling it via session options.
> 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.
