[
https://issues.apache.org/jira/browse/HIVE-26758?focusedWorklogId=831141&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-831141
]
ASF GitHub Bot logged work on HIVE-26758:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Dec/22 18:21
Start Date: 05/Dec/22 18:21
Worklog Time Spent: 10m
Work Description: yigress commented on PR #3781:
URL: https://github.com/apache/hive/pull/3781#issuecomment-1337898840
close this one and to create a new PR due to testing issue
https://issues.apache.org/jira/browse/HIVE-26806
Issue Time Tracking
-------------------
Worklog Id: (was: 831141)
Time Spent: 2h 50m (was: 2h 40m)
> Allow use scratchdir for staging final job
> ------------------------------------------
>
> Key: HIVE-26758
> URL: https://issues.apache.org/jira/browse/HIVE-26758
> Project: Hive
> Issue Type: New Feature
> Components: Query Planning
> Affects Versions: 4.0.0-alpha-2
> Reporter: Yi Zhang
> Assignee: Yi Zhang
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> The query results are staged in stagingdir that is relative to the
> destination path <destination_dir>/<staging_dir>/
> during blobstorage optimzation HIVE-17620 final job is set to use stagingdir.
> HIVE-15215 mentioned the possibility of using scratch for staging when write
> to S3 but it was long time ago and no activity.
>
> This is to allow final job to use hive.exec.scratchdir as the interim jobs,
> with a configuration
> hive.use.scratchdir.for.staging
> This is useful for cross Filesystem, user can use local source filesystem
> instead of remote filesystem for the staging.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
