[
https://issues.apache.org/jira/browse/HIVE-24259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Sharma updated HIVE-24259:
---------------------------------
Description:
Description -
Problem -
1. Redundant check if table is present or not
2. Currently in order to get all constraint form the cachedstore. 6 different
call is made with in the cached store. Which led to 6 different call to raw
store
3. If constraints are null and valid then also a redundant call is made to raw
store.
DOD
1. Create a flag which tell weather constraint snapshot is valid or not.
2. if incremental addition happen to any of the constraint mark snapshot as
invalid and let updater thread to update cache with valid snapshot data.
3. Combine individual constraint call into one call for refresh and creation.
was:
Description -
Problem -
1. Redundant check if table is present or not
2. Currently in order to get all constraint form the cachedstore. 6 different
call is made with in the cached store. Which led to 6 different call to raw
store
DOD
1. Check only once if table exit in cached store.
2. Instead of calling individual constraint in cached store. Add a method which
return all constraint at once and if data is not consistent then fall back to
rawstore.
> [CachedStore] Optimise get all constraint api
> ---------------------------------------------
>
> Key: HIVE-24259
> URL: https://issues.apache.org/jira/browse/HIVE-24259
> Project: Hive
> Issue Type: Sub-task
> Reporter: Ashish Sharma
> Assignee: Ashish Sharma
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> Description -
> Problem -
> 1. Redundant check if table is present or not
> 2. Currently in order to get all constraint form the cachedstore. 6 different
> call is made with in the cached store. Which led to 6 different call to raw
> store
> 3. If constraints are null and valid then also a redundant call is made to
> raw store.
>
> DOD
> 1. Create a flag which tell weather constraint snapshot is valid or not.
> 2. if incremental addition happen to any of the constraint mark snapshot as
> invalid and let updater thread to update cache with valid snapshot data.
> 3. Combine individual constraint call into one call for refresh and creation.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
