Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 78DE1100AA for ; Mon, 9 Feb 2015 17:43:44 +0000 (UTC) Received: (qmail 16074 invoked by uid 500); 9 Feb 2015 17:43:42 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 16011 invoked by uid 500); 9 Feb 2015 17:43:42 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 15999 invoked by uid 99); 9 Feb 2015 17:43:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2015 17:43:42 +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 ian@flurry.com designates 209.85.216.51 as permitted sender) Received: from [209.85.216.51] (HELO mail-qa0-f51.google.com) (209.85.216.51) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2015 17:43:14 +0000 Received: by mail-qa0-f51.google.com with SMTP id i13so3709129qae.10 for ; Mon, 09 Feb 2015 09:41:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=aHrnH4R/n2SahKPqWr+2WEzlWlw80fedrtfH1TO4nbA=; b=dSeot2Fxxw7Sog4d4/mhXSSKyvufl5R/hO+wmKMiurWcU6OI1DfDKjDPwqpZs5Wl6y wAzOMSyJZhUkFf7CChhbKtlMuDc3E9cbsRA0CiZ4Xk/9KFxrrlKGhhStTXGzAVVSE7Lg QfdO+pcfY4BjnZzIm9nA45EyH9VyqbVllqPTet9GE0+HAiOFzWDxQTrC55XOewAseDS4 mt13I7kTu7E/lOD1dl2dyknPaQqA/ALDHuGnmWHc9SiksKf3yyrhVWsJVh65OAicdhLo iZWIFRbL8UJUD/O7htAVJZDgcdo46kxiG3OXajzdOvGCtufDR1SyhmB8lit8oKAhrMzE Y43A== X-Gm-Message-State: ALoCoQnQhJqsYaoFcUNOvrgHgAIAhebiiTGYlh0l9wbNz2x0fTFpXdI3EHQUSfjw5vkCo0Z02x2b X-Received: by 10.140.88.48 with SMTP id s45mr40835695qgd.28.1423503702644; Mon, 09 Feb 2015 09:41:42 -0800 (PST) Received: from unknown-10-75-114-x.yahoo.com (dip5.cfw-a-gci.nytimes.corp.yahoo.com. [209.131.52.149]) by mx.google.com with ESMTPSA id w107sm12496285qge.5.2015.02.09.09.41.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 09:41:41 -0800 (PST) From: Ian Friedman Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: filter serialization question Message-Id: <3D2EFF7E-C1C6-4C84-864E-7261F027633A@flurry.com> Date: Mon, 9 Feb 2015 12:41:40 -0500 To: user@hbase.apache.org Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) X-Virus-Checked: Checked by ClamAV on apache.org Hello! I'm in the process of upgrading our HBase 94 codebase to HBase = 98. The org.apache.hadoop.hbase.filter.Filter class now has a field=20 protected boolean reversed; which seems to, from my reading of the code = that touches it, be a transient field set only when the Scan using the = filter is itself reversed. It doesn't seem like it's supposed to be = serialized/deserialized with the rest of the filter. However it is not = marked transient, which trips up our serialization unittests... Is my = reading wrong and this field should get serialized (despite being = protected in a abstract base class) or should this field actually be = transient? Thanks in advance --Ian=