[
https://issues.apache.org/jira/browse/DRILL-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235952#comment-15235952
]
ASF GitHub Bot commented on DRILL-4596:
---------------------------------------
Github user yufeldman commented on the pull request:
https://github.com/apache/drill/pull/474#issuecomment-208554692
Not sure how that comment contradicts with what I said. Adding new feature
in the next version should not break previous version.
> On Apr 11, 2016, at 12:41 PM, arina-ielchiieva <notificati...@github.com>
wrote:
>
> I thought it's hard to maintain backward compatibility. Quoting Parth
comment from Jira:
> "Drill needs to be able to run queries that depend only on features that
are in the oldest version of Drill in the cluster. Say for example, most
drillbits are at version N and some are at version N+1. You added support for a
new type foo in version N+1. Any queries not using or depending on type foo
should run successfully. Queries depending on foo can only run successfully
after all the drillbits are upgraded to N+1."
>
> —
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub
>
> 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)
