[
https://issues.apache.org/jira/browse/PHOENIX-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877286#comment-14877286
]
Hudson commented on PHOENIX-2239:
---------------------------------
FAILURE: Integrated in Phoenix-master #898 (See
[https://builds.apache.org/job/Phoenix-master/898/])
PHOENIX-2239 Improve strict mode in psql CSV load (greid: rev
886483728f0376dea748258348273b214382b535)
*
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/CsvToKeyValueMapper.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/CSVCommonsLoaderIT.java
* phoenix-core/src/main/java/org/apache/phoenix/util/CSVCommonsLoader.java
* phoenix-core/src/main/java/org/apache/phoenix/util/csv/CsvUpsertExecutor.java
*
phoenix-core/src/test/java/org/apache/phoenix/util/csv/CsvUpsertExecutorTest.java
> Honor strict option when catching data error during CSV load
> ------------------------------------------------------------
>
> Key: PHOENIX-2239
> URL: https://issues.apache.org/jira/browse/PHOENIX-2239
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Gabriel Reid
> Fix For: 4.6.0
>
> Attachments: PHOENIX-2239.patch, PHOENIX-2239b.patch
>
>
> The Phoenix CSV Bulk Loader has a strict option (i.e. -s or --strict) which
> is intended to abort the load if a data error is found. Looks like we're not
> passing this option through the errorOnRecord method, but I think that'd be a
> good (and likely pretty easy) improvement:
> {code}
> @Override
> public void errorOnRecord(CSVRecord csvRecord, String errorMessage) {
> LOG.error("Error upserting record {}: {}", csvRecord,
> errorMessage);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)