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

ASF GitHub Bot commented on TAJO-1132:
--------------------------------------

GitHub user hyunsik opened a pull request:

    https://github.com/apache/tajo/pull/211

    TAJO-1132: More detailed version info in tsql.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hyunsik/tajo TAJO-1132

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tajo/pull/211.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #211
    
----
commit 8331b6001ca2b597f345f84d2bb4ea84748e2ba0
Author: Hyunsik Choi <[email protected]>
Date:   2014-10-25T19:52:20Z

    TAJO-1132: More detailed version info in tsql.

----


> More detailed version info in tsql
> ----------------------------------
>
>                 Key: TAJO-1132
>                 URL: https://issues.apache.org/jira/browse/TAJO-1132
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>            Priority: Trivial
>             Fix For: 0.9.1
>
>
> Currently, the displayed version information in tsql and WEB BI contains only 
> version number. For easier debugging, we need more information including a 
> git revision and a source checksum of compiled source and a compiled user.
> If we get the information from a user who has some problems, we can find out 
> more things than now.
> This patch changes the display version information as follows:
> before
> {noformat}
> default> \version
> 0.9.1-SNAPSHOT
> {noformat}
> after patch
> {noformat}
> default> \version
> Tajo 0.9.1-SNAPSHOT (rev. 3c3bcce source checksum d8e7ddb compiled by hyunsik 
> 2014-10-25T19:48Z)
> {noformat}



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

Reply via email to