[
https://issues.apache.org/jira/browse/DRILL-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Challapalli updated DRILL-3835:
-------------------------------------
Description:
git.commit.id.abbrev=240a455
Looking at the below numbers, it looks like we are not doing an incremental
update to the cache when the first query is executed after the data has been
modified.
{code}
refresh table metadata 1st time : ~45 seconds
select count(*) from lineitem : ~32 seconds
Add a new file to the lineitem folder
select count(*) from lineitem: ~79 seconds
{code}
was:
git.commit.id.abbrev=240a455
Looking at the below numbers, it looks like we are not doing an incremental
update to the cache when the first query is executed after the data has been
modified.
{code}
refresh table metadata 1st time : ~45 seconds
select count(*) from lineitem : ~32 seconds
Add a new file to the lineitem folder
select count(*) from lineitem: ~79 seconds
{code}
Query :
{code}
{code}
> Metadata Caching : Running a query should update the cache incrementally when
> data gets modified
> ------------------------------------------------------------------------------------------------
>
> Key: DRILL-3835
> URL: https://issues.apache.org/jira/browse/DRILL-3835
> Project: Apache Drill
> Issue Type: Bug
> Components: Metadata
> Reporter: Rahul Challapalli
> Fix For: 1.2.0
>
>
> git.commit.id.abbrev=240a455
> Looking at the below numbers, it looks like we are not doing an incremental
> update to the cache when the first query is executed after the data has been
> modified.
> {code}
> refresh table metadata 1st time : ~45 seconds
> select count(*) from lineitem : ~32 seconds
> Add a new file to the lineitem folder
> select count(*) from lineitem: ~79 seconds
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
