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 EE810110AE for ; Tue, 22 Apr 2014 18:42:17 +0000 (UTC) Received: (qmail 49586 invoked by uid 500); 22 Apr 2014 18:42:16 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 49519 invoked by uid 500); 22 Apr 2014 18:42:15 -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 49505 invoked by uid 99); 22 Apr 2014 18:42:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2014 18:42:15 +0000 Date: Tue, 22 Apr 2014 18:42:15 +0000 (UTC) From: "Mike Drob (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-743) Authorization constructors are pretty wonky - String research? 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-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated ACCUMULO-743: ------------------------------- Issue Type: Sub-task (was: Improvement) Parent: ACCUMULO-2589 > Authorization constructors are pretty wonky - String research? > -------------------------------------------------------------- > > Key: ACCUMULO-743 > URL: https://issues.apache.org/jira/browse/ACCUMULO-743 > Project: Accumulo > Issue Type: Sub-task > Components: client > Reporter: John Vines > > The various constructors for Authorizations are somewhat all over the place. There is only one which uses Strings (most convenient for the user) but it only accepts them via variable args. > The rest are in some form of bytes. One is a comma seperated byte array, one is a List of ByteBuffers, and then there is another which is a Collection of byte[]. > We make extensive use of bytes instead of Strings due to encoding concerns. I would like to see a bit more consistency in the constructors for Authorizations. Because right now we sort of have a half assed approach of being safe by using Bytes, but then having Strings (as var args) for usability. I think we need to come up with a definite yes or no on Strings, and then provide appropriate methods for dealing with them. -- This message was sent by Atlassian JIRA (v6.2#6252)