Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 347EAF381 for ; Mon, 28 Apr 2014 14:50:22 +0000 (UTC) Received: (qmail 16089 invoked by uid 500); 28 Apr 2014 14:50:19 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 15947 invoked by uid 500); 28 Apr 2014 14:50:18 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 15851 invoked by uid 99); 28 Apr 2014 14:50:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Apr 2014 14:50:16 +0000 Date: Mon, 28 Apr 2014 14:50:16 +0000 (UTC) From: "Mike Drob (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1581) Limit length of values printed in listscans by default 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-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983054#comment-13983054 ] Mike Drob commented on ACCUMULO-1581: ------------------------------------- [~mridley], [~elserj] - I'm not sure the issue is that simple. Consider ACCUMULO-816. > Limit length of values printed in listscans by default > ------------------------------------------------------ > > Key: ACCUMULO-1581 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1581 > Project: Accumulo > Issue Type: Improvement > Components: shell > Reporter: Josh Elser > Labels: newbie > Fix For: 1.7.0 > > > Listscans currently print out the entire options map provided to a ScanSession. If these large option values are printed, it makes the output rather difficult to read/parse. > We should add an upper limit to the length of the key-values printed out from said option map, including a "" to match what is done for large Keys when scanning a table. We could also add an option to override the truncation for when people really want to see the complete option map. -- This message was sent by Atlassian JIRA (v6.2#6252)