Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D9D0BCEFE for ; Mon, 4 Jun 2012 22:03:23 +0000 (UTC) Received: (qmail 55308 invoked by uid 500); 4 Jun 2012 22:03:23 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 55266 invoked by uid 500); 4 Jun 2012 22:03:23 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 55243 invoked by uid 99); 4 Jun 2012 22:03:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2012 22:03:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 28F2E1402B8 for ; Mon, 4 Jun 2012 22:03:23 +0000 (UTC) Date: Mon, 4 Jun 2012 22:03:22 +0000 (UTC) From: "Keith Turner (JIRA)" To: dev@accumulo.apache.org Message-ID: <1532629151.36427.1338847403169.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1232360791.36116.1338842423426.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Work started] (ACCUMULO-616) Table setting table.scan.max.memory ignored MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ACCUMULO-616 started by Keith Turner. > Table setting table.scan.max.memory ignored > ------------------------------------------- > > Key: ACCUMULO-616 > URL: https://issues.apache.org/jira/browse/ACCUMULO-616 > Project: Accumulo > Issue Type: Bug > Components: tserver > Affects Versions: 1.4.0, 1.3.5 > Reporter: Keith Turner > Assignee: Keith Turner > Fix For: 1.5.0 > > > When the setting table.scan.max.memory is set at the table level its ignored by the batch scanner. The setting is always read from the system level configuration. It should be read from the table level configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira