[ 
https://issues.apache.org/jira/browse/DRILL-7171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818437#comment-16818437
 ] 

ASF GitHub Bot commented on DRILL-7171:
---------------------------------------

dvjyothsna commented on issue #1748: DRILL-7171: Create metadata directories 
cache file in the leaf level directories to support ConvertCountToDirectScan 
optimization.
URL: https://github.com/apache/drill/pull/1748#issuecomment-483441203
 
 
   @vdiravka Yes, I have also observed that there are two places we store the 
list of directories. I think we should keep the directories cache file as is 
since it is used for checking timestamps. I think we can remove the directories 
list from the Metadata Summary cache file. I will file a different jira for 
that. Let me know if you have any other comments.
 
----------------------------------------------------------------
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:
[email protected]


> Count(*) query on leaf level directory is not reading summary cache file.
> -------------------------------------------------------------------------
>
>                 Key: DRILL-7171
>                 URL: https://issues.apache.org/jira/browse/DRILL-7171
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Venkata Jyothsna Donapati
>            Assignee: Venkata Jyothsna Donapati
>            Priority: Minor
>             Fix For: 1.17.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Since the leaf level directory doesn't store the metadata directories file, 
> while reading summary if the directories cache file is not present, it is 
> assumed that the cache is possibly corrupt and reading of the summary cache 
> file is skipped. Metadata directories cache file should be created at the 
> leaf level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to