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

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

Github user paul-rogers commented on a diff in the pull request:

    https://github.com/apache/drill/pull/482#discussion_r86565724
  
    --- Diff: 
exec/java-exec/src/main/java/org/apache/drill/exec/coord/zk/ZKClusterCoordinator.java
 ---
    @@ -252,6 +252,8 @@ public DrillbitEndpoint 
apply(ServiceInstance<DrillbitEndpoint> input) {
               builder.append(bit.getControlPort());
               builder.append(':');
               builder.append(bit.getDataPort());
    +          builder.append(". Version - ");
    +          builder.append(bit.getVersion());
    --- End diff --
    
    Now that we have many fields, would this be better displayed as a table 
with columns for each field?
    
    Host | User Port | Control Port | Data Port | Version | ...
    
    In this form we could also show the HTTP port and the port (forgot the 
name) whose value is computed rather than configured. Eventually, we can also 
show Drillbit status, etc.


> Generate warning on Web UI if drillbits version mismatch is detected
> --------------------------------------------------------------------
>
>                 Key: DRILL-4604
>                 URL: https://issues.apache.org/jira/browse/DRILL-4604
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.6.0
>            Reporter: Arina Ielchiieva
>            Assignee: Sudheesh Katkam
>              Labels: doc-impacting
>             Fix For: Future
>
>         Attachments: index_page.JPG, index_page_mismatch.JPG, 
> screenshots_with_different_states.docx
>
>
> Display drillbit version on web UI. If any of drillbits version doesn't match 
> with current drillbit, generate warning.
> Screenshots - screenshots_with_different_states.docx.



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

Reply via email to