-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE in VersionedTap.sourceConfInit #39
Comments
Are you using a relative path?
Sam Ritchie, Twitter Inc |
This ended up being a false alarm. However, there is still an issue with NPEs not being the most useful error message. I will send a pull request to add better logging. |
What is the real issue at play here?
Sam Ritchie, Twitter Inc |
I was trying to read and write from the same, uninitialized source. |
Ooooooooooooh
Sam Ritchie, Twitter Inc |
Addressed by #40 |
When I create a new versioned tap (using VersionedKeyValSource from Scalding) I get an NPE:
Caused by: java.lang.NullPointerException
at org.apache.hadoop.mapred.FileInputFormat.getPathStrings(FileInputFormat.java:342)
at org.apache.hadoop.mapred.FileInputFormat.setInputPaths(FileInputFormat.java:288)
at com.backtype.cascading.tap.VersionedTap.sourceConfInit(VersionedTap.java:88)
at com.backtype.cascading.tap.VersionedTap.sourceConfInit(VersionedTap.java:19)
at cascading.flow.hadoop.HadoopFlowStep.initFromSources(HadoopFlowStep.java:332)
at cascading.flow.hadoop.HadoopFlowStep.getInitializedConfig(HadoopFlowStep.java:99)
at cascading.flow.hadoop.HadoopFlowStep.createFlowStepJob(HadoopFlowStep.java:201)
at cascading.flow.hadoop.HadoopFlowStep.createFlowStepJob(HadoopFlowStep.java:69)
at cascading.flow.planner.BaseFlowStep.getFlowStepJob(BaseFlowStep.java:680)
at cascading.flow.BaseFlow.initializeNewJobsMap(BaseFlow.java:1148)
at cascading.flow.BaseFlow.initialize(BaseFlow.java:198)
at cascading.flow.hadoop.planner.HadoopPlanner.buildFlow(HadoopPlanner.java:231)
I can avoid the NPE by doing:
$ hdfs -mkdir /user/foo/1
$ touch 1.version
$ hdfs -copyFromLocal 1.version /user/mikeg/xpm/1.version
@argyris thinks this bug may be from a recent change he committed
The text was updated successfully, but these errors were encountered: