[
https://issues.apache.org/jira/browse/HIVE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653005#action_12653005
]
Joydeep Sen Sarma commented on HIVE-65:
---------------------------------------
@Zheng - i don't follow. i thought we discussed a while back that
double->string conversion is non-intuitive in a comparison between double and
string. it's almost always the case that the user in such a case would like the
string to be treated as a double and hence we had talked about putting string
at the base of the partial order. mysql type conversion agrees with this
approach.
i am ok with using mysql type conversion semantics as well - but i think what
we had agreed was better (in terms of partial order and finding least common
super-type to convert to). this actually has space consequences - for example
in mysql string + int will produce double. which consumes double the space of
int (which is the least common super-type).
i still don't see the problem with this approach (and letting udf polymorphism
take care of ambiguities)
> Implict conversion from integer to long broken for Dynamic Serde tables
> -----------------------------------------------------------------------
>
> Key: HIVE-65
> URL: https://issues.apache.org/jira/browse/HIVE-65
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Ashish Thusoo
> Assignee: Zheng Shao
>
> For a dynamic serde table that has a bigint column, implict conversion from
> int to bigint seems to be broken. I have not verified this for other tables.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
