[ 
https://issues.apache.org/jira/browse/PARQUET-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gabor Szadovszky updated PARQUET-431:
-------------------------------------
    Fix Version/s: 1.8.2

> Make ParquetOutputFormat.memoryManager volatile
> -----------------------------------------------
>
>                 Key: PARQUET-431
>                 URL: https://issues.apache.org/jira/browse/PARQUET-431
>             Project: Parquet
>          Issue Type: Bug
>          Components: parquet-mr
>    Affects Versions: 1.8.0, 1.8.1
>            Reporter: Liwei Lin(Inactive)
>            Assignee: Liwei Lin(Inactive)
>            Priority: Major
>             Fix For: 1.9.0, 1.8.2
>
>
> Currently ParquetOutputFormat.getRecordWriter() contains an unsynchronized 
> lazy initialization of the non-volatile static field *memoryManager*.
> Because the compiler or processor may reorder instructions, threads are not 
> guaranteed to see a completely initialized object, when 
> ParquetOutputFormat.getRecordWriter() is called by multiple threads.
> This ticket proposes to make *memoryManager* volatile to correct the problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to