[
https://issues.apache.org/jira/browse/HIVE-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566913#comment-13566913
]
Jakob Homan commented on HIVE-3833:
-----------------------------------
This patch has broken Avro (and probably HBase and Cassandra) for partitioned
tables since it no longer passes the table properties down to the serde:
{noformat}+ Properties partProps =
+ (pd.getPartSpec() == null || pd.getPartSpec().isEmpty()) ?
+ pd.getTableDesc().getProperties() : pd.getProperties();{noformat}
Was this intentional? If so, it's a breaking change and should be marked as
such. If not, since it's not been in a release yet, can we revert the patch?
See HIVE-3953.
> object inspectors should be initialized based on partition metadata
> -------------------------------------------------------------------
>
> Key: HIVE-3833
> URL: https://issues.apache.org/jira/browse/HIVE-3833
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Namit Jain
> Fix For: 0.11.0
>
> Attachments: hive.3833.10.patch, hive.3833.11.patch,
> hive.3833.12.patch, hive.3833.13.patch, hive.3833.14.patch,
> hive.3833.16.path, hive.3833.17.patch, hive.3833.18.patch,
> hive.3833.19.patch, hive.3833.1.patch, hive.3833.20.patch,
> hive.3833.21.patch, hive.3833.22.patch, hive.3833.23.patch,
> hive.3833.2.patch, hive.3833.3.patch, hive.3833.4.patch, hive.3833.5.patch,
> hive.3833.6.patch, hive.3833.7.patch, hive.3833.8.patch, hive.3833.9.patch
>
>
> Currently, different partitions can be picked up for the same input split
> based on the
> serdes' etc. And, we dont allow to change the schema for
> LazyColumnarBinarySerDe.
> Instead of that, different partitions should be part of the same split, only
> if the
> partition schemas exactly match. The operator tree object inspectors should
> be based
> on the partition schema. That would give greater flexibility and also help
> using binary serde with rcfile
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
