Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 12 Apr 2016 20:04:25 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12957180.1460112641000.210095.1460491465476@Atlassian.JIRA>
In-Reply-To: <JIRA.12957180.1460112641000@Atlassian.JIRA>
References: <JIRA.12957180.1460112641000@Atlassian.JIRA>
 <JIRA.12957180.1460112641036@arcas>
Subject: [jira] [Commented] (DRILL-4596) Drill should do version check among
 drillbits
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DRILL-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237875#comment-15237875 ] 

ASF GitHub Bot commented on DRILL-4596:
---------------------------------------

Github user jacques-n commented on the pull request:

    https://github.com/apache/drill/pull/474#issuecomment-209081311
  
    In general, I'm against version number checking. We did that in the code early on but we should be moving towards a capabilities flag approach.
    
    Also agree with Paul in his mention of DRILL-4286, don't think worrying about rolling upgrade makes sense until we resolve the issues around decommissioning.


> Drill should do version check among drillbits
> ---------------------------------------------
>
>                 Key: DRILL-4596
>                 URL: https://issues.apache.org/jira/browse/DRILL-4596
>             Project: Apache Drill
>          Issue Type: New Feature
>    Affects Versions: 1.6.0
>            Reporter: Arina Ielchiieva
>            Assignee: Arina Ielchiieva
>             Fix For: Future
>
>
> Before registering new drillbit in zookeeper, we should do version check, and make sure all the running drillbits are in the same version.
> Using drillbits of different version can lead to unexpected results.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)