Skip to content
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

New ETLStage classes don't work as the deprecated one #335

Open
anwar6953 opened this issue Jul 14, 2016 · 1 comment
Open

New ETLStage classes don't work as the deprecated one #335

anwar6953 opened this issue Jul 14, 2016 · 1 comment

Comments

@anwar6953
Copy link
Contributor

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.

@anwar6953
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant