You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/07/13 19:24:05 UTC
[jira] [Commented] (TAJO-1681) Fix TajoDump invalid null check for
database name
[ https://issues.apache.org/jira/browse/TAJO-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624981#comment-14624981 ]
ASF GitHub Bot commented on TAJO-1681:
--------------------------------------
GitHub user charsyam opened a pull request:
https://github.com/apache/tajo/pull/628
TAJO-1681 Fix TajoDump invalid null check for database name
isAcceptableDumpingDatabase return true even if databaseName is null
so it cause exception in dumpDatabase
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/charsyam/tajo feature/fix-bug-for-tajodump
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/628.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 #628
----
commit 6e7f2b319751ddeb0619648bba3f14c491978178
Author: clark.kang <cl...@kakao.com>
Date: 2015-07-13T17:21:28Z
fix invalid null check
----
> Fix TajoDump invalid null check for database name
> -------------------------------------------------
>
> Key: TAJO-1681
> URL: https://issues.apache.org/jira/browse/TAJO-1681
> Project: Tajo
> Issue Type: Bug
> Reporter: DaeMyung Kang
> Assignee: DaeMyung Kang
>
> TajoDump invalid null check in isAcceptableDumpingDatabase
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)