hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ádám Szita (Jira) <>
Subject [jira] [Commented] (HIVE-23729) LLAP text cache fails when using multiple tables/schemas on the same files
Date Fri, 19 Jun 2020 12:45:00 GMT


Ádám Szita commented on HIVE-23729:

[~odraese], [~gopalv], [~asinkovits] can you please take a look at this PR?

> LLAP text cache fails when using multiple tables/schemas on the same files
> --------------------------------------------------------------------------
>                 Key: HIVE-23729
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Ádám Szita
>            Assignee: Ádám Szita
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
> When using the text based cache we will hit exceptions in the following case:
>  * Table A with 3 columns is defined on location X (where we have text based data files)
>  * Table B with 2 columns is defined on the same location X
>  * User runs a query on table A, thereby filling the LLAP cache.
>  * If the next query goes against table B that has a different schema, LLAP will throw
an error:
> {code:java}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 2
>  at org.apache.hadoop.hive.llap.cache.SerDeLowLevelCacheImpl.getCacheDataForOneSlice(
>  at org.apache.hadoop.hive.llap.cache.SerDeLowLevelCacheImpl.getFileData(
>  at
>  at
>  at$
>  at$
> This is because the cache lookup is based on file ID, which in this case is the same
for both tables. However, unlike with ORC files, the cached content and the file content is
different, as it is dependent on the schema that was defined by the user. That's because the
original text content is encoded into ORC in the cache.
> I think for the text cache case we will need to extend the cache key from being just
the simple file ID to something that tracks the schema too. This will result in caching the
*same* *file* *content* multiple times (if there are multiple schemas like this), however
as we can see the *cached content itself could be quite different* (e.g. different streams
with different encodings), and in turn we gain correctness.

This message was sent by Atlassian Jira

View raw message