[
https://issues.apache.org/jira/browse/HIVE-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011543#comment-16011543
]
Hive QA commented on HIVE-16663:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12868181/HIVE-16663.5.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 10717 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[materialized_view_create_rewrite]
(batchId=236)
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[table_nonprintable]
(batchId=140)
org.apache.hive.beeline.TestTableOutputFormat.testPrint (batchId=174)
org.apache.hive.hcatalog.pig.TestTextFileHCatStorer.testDateCharTypes
(batchId=179)
org.apache.hive.hcatalog.pig.TestTextFileHCatStorer.testWriteTimestamp
(batchId=179)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/5269/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/5269/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-5269/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 5 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12868181 - PreCommit-HIVE-Build
> String Caching For Rows
> -----------------------
>
> Key: HIVE-16663
> URL: https://issues.apache.org/jira/browse/HIVE-16663
> Project: Hive
> Issue Type: Improvement
> Components: Beeline
> Affects Versions: 2.0.1
> Reporter: BELUGA BEHR
> Priority: Minor
> Attachments: HIVE-16663.1.patch, HIVE-16663.2.patch,
> HIVE-16663.3.patch, HIVE-16663.4.patch, HIVE-16663.5.patch
>
>
> It is very common that there are many repeated values in the result set of a
> query. As it currently stands, beeline does not attempt to cache any of
> these values and therefore it consumes a lot of memory.
> Adding a string cache may save a lot of memory. There are organizations that
> use beeline to perform ETL processing of result sets into CSV. This will
> better support those organizations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
