crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mac champion (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-565) CSVInputFormat needs to be more defensive when configuring itself
Date Thu, 01 Oct 2015 14:55:27 GMT


mac champion commented on CRUNCH-565:

Well, at first I started using it just because that's what I'm comfortable with. But later
I realized i wasn't completely certain how to manipulate it into returning null instead of
blank strings. With Mockito that's easy, just don't mock anything and the return value will
be null.

BUT, If I switch all of these to get(opt,default) I will have to do some extra stuff, but
I shouldn't have to handle nulls or do anything weird like that. Can you take another look

Also, sorry about the pull request to apache/crunch. I've forked that and I use it play around
and create pull requests so I can have a nice place to review and comment on the diffs. When
the code looks good and it builds, I'll create a patch and attach it to the JIRA. Is that
an okay workflow? The official one is pretty sparse and doesn't include any kind of review

> CSVInputFormat needs to be more defensive when configuring itself
> -----------------------------------------------------------------
>                 Key: CRUNCH-565
>                 URL:
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.10.0, 0.8.3
>            Reporter: mac champion
>            Assignee: mac champion
>            Priority: Minor
>              Labels: csv, csvparser
> It seems that some behavior has changed somewhere along the line where hadoop Configuration
is concerned. It is possible that a call to .get(OPTION) will return null. CSVInputFormat
does not handle that case gracefully:
> Some more relevant details can be found in this JIRA:

This message was sent by Atlassian JIRA

View raw message