[
https://issues.apache.org/jira/browse/DRILL-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15810939#comment-15810939
]
Kunal Khatua commented on DRILL-5174:
-------------------------------------
It might make sense to project a warning within SQLLine than throw an error.
I believe the UI too shows an warning, but allows you to query the cluster.
The cluster should be usable still, though there might be cases where behaviour
is unpredictable if a specific feature is supported on a part of such a
heterogeneous cluster.
> when different Drillbit versions are up on a cluster - we need to report an
> error
> ---------------------------------------------------------------------------------
>
> Key: DRILL-5174
> URL: https://issues.apache.org/jira/browse/DRILL-5174
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Affects Versions: 1.10.0
> Reporter: Khurram Faraaz
>
> Drill 1.10.0 git commit : bbcf4b76
> Note that one of the nodes in the 4 node cluster had a Drillbit from 1.9.0
> and the other three Drillbits are of 1.10.0 version. We report an error on
> the Web UI (see DRILL-4604) for such a scenario, we need a similar message
> when querying sys.drillbits table from sqlline.
> {noformat}
> 0: jdbc:drill:schema=dfs.tmp> select * from sys.drillbits;
> +-------------------+------------+---------------+------------+----------+------------------+
> | hostname | user_port | control_port | data_port | current |
> version |
> +-------------------+------------+---------------+------------+----------+------------------+
> | centos-03.qa.lab | 31010 | 31011 | 31012 | false |
> 1.10.0-SNAPSHOT |
> | centos-02.qa.lab | 31010 | 31011 | 31012 | false |
> |
> | centos-04.qa.lab | 31010 | 31011 | 31012 | false |
> 1.10.0-SNAPSHOT |
> | centos-01.qa.lab | 31010 | 31011 | 31012 | true |
> 1.10.0-SNAPSHOT |
> +-------------------+------------+---------------+------------+----------+------------------+
> 4 rows selected (0.285 seconds)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
