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

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

Github user jacques-n commented on the pull request:

    https://github.com/apache/drill/pull/325#issuecomment-172747355
  
    Let's do a separate hangout. This seems to deep/specific to cover in a
    large group.
    On Jan 18, 2016 9:51 AM, "Hanifi Gunes" <[email protected]> wrote:
    
    > Cool. Let's sync up on tomorrow's weekly hangout. Let me know if that does
    > not work for you.
    >
    > —
    > Reply to this email directly or view it on GitHub
    > <https://github.com/apache/drill/pull/325#issuecomment-172604790>.
    >



> Refactor e/pstore interfaces and their factories to provide a unified 
> mechanism to access stores
> ------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-4275
>                 URL: https://issues.apache.org/jira/browse/DRILL-4275
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Flow
>            Reporter: Hanifi Gunes
>            Assignee: Deneche A. Hakim
>
> We rely on E/PStore interfaces to persist data. Even though E/PStore stands 
> for Ephemeral and Persistent stores respectively, the current design for 
> EStore does not extend the interface/functionality of PStore at all, which 
> hints abstraction for EStore is redundant. This issue proposes a new unified 
> Store interface replacing the old E/PStore that exposes an additional method 
> that report persistence level as follows:
> {code:title=Store interface}
> interface Store<V> {
>   StoreMode getMode();
>   V get(String key);
>   ...
> }
> enum StoreMode {
>   EPHEMERAL,
>   PERSISTENT,
>   ...
> }
> {code}
> The new design brings in less redundancy, more centralized code, ease to 
> reason and maintain.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to