drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5481) Allow Drill to persist profiles in-memory only with a max capacity
Date Tue, 09 May 2017 19:41:04 GMT

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

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

Github user kkhatua commented on the issue:

    https://github.com/apache/drill/pull/827
  
    @ppadma, @sudheeshkatkam 
    Updated most of the changes except the flag itself. Waiting for a quick review and final
comment on whether I can change the flag from _drill.exec.sys.store.provider.local.write_
to _drill.exec.sys.store.provider.local.inmemory.write_ .


> Allow Drill to persist profiles in-memory only with a max capacity
> ------------------------------------------------------------------
>
>                 Key: DRILL-5481
>                 URL: https://issues.apache.org/jira/browse/DRILL-5481
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.10.0
>            Reporter: Kunal Khatua
>            Assignee: Kunal Khatua
>
> To allow for fast persistence of profiles on a temporary basis (i.e. till the life of
the Drillbit), an existing test class {{org.apache.drill.exec.testing.store.NoWriteLocalStore.java}}
was refactored to {{org.apache.drill.exec.store.sys.store.EphemeralPersistentStore}} and given
the ability to maintain a max capacity.
> This should allow query profiles to be available for as long as the Drillbit process'
lifespan.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message