[
https://issues.apache.org/jira/browse/DRILL-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232774#comment-15232774
]
Arina Ielchiieva commented on DRILL-4596:
-----------------------------------------
[Parth|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=parthc],
I can't think of use case when customer would like to have drillbits with
different versions.
If we want to test out new drillibit version, we can just simply set different
cluster-id.
Though, I agree that it makes sense to check each module for version
compatibility. Let's say, compare each module major version only.
Does it sound reasonable?
> 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)
