[
https://issues.apache.org/jira/browse/TAJO-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958550#comment-14958550
]
Tajo QA commented on TAJO-1891:
-------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12766744/TAJO-1891.patch
against master revision release-0.9.0-rc0-535-g54bf516.
{color:green}+1 @author.{color} The patch does not contain any @author
tags.
{color:green}+1 tests included.{color} The patch appears to include 12 new
or modified test files.
{color:green}+1 javac.{color} The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc.{color} The applied patch does not increase the
total number of javadoc warnings.
{color:green}+1 checkstyle.{color} The patch generated 0 code style errors.
{color:red}-1 findbugs.{color} The patch appears to cause Findbugs
(version 2.0.3) to fail.
{color:green}+1 release audit.{color} The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests.{color} The patch passed unit tests in
tajo-catalog/tajo-catalog-drivers/tajo-hive tajo-catalog/tajo-catalog-server
tajo-cli tajo-core tajo-core-tests tajo-jdbc tajo-plan.
Test results:
https://builds.apache.org/job/PreCommit-TAJO-Build/885//testReport/
Findbugs results:
https://builds.apache.org/job/PreCommit-TAJO-Build/885//findbugsResult
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/885//console
This message is automatically generated.
> Allow arbitrary partition path
> ------------------------------
>
> Key: TAJO-1891
> URL: https://issues.apache.org/jira/browse/TAJO-1891
> Project: Tajo
> Issue Type: Sub-task
> Components: Physical Operator, Planner/Optimizer
> Affects Versions: 0.12.0
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Fix For: 0.12.0, 0.11.1
>
> Attachments: TAJO-1891.patch
>
>
> Currently, Tajo just allow well-defined partition path which includes all
> partition columns because rewriter builds basic tuple for scanning data files
> using partition path. So, if users data already exist on arbitrary partition
> path, they should move their partitions to other directories. It seems a very
> inefficient way and we need to allow arbitrary partition path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
