[ https://issues.apache.org/jira/browse/HIVE-24503?focusedWorklogId=523726&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-523726 ]
ASF GitHub Bot logged work on HIVE-24503: ----------------------------------------- Author: ASF GitHub Bot Created on: 14/Dec/20 07:16 Start Date: 14/Dec/20 07:16 Worklog Time Spent: 10m Work Description: maheshk114 commented on a change in pull request #1753: URL: https://github.com/apache/hive/pull/1753#discussion_r542159016 ########## File path: ql/src/java/org/apache/hadoop/hive/ql/exec/vector/VectorSerializeRow.java ########## @@ -383,6 +414,13 @@ private void serializeMapWrite( serializeWrite.finishMap(); } + class VectorSerializeListWriter extends VectorSerializeWriter { + @Override + void serialize(Object colInfo, Field field, int adjustedBatchIndex) throws IOException { + serializeListWrite((ListColumnVector)colInfo, field, adjustedBatchIndex); + } + } + private void serializeListWrite( Review comment: done ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 523726) Time Spent: 50m (was: 40m) > Optimize vector row serde by avoiding type check at run time > ------------------------------------------------------------- > > Key: HIVE-24503 > URL: https://issues.apache.org/jira/browse/HIVE-24503 > Project: Hive > Issue Type: Bug > Components: Hive > Reporter: mahesh kumar behera > Assignee: mahesh kumar behera > Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > Serialization/Deserialization of vectorized batch done at VectorSerializeRow > and VectorDeserializeRow does a type checking for each column of each row. > This becomes very costly when there are billions of rows to read/write. This > can be optimized if the type check is done during init time and specific > reader/writer classes are created. This classes can be used directly stored > in filed structure to avoid run time type check. -- This message was sent by Atlassian Jira (v8.3.4#803005)