You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Rahul Challapalli (JIRA)" <ji...@apache.org> on 2015/10/09 02:34:26 UTC
[jira] [Closed] (DRILL-3832) Metadata Caching : There should be a
way for the user to know that the cache has been leveraged
[ https://issues.apache.org/jira/browse/DRILL-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Challapalli closed DRILL-3832.
------------------------------------
Resolution: Fixed
This has been fixed by steven commit 1cfd4c20d30dd042290e769472e60d06ae66020c
> Metadata Caching : There should be a way for the user to know that the cache has been leveraged
> -----------------------------------------------------------------------------------------------
>
> Key: DRILL-3832
> URL: https://issues.apache.org/jira/browse/DRILL-3832
> Project: Apache Drill
> Issue Type: Improvement
> Components: Metadata
> Reporter: Rahul Challapalli
>
> git.commit.id.abbrev=3c89b30
> Currently the user has no way of knowing that the metadata cache file has been leveraged apart from comparing the time which could be influenced by other factors.
> It would be helpful while debugging to know whether or not the cache has been leveraged. This information can be added to one or a combination of the below places
> 1. Profiles
> 2. Explain Plan Output
> 3. Log files
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)