Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
From: julienledem <git@git.apache.org>
To: dev@drill.apache.org
Reply-To: dev@drill.apache.org
References: <git-pr-283-drill@git.apache.org>
In-Reply-To: <git-pr-283-drill@git.apache.org>
Subject: [GitHub] drill pull request: DRILL-4134: Allocator updates
Content-Type: text/plain
Message-Id: <20151201003015.89F29E2C6C@git1-us-west.apache.org>
Date: Tue,  1 Dec 2015 00:30:15 +0000 (UTC)

Github user julienledem commented on a diff in the pull request:

    https://github.com/apache/drill/pull/283#discussion_r46225495
  
    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/ops/FragmentContext.java ---
    @@ -465,6 +441,14 @@ public Executor getExecutor(){
         return context.getExecutor();
       }
     
    +  public long getFragmentMemoryLimit() {
    +    return allocator.getLimit();
    +  }
    +
    +  public void setFragmentMemoryLimit(long value) {
    --- End diff --
    
    getFragmentMemoryLimit and setFragmentMemoryLimit don't look like they are used anywhere. Let's just remove them.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---