[ 
https://issues.apache.org/jira/browse/PARQUET-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391699#comment-17391699
 ] 

Steve Loughran commented on PARQUET-1615:
-----------------------------------------

just looking at this. Any specific reason not to have overwrite the default?

it saves the overhead of an HTTP head probe against any of the object stores, 
and for any job where the  output committer has created a unique dir for that 
task attempt, no risk of conflict unless somehow the task really has decided to 
create two files with the same name.

Has anyone ever encountered conflicts?

> getRecordWriter shouldn't hardcode CREAT mode when new ParquetFileWriter
> ------------------------------------------------------------------------
>
>                 Key: PARQUET-1615
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1615
>             Project: Parquet
>          Issue Type: Bug
>          Components: parquet-mr
>    Affects Versions: 1.11.0
>            Reporter: Lantao Jin
>            Assignee: Lantao Jin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>
> getRecordWriter shouldn't hardcode CREAT mode when new ParquetFileWriter.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to