cascading.flow.planner.PlannerException

union of steps have 1 fewer elements than parent assembly: MapReduceHadoopRuleRegistry, missing:

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web75

  • via Google Groups by Piyush Narang, 7 months ago
    union of steps have 1 fewer elements than parent assembly: MapReduceHadoopRuleRegistry, missing:
  • via GitHub by johnynek
    , 10 months ago
    union of steps have 1 fewer elements than parent assembly: MapReduceHadoopRuleRegistry, missing: [Each(_pipe_4+_pipe_5)[Identity[decl:'id', 'count']]]
  • union of steps have 3 fewer elements than parent assembly: MapReduceHadoopRuleRegistry, missing: [Hfs["TextDelimited[['f1', 'f2', 'f3']]"]["../cascading-platform/src/test/resources/data/delimited-file1.txt"], Every(GroupBy Pipe 1)[First[decl:ARGS]], GroupBy(GroupBy Pipe 1)[by:[{1}:'f1']]]
  • Stack trace

    • cascading.flow.planner.PlannerException: union of steps have 1 fewer elements than parent assembly: MapReduceHadoopRuleRegistry, missing: at cascading.flow.planner.FlowPlanner.verifyResultInternal(FlowPlanner.java:621) at cascading.flow.planner.FlowPlanner.verifyResult(FlowPlanner.java:560) at cascading.flow.planner.rule.RuleSetExec.execPlannerFor(RuleSetExec.java:163) at cascading.flow.planner.rule.RuleSetExec$3.call(RuleSetExec.java:336) at cascading.flow.planner.rule.RuleSetExec$3.call(RuleSetExec.java:328) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.