Folks,
I am making some code changes to "flink-runtime" module. I am able to 
test/debug my changes from IDE (IntelliJ) using remote debug option (test Job 
Manager/Task Manager runtime/startup).

Steps followed...1) git clone flink...
2) Import Flink maven project from IntelliJ3) Made some code changes to 
flink-runtime module4) test/debug my changes using JM/TM startup scripts and 
remote debug attach options
I want to write a job code and test it to make sure the changes that I have 
made to "flink-runtime" works properly. Ideally I would like to test the "job 
code" on the same project workspace (the one create in step-3)   
If I understood correctly, the standard way to setup a job development 
environment in iDE is to use "flink-quickstart-java" maven project 
(https://ci.apache.org/projects/flink/flink-docs-release-1.0/quickstart/java_api_quickstart.html)
 which comes with pre-configured Flink artifact dependencies. In my case, I 
would like the Job code to use the dependencies from my local IDE changes 
(project workspace artifacts from step-3). 

One option for me is to push the build artifacts from Flink workspace (step-3) 
to local maven artifactory and refer these artifacts as dependency from the Job 
code project workspace. I haven't tested it but I would not prefer as it is not 
productive.
I would like to understand what's the recommended approach for this scenario?
Please share your thoughts.
RegardsVijay

Reply via email to