[
https://issues.apache.org/jira/browse/PHOENIX-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600304#comment-14600304
]
Hudson commented on PHOENIX-2030:
---------------------------------
FAILURE: Integrated in Phoenix-master #795 (See
[https://builds.apache.org/job/Phoenix-master/795/])
PHOENIX-2030 CsvBulkLoadTool should use logical name of the table for output
directory suffix(Rajeshbabu) (rajeshbabu: rev
3cf22a7de4eaec6978763b6961d73aa9eaa07015)
* phoenix-core/src/it/java/org/apache/phoenix/mapreduce/CsvBulkLoadToolIT.java
* phoenix-core/src/main/java/org/apache/phoenix/mapreduce/CsvBulkLoadTool.java
> CsvBulkLoadTool should use logical name of the table for output directory
> suffix
> --------------------------------------------------------------------------------
>
> Key: PHOENIX-2030
> URL: https://issues.apache.org/jira/browse/PHOENIX-2030
> Project: Phoenix
> Issue Type: Bug
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Fix For: 5.0.0, 4.5.0, 4.4.1
>
> Attachments: PHOENIX-2030.patch
>
>
> Currently the CsvBulkLoad tool loads the data parrallely to data and index
> tables. If a table has multiple local indexes then the output directory for
> the indexes data is will be same and then one thread might delete when it's
> job done and then other index data loading fail with FileNotFoundException.
> To avoid this we should use logical name as suffix output directory which is
> unique for data table and index tables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)