Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7E1DE200CA3 for ; Thu, 1 Jun 2017 13:48:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7CC5D160BB5; Thu, 1 Jun 2017 11:48:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BE865160BC4 for ; Thu, 1 Jun 2017 13:48:07 +0200 (CEST) Received: (qmail 44007 invoked by uid 500); 1 Jun 2017 11:48:06 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 43996 invoked by uid 99); 1 Jun 2017 11:48:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Jun 2017 11:48:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 90F181A7A94 for ; Thu, 1 Jun 2017 11:48:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id ATNpFid1R_dA for ; Thu, 1 Jun 2017 11:48:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3EA245F2AE for ; Thu, 1 Jun 2017 11:48:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 76269E0C0D for ; Thu, 1 Jun 2017 11:48:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3136621B59 for ; Thu, 1 Jun 2017 11:48:04 +0000 (UTC) Date: Thu, 1 Jun 2017 11:48:04 +0000 (UTC) From: "Vladimir Ozerov (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-5383) Do not perform cache key validation when BinaryMarshaller is used MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 01 Jun 2017 11:48:08 -0000 Vladimir Ozerov created IGNITE-5383: --------------------------------------- Summary: Do not perform cache key validation when BinaryMarshaller is used Key: IGNITE-5383 URL: https://issues.apache.org/jira/browse/IGNITE-5383 Project: Ignite Issue Type: Task Components: binary, cache Affects Versions: 2.1 Reporter: Vladimir Ozerov Fix For: 2.2 Currently whenever cache operation is performed, we invoke {{GridCacheAdapter.validateCacheKey}} to make sure that key overrides {{equals}} and {{hashCode}}. This check should not be performed when {{BinaryMarshaller}} is set, since we do not use these methods in binary mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)