You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am getting following error when using 'MapReduceManager mrManager = appManager.getMapReduceManager()' with co.cask.cdap.etl.proto.v2.ETLStage and co.cask.cdap.proto.artifact.AppRequest.
java.lang.RuntimeException: co.cask.cdap.common.ProgramNotFoundException: 'program:default.XMLParserTest.mapreduce.ETLMapReduce' was not found.
at co.cask.cdap.client.ProgramClient.getStatus(ProgramClient.java:269)
at co.cask.cdap.test.remote.RemoteApplicationManager.startProgram(RemoteApplicationManager.java:127)
at co.cask.cdap.test.AbstractProgramManager.start(AbstractProgramManager.java:49)
at co.cask.cdap.test.AbstractProgramManager.start(AbstractProgramManager.java:44)
at co.cask.cdap.app.etl.batch.XMLParserTest.testXPathArray(XMLParserTest.java:376)
However, when I use 'MapReduceManager mrManager = appManager.getMapReduceManager()' with the deprecated classes ETLStage (co.cask.cdap.etl.common.ETLStage) and AppRequest(co.cask.cdap.etl.batch.config.ETLBatchConfig), I am able to check the failed status and the test case passes on both standalone and cluster.
We need to figure out if there is something wrong with the new ETLStage classes or how they're handled in integration tests.
The text was updated successfully, but these errors were encountered:
The cause for this is that using the new APIs uses the new app, in which the MapReduce is no longer called ETLMapreduce. Instead, the name is something like phase-1.
Because of this, the status check fails.
One way to do it is to get the app spec and list the program(s) in the workflow and check their status. And/or check the status of the workflow, which is dependent on https://issues.cask.co/browse/CDAP-6008.
We need to figure out if there is something wrong with the new ETLStage classes or how they're handled in integration tests.
The text was updated successfully, but these errors were encountered: