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 6945C200C53 for ; Tue, 11 Apr 2017 15:12:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 67B45160B9E; Tue, 11 Apr 2017 13:12:46 +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 AE90A160B89 for ; Tue, 11 Apr 2017 15:12:45 +0200 (CEST) Received: (qmail 49402 invoked by uid 500); 11 Apr 2017 13:12:44 -0000 Mailing-List: contact issues-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 issues@ignite.apache.org Received: (qmail 49393 invoked by uid 99); 11 Apr 2017 13:12:44 -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; Tue, 11 Apr 2017 13:12:44 +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 7F67C1A7A56 for ; Tue, 11 Apr 2017 13:12:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 1enQAieAVbr9 for ; Tue, 11 Apr 2017 13:12:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 9291561A58 for ; Tue, 11 Apr 2017 13:12:43 +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 AFF73E0D5E for ; Tue, 11 Apr 2017 13:12:42 +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 DF19524077 for ; Tue, 11 Apr 2017 13:12:41 +0000 (UTC) Date: Tue, 11 Apr 2017 13:12:41 +0000 (UTC) From: "Sergi Vladykin (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-4523) Allow distributed SQL query execution over explicit set of partitions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 11 Apr 2017 13:12:46 -0000 [ https://issues.apache.org/jira/browse/IGNITE-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964344#comment-15964344 ] Sergi Vladykin commented on IGNITE-4523: ---------------------------------------- I reviewed the patch, my comments are in Upsource. > Allow distributed SQL query execution over explicit set of partitions > --------------------------------------------------------------------- > > Key: IGNITE-4523 > URL: https://issues.apache.org/jira/browse/IGNITE-4523 > Project: Ignite > Issue Type: Improvement > Components: cache, SQL > Affects Versions: 1.8 > Reporter: Alexei Scherbakov > Assignee: Alexei Scherbakov > Labels: important > Fix For: 2.0 > > > 3Currently distributed SQL query is executed on all nodes containing primary partitions for a cache, sending map query requests on all nodes in grid. > Sometimes we know in advance which partitions hold a data for query, on example, in case of custom affinity function. > Therefore it's possible to reduce number of nodes receiving map query request by providing explicit set of partitions, which will give significant performance advantage and traffic reduction in case of very large clusters. > Internally we already have such functionality, so the only necessary thing is to provide public API for what. -- This message was sent by Atlassian JIRA (v6.3.15#6346)