[
https://issues.apache.org/jira/browse/HIVE-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715071#comment-13715071
]
Hive QA commented on HIVE-3725:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12593448/HIVE-3725.3.patch.txt
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 2647 tests executed
*Failed tests:*
{noformat}
org.apache.hcatalog.mapreduce.TestHCatInputFormat.testBadRecordHandlingPasses
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/124/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/124/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.CleanupPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
> Add support for pulling HBase columns with prefixes
> ---------------------------------------------------
>
> Key: HIVE-3725
> URL: https://issues.apache.org/jira/browse/HIVE-3725
> Project: Hive
> Issue Type: Improvement
> Components: HBase Handler
> Affects Versions: 0.9.0
> Reporter: Swarnim Kulkarni
> Assignee: Swarnim Kulkarni
> Attachments: HIVE-3725.1.patch.txt, HIVE-3725.2.patch.txt,
> HIVE-3725.3.patch.txt, HIVE-3725.patch.3.txt
>
>
> Current HBase Hive integration supports reading many values from the same row
> by specifying a column family. And specifying just the column family can pull
> in all qualifiers within the family.
> We should add in support to be able to specify a prefix for the qualifier and
> all columns that start with the prefix would automatically get pulled in. A
> wildcard support would be ideal.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
