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 DD2F6D771 for ; Tue, 30 Oct 2012 23:27:03 +0000 (UTC) Received: (qmail 67719 invoked by uid 500); 30 Oct 2012 23:27:03 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 67688 invoked by uid 500); 30 Oct 2012 23:27:03 -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 67680 invoked by uid 99); 30 Oct 2012 23:27:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2012 23:27:03 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bimargulies@gmail.com designates 209.85.210.169 as permitted sender) Received: from [209.85.210.169] (HELO mail-ia0-f169.google.com) (209.85.210.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2012 23:26:56 +0000 Received: by mail-ia0-f169.google.com with SMTP id h37so740504iak.0 for ; Tue, 30 Oct 2012 16:26:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=TXspaei/0/VSmEmXK52zf8DS55+6FFGOeTXND0YXwIA=; b=Cyyyk+YtbSV06k4aI/oraksdJvRfopAsqfetOrqfhOC8OBlqlH6x72GruuPWSeFyJ2 FGp7MOOOf4/xtseKDCveB7e0+NIZJEAQbFroQuTKqB3UQGobj9bznBm9aNOAh7Li3maH +rOzf07PKsLZNHOlvcded7lf3JUFg+yIm/39z5gl6E+YBJ+0f1G4UFwWVcKCZN3XkLsF xcGHQ4v2AyXJkcOIOHlWswDAqToePVtvVoLFgIiE00eNZqPSWrbIxoll4Ts06TqsdMYp 1zeTN552hCoPPB/qs0fbGCMaqN43HwNtB0TtoIqplSY4L/io+pHUkhZvN57VSzq/kZXF 5stg== MIME-Version: 1.0 Received: by 10.50.214.65 with SMTP id ny1mr3127451igc.10.1351639595047; Tue, 30 Oct 2012 16:26:35 -0700 (PDT) Received: by 10.42.67.203 with HTTP; Tue, 30 Oct 2012 16:26:35 -0700 (PDT) In-Reply-To: References: <508EACFF.5000704@gmail.com> <508EB572.2020507@gmail.com> <508F236F.6070108@gmail.com> Date: Tue, 30 Oct 2012 19:26:35 -0400 Message-ID: Subject: Re: Setting Charset in getBytes() call. From: Benson Margulies To: dev@accumulo.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org UTF-8 allows any String to have to go into the database and get back out. Are there actually use cases in which some application code pushes in strings, and another pulls out bytes, and would be perturbed to find UTF-8 as opposed to some other encoding in the bytes?