[
https://issues.apache.org/jira/browse/PHOENIX-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544598#comment-17544598
]
ASF GitHub Bot commented on PHOENIX-6721:
-----------------------------------------
ss77892 opened a new pull request, #1450:
URL: https://github.com/apache/phoenix/pull/1450
…output points to the S3 location
The problem is that in our code we explicitly set the output committer to
FileOutputCommitter which doesn't work well with the S3. HBase had a similar
problem covered by HBASE-18885. I've tried to duplicate the approach used
there, but it comes that S3 committer doesn't extend FileOuputCommitter, so I
have to use the base class for both of those - PathOutputCommitter and use
getOutputPath instead of getWorkPath. It works in my manual tests with and
without AWS use.
> CSV bulkload tool fails with FileNotFoundException if --output points to the
> S3 location
> ----------------------------------------------------------------------------------------
>
> Key: PHOENIX-6721
> URL: https://issues.apache.org/jira/browse/PHOENIX-6721
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Reporter: Sergey Soldatov
> Assignee: Sergey Soldatov
> Priority: Major
>
> We were trying to use CSV bulkload tool with the HBase/Phoenix running on top
> of AWS S3 and found that once we use --output params pointing to S3, the job
> fails with FNFE
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
