[
https://issues.apache.org/jira/browse/APEXCORE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110203#comment-15110203
]
ASF GitHub Bot commented on APEXCORE-304:
-----------------------------------------
Github user chinmaykolhatkar commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/208#discussion_r50367453
--- Diff:
engine/src/test/java/com/datatorrent/stram/StramMiniClusterTest.java ---
@@ -227,6 +242,7 @@ public void testSetupShutdown() throws Exception
private LogicalPlan createDAG(LogicalPlanConfiguration lpc) throws
Exception
{
LogicalPlan dag = new LogicalPlan();
+ addExtraTestJar(dag);
--- End diff --
There will be duplicate of code.. Because most of the things I want to do
are part of testSetupShutdown test.
But I get your point, I'll have a seperate test than the current one to
test this functionality.
> Ability to add jars to classpath in populateDAG
> -----------------------------------------------
>
> Key: APEXCORE-304
> URL: https://issues.apache.org/jira/browse/APEXCORE-304
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Chinmay Kolhatkar
> Assignee: Chinmay Kolhatkar
>
> This will have following functionality:
> 1) In populateDAG one would be allowed to add given local jar path to
> classpath of the application.
> 2) Optionally delete the given jar file after copying to HDFS is done.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
