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

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

amansinha100 commented on issue #1728: DRILL-7089: Implement caching for 
TableMetadataProvider at query level and adapt statistics to use Drill 
metastore API
URL: https://github.com/apache/drill/pull/1728#issuecomment-480620573
 
 
   @vvysotskyi one other thought is that since this PR touches several of the 
Statistics related classes,  considering the Drill 1.16.0 release is imminent 
and the core statistics testing is ongoing, it would be disruptive to introduce 
these changes at this stage.  Even though functional regression might pass, we 
have had performance issues even with statistics disabled, so I feel hesitant 
for 1.16.0.  Let me know what you think.  
 
----------------------------------------------------------------
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:
us...@infra.apache.org


> Implement caching of BaseMetadata classes
> -----------------------------------------
>
>                 Key: DRILL-7089
>                 URL: https://issues.apache.org/jira/browse/DRILL-7089
>             Project: Apache Drill
>          Issue Type: Sub-task
>    Affects Versions: 1.16.0
>            Reporter: Volodymyr Vysotskyi
>            Assignee: Volodymyr Vysotskyi
>            Priority: Major
>             Fix For: 1.16.0
>
>
> In the scope of DRILL-6852 were introduced new classes for metadata usage. 
> These classes may be reused in other GroupScan instances to preserve heap 
> usage for the case when metadata is large.
> The idea is to store {{BaseMetadata}} inheritors in {{DrillTable}} and pass 
> them to the {{GroupScan}}, so in the scope of the single query, it will be 
> possible to reuse them.



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

Reply via email to