You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Sahil Takiar (JIRA)" <ji...@apache.org> on 2018/11/07 18:07:00 UTC

[jira] [Resolved] (IMPALA-6249) Expose several build flags via web UI

     [ https://issues.apache.org/jira/browse/IMPALA-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sahil Takiar resolved IMPALA-6249.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0

> Expose several build flags via web UI
> -------------------------------------
>
>                 Key: IMPALA-6249
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6249
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>            Reporter: Tim Armstrong
>            Assignee: Sahil Takiar
>            Priority: Minor
>             Fix For: Impala 3.1.0
>
>         Attachments: Screen Shot 2018-09-06 at 11.47.45 AM.png
>
>
> IMPALA-6241 added a .cmake_build_type file with the CMAKE_BUILD_TYPE value for the last build. The file is used to detect the type of the build that the python tests are running against. However, this assumes that the tests are running from the same directory that the Impala cluster under test was built from, which isn't necessarily true for all dev workflows and for remote cluster tests.
> It would be convenient if CMAKE_BUILD_TYPE was exposed from the Impalad web UI. Currently we expose DEBUG/RELEASE depending on the value of NDEBUG - see GetVersionString() and impalad-host:25000/?json=true, but we could expose the precise build type, then allow the python tests to parse it from the web UI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)