You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vihang Karajgaonkar (JIRA)" <ji...@apache.org> on 2019/06/27 21:02:00 UTC
[jira] [Updated] (HIVE-21932) IndexOutOfRangeExeption in
FileChksumIterator
[ https://issues.apache.org/jira/browse/HIVE-21932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vihang Karajgaonkar updated HIVE-21932:
---------------------------------------
Status: Patch Available (was: Open)
> IndexOutOfRangeExeption in FileChksumIterator
> ---------------------------------------------
>
> Key: HIVE-21932
> URL: https://issues.apache.org/jira/browse/HIVE-21932
> Project: Hive
> Issue Type: Bug
> Reporter: Vihang Karajgaonkar
> Assignee: Vihang Karajgaonkar
> Priority: Major
> Attachments: HIVE-21932.01.patch
>
>
> According to definition of {{InsertEventRequestData}} in {{hive_metastore.thrift}} the {{filesAddedChecksum}} is a optional field. But the FileChksumIterator does not handle it correctly when a client fires a insert event which does not have file checksums. The issue is that {{InsertEvent}} class initializes fileChecksums list to a empty arrayList to the following check will never come into play
> {noformat}
> result = ReplChangeManager.encodeFileUri(files.get(i), chksums != null ? chksums.get(i) : null,
> subDirs != null ? subDirs.get(i) : null);
> {noformat}
> The chksums check above should include a {{!chksums.isEmpty()}} check as well in the above line.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)