Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 50AC718144 for ; Thu, 18 Feb 2016 19:34:19 +0000 (UTC) Received: (qmail 21290 invoked by uid 500); 18 Feb 2016 19:34:18 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 21164 invoked by uid 500); 18 Feb 2016 19:34:18 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 20928 invoked by uid 99); 18 Feb 2016 19:34:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Feb 2016 19:34:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1DDA32C1F5C for ; Thu, 18 Feb 2016 19:34:18 +0000 (UTC) Date: Thu, 18 Feb 2016 19:34:18 +0000 (UTC) From: "Yuliya Feldman (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DRILL-4412) Have an array of DrillBitEndPoints (at least) for leaf fragments instead of single one MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DRILL-4412?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuliya Feldman updated DRILL-4412: ---------------------------------- Description: To follow up on the ability to submit simple physical plan= directly to a DrillBit for execution [DRILL-4132|https://issues.apache.org= /jira/browse/DRILL-4132] it would be beneficial to have an array of DrillBi= tEndPoint in PlanFragment. Leaf fragments that scan the data can have an ar= ray of DrillBitEndPoint based on data locality, as data may be replicated a= nd in case it is necessary to restart Scan fragment it can be restarted on = DrillBits that have replica of the data, versus always retrying the same Dr= illBit. (was: To follow up on the ability to submit simple physical plan d= irectly to a DrillBit for execution [JIRA-4132|https://issues.apache.org/ji= ra/browse/DRILL-4132] it would be beneficial to have an array of DrillBitEn= dPoint in PlanFragment. Leaf fragments that scan the data can have an array= of DrillBitEndPoint based on data locality, as data may be replicated and = in case it is necessary to restart Scan fragment it can be restarted on Dri= llBits that have replica of the data, versus always retrying the same Drill= Bit.) > Have an array of DrillBitEndPoints (at least) for leaf fragments instead = of single one > -------------------------------------------------------------------------= ------------- > > Key: DRILL-4412 > URL: https://issues.apache.org/jira/browse/DRILL-4412 > Project: Apache Drill > Issue Type: Improvement > Components: Query Planning & Optimization > Reporter: Yuliya Feldman > Assignee: Yuliya Feldman > > To follow up on the ability to submit simple physical plan directly to a = DrillBit for execution [DRILL-4132|https://issues.apache.org/jira/browse/DR= ILL-4132] it would be beneficial to have an array of DrillBitEndPoint in Pl= anFragment. Leaf fragments that scan the data can have an array of DrillBit= EndPoint based on data locality, as data may be replicated and in case it i= s necessary to restart Scan fragment it can be restarted on DrillBits that = have replica of the data, versus always retrying the same DrillBit. -- This message was sent by Atlassian JIRA (v6.3.4#6332)