[
https://issues.apache.org/jira/browse/CRUNCH-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262178#comment-14262178
]
Danny Morgan commented on CRUNCH-429:
-------------------------------------
Typically my source is just an "s3n://" path and the target is hdfs. I'm used
to the rest of the hadoop ecosystem which tries to figure out which filesystem
type to use based on the what's in the path name as opposed to the
configuration object.
You are right I can set fs.defaultFS and fs.default.name on the inputConf of
the source to get it to work. I guess it's more of an issue with "expected
behavior".
> The CSVFileSource does not always function properly
> ---------------------------------------------------
>
> Key: CRUNCH-429
> URL: https://issues.apache.org/jira/browse/CRUNCH-429
> Project: Crunch
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.3
> Reporter: mac champion
> Assignee: mac champion
> Priority: Minor
> Labels: csv, csvparser
> Fix For: 0.8.4, 0.11.0
>
> Attachments: 0001-CRUNCH-429-Fix-CSVInputFormat.patch,
> CRUNCH-429_a.patch
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> The "configure" method of CSVInputFormat does not have any effect on its
> configuration and is never called. Instead, the class needs to implement
> Configurable and set its configuration options in an overriden setConf
> method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
