[
https://issues.apache.org/jira/browse/DRILL-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233563#comment-15233563
]
Arina Ielchiieva commented on DRILL-4596:
-----------------------------------------
[Parth|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=parthc],
thanks for use case.
So implementation approach can be the following:
1. we allow to register any drillbit (disregarding the version) in zookeeper.
2. version compatibility will be guaranteed during release, changes in modules
(protobuf, rpc, etc) will influence main version number.
3. when issuing fragment, query to different drillbit, we will check if it's
main version is compatible with our drillibit (N + 1). For example, drillbit
with version 1.5 can work with 1.5 and 1.6. Drillbit with version 1.6 can work
with 1.6 and 1.7 and so on.
> 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)
