Return-Path: 
 <user-return-3970-apmail-accumulo-user-archive=accumulo.apache.org@accumulo.apache.org>
X-Original-To: apmail-accumulo-user-archive@www.apache.org
Delivered-To: apmail-accumulo-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9453510B95
	for <apmail-accumulo-user-archive@www.apache.org>;
 Fri, 21 Mar 2014 14:31:11 +0000 (UTC)
Received: (qmail 97569 invoked by uid 500); 21 Mar 2014 14:31:10 -0000
Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org
Received: (qmail 97491 invoked by uid 500); 21 Mar 2014 14:31:09 -0000
Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@accumulo.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@accumulo.apache.org>
List-Post: <mailto:user@accumulo.apache.org>
List-Id: <user.accumulo.apache.org>
Reply-To: user@accumulo.apache.org
Delivered-To: mailing list user@accumulo.apache.org
Received: (qmail 97480 invoked by uid 99); 21 Mar 2014 14:31:08 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Mar 2014 14:31:08 +0000
X-ASF-Spam-Status: No, hits=2.8 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of david.medinets@gmail.com
 designates 209.85.216.179 as permitted sender)
Received: from [209.85.216.179] (HELO mail-qc0-f179.google.com)
 (209.85.216.179)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Mar 2014 14:31:03 +0000
Received: by mail-qc0-f179.google.com with SMTP id m20so2803459qcx.24
        for <user@accumulo.apache.org>; Fri, 21 Mar 2014 07:30:41 -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=tF2ERtHtyA4MipXJdG6FFiPt+VJ3PwkOgVGRx6CAk6Q=;
        b=SfVgJ5l4ooiaFcb9LNdid8q7w7QWYhPSb8y5f9TfI6IV65FS/23inTFn4zlgwJ3rvX
         /jKIgVgiU7JyCX4IcJyJwQyuwmkCEsYZsFfpgi3+2Mu8EF9Trp9Gief/Tuu9kYvgHLan
         z3XvbuQLxFDdvxqR/dG9cRErTNxiF1sspT8z3w3fpN0WwIB+DqcrQI6Rc6ifYg7fGJ3X
         xJ2h3qbLUYGKOsYNi+vDmpyo8+45NwXldwOdkNCnUOesZ3LS/ViLUaaaIDLrCzO+CVor
         eZRvqcQSx/q1P4bZEYdVXn8h8kpgMYqr7EeqgzxefTA9zq9C8JTIdlZ735aMIY6zZaoz
         u1gw==
MIME-Version: 1.0
X-Received: by 10.224.89.71 with SMTP id d7mr57590733qam.54.1395412241732;
 Fri, 21 Mar 2014 07:30:41 -0700 (PDT)
Received: by 10.96.64.161 with HTTP; Fri, 21 Mar 2014 07:30:41 -0700 (PDT)
In-Reply-To: <1395410179795-8350.post@n5.nabble.com>
References: <1394052507311-7949.post@n5.nabble.com>
	<1395410179795-8350.post@n5.nabble.com>
Date: Fri, 21 Mar 2014 10:30:41 -0400
Message-ID: 
 <CAOiJXP7+SsQX_j183=dX4srPhTgCCj=f4gY0YfEhik_gtF-Rhg@mail.gmail.com>
Subject: Re: "NOT" operator in visibility string
From: David Medinets <david.medinets@gmail.com>
To: accumulo-user <user@accumulo.apache.org>
Content-Type: multipart/alternative; boundary=001a11c3e166fbd9e604f51eba7a
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c3e166fbd9e604f51eba7a
Content-Type: text/plain; charset=ISO-8859-1

This conversation seems more suited to accumulo-developer, perhaps. Does it
matter?


On Fri, Mar 21, 2014 at 9:56 AM, joeferner <joe.m.ferner@gmail.com> wrote:

> If I were to submit a patch to allow the visibility system to be plug-gable
> would that be accepted? Or would it be better to have a configurable option
> to just enable/disable the NOT operator?
>
>
>
> --
> View this message in context:
> http://apache-accumulo.1065345.n5.nabble.com/NOT-operator-in-visibility-string-tp7949p8350.html
> Sent from the Users mailing list archive at Nabble.com.
>

--001a11c3e166fbd9e604f51eba7a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This conversation seems more suited to accumulo-devel=
oper, perhaps. Does it matter?<br></div></div><div class=3D"gmail_extra"><b=
r><br><div class=3D"gmail_quote">On Fri, Mar 21, 2014 at 9:56 AM, joeferner=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:joe.m.ferner@gmail.com" target=3D"=
_blank">joe.m.ferner@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">If I were to submit a patch to allow the vis=
ibility system to be plug-gable<br>
would that be accepted? Or would it be better to have a configurable option=
<br>
to just enable/disable the NOT operator?<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-accumulo.1065345.n5.=
nabble.com/NOT-operator-in-visibility-string-tp7949p8350.html" target=3D"_b=
lank">http://apache-accumulo.1065345.n5.nabble.com/NOT-operator-in-visibili=
ty-string-tp7949p8350.html</a><br>

Sent from the Users mailing list archive at Nabble.com.<br>
</blockquote></div><br></div>

--001a11c3e166fbd9e604f51eba7a--