hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <>
Subject [jira] [Commented] (HIVE-16295) Add support for using Hadoop's S3A OutputCommitter
Date Tue, 24 Jul 2018 19:35:00 GMT


Steve Loughran commented on HIVE-16295:

w.r.t maven dependencies, if you are building against hadoop-3.x, the "hadoop-cloud-storage"
POM artifact will pull in all the cloud modules of the specific version of hadoop, while downgrading
the hadoop-common dependency to "provided". You'll inevitably have to exclude jackson versions
which will creep in somewhere, but its goal is a lower-maintenance way to to pull in cloud

> Add support for using Hadoop's S3A OutputCommitter
> --------------------------------------------------
>                 Key: HIVE-16295
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Sahil Takiar
>            Assignee: Sahil Takiar
>            Priority: Major
>         Attachments: HIVE-16295.1.WIP.patch, HIVE-16295.2.WIP.patch, HIVE-16295.3.WIP.patch,
HIVE-16295.4.patch, HIVE-16295.5.patch, HIVE-16295.6.patch, HIVE-16295.7.patch, HIVE-16295.8.patch,
> Hive doesn't have integration with Hadoop's {{OutputCommitter}}, it uses a {{NullOutputCommitter}}
and uses its own commit logic spread across {{FileSinkOperator}}, {{MoveTask}}, and {{Hive}}.
> The Hadoop community is building an {{OutputCommitter}} that integrates with S3Guard
and does a safe, coordinate commit of data on S3 inside individual tasks (HADOOP-13786). If
Hive can integrate with this new {{OutputCommitter}} there would be a lot of benefits to Hive-on-S3:
> * Data is only written once; directly committing data at a task level means no renames
are necessary
> * The commit is done safely, in a coordinated manner; duplicate tasks (from task retries
or speculative execution) should not step on each other

This message was sent by Atlassian JIRA

View raw message