[
https://issues.apache.org/jira/browse/HIVE-23085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068349#comment-17068349
]
Hive QA commented on HIVE-23085:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12997892/HIVE-23085.01.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 18143 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/21291/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/21291/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-21291/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12997892 - PreCommit-HIVE-Build
> LLAP: Support Multiple NVMe-SSD disk Locations While Using SSD Cache
> --------------------------------------------------------------------
>
> Key: HIVE-23085
> URL: https://issues.apache.org/jira/browse/HIVE-23085
> Project: Hive
> Issue Type: Improvement
> Reporter: Syed Shameerur Rahman
> Assignee: Syed Shameerur Rahman
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-23085.01.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we can configure only one SSD location while using SSD cache in
> LLAP. This highly undermines the capacity of some machines to use its disk
> capacity to the fullest. For example *AWS* provides *r5d.4x large* series
> which comes with *2 * 300 GB NVme SSD disk* with the current design only one
> of the mounted *NVme SSD* disk can be used for caching. Hence adding support
> for caching data at multiple ssd mounted locations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
