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

Aihua Xu commented on HIVE-9500:
--------------------------------

Thanks [~thejas] for the comments.

1. UTF8 could contain negative byte values. Probably it's better than using the 
positive byte values. But since we escape if they appear in the data, it should 
be fine.
2. Yeah. It's not applicable to all the serdes. I will update that.
3. Performance for HashMap should be comparable to array. I can get rid of 
get() call since we only care if the key exists or not and the value is always 
"true". Using array seems not intuitive and we have to explain what's the array 
is for. And now with negative byte, we need to calculate the index and get the 
value. So that's why I still prefer to HashMap.

Will give it a try to upload the review by excluding the q.out.

> Support nested structs over 24 levels.
> --------------------------------------
>
>                 Key: HIVE-9500
>                 URL: https://issues.apache.org/jira/browse/HIVE-9500
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>              Labels: SerDe
>             Fix For: 1.2.0
>
>         Attachments: HIVE-9500.1.patch, HIVE-9500.2.patch
>
>
> Customer has deeply nested avro structure and is receiving the following 
> error when performing queries.
> 15/01/09 20:59:29 ERROR ql.Driver: FAILED: SemanticException 
> org.apache.hadoop.hive.serde2.SerDeException: Number of levels of nesting 
> supported for LazySimpleSerde is 23 Unable to work with level 24
> Currently we support up to 24 levels of nested structs when 
> hive.serialization.extend.nesting.levels is set to true, while the customers 
> have the requirement to support more than that. 
> It would be better to make the supported levels configurable or completely 
> removed (i.e., we can support any number of levels). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to