[CARBONDATA-2464] Fixed OOM in case of complex type

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Assignee: Kumar Vishal
• Reporter: Kumar Vishal
• Created: 09/May/18 17:48
• Updated: 10/May/18 10:40
• Resolved: 10/May/18 10:40

Description

Problem: Query with Complex type is failing with OOM

Root Cause: Complex type child column(No-dictionary) values are written in LV format, while reading the data it will read length then based on length it is reading the data. Converting byte array to int is giving wrong length value, because of this it's trying to create big memory chunk and as memory is not available in Unsafe it is failing with OOM.

Code issue: While converting byte array to int it is not masking the the byte values and because of this is giving wrong integer value.

Solution: Mask each byte and then left shift the bits

 

 

Issue Links

• links to: GitHub Pull Request #2288