Currently jobs must specify a name in a getJobName() method, which is used to make jobs visible in Oozie and Spark. This means the same job class can't be reused with different configuration under different names.
We can resolve this by removing the job name from that class and having the Schedule.Builder and StreamDescription.Builder specify the name of the job being submitted. This allows job implementations to be reused with different names and settings.
Currently jobs must specify a name in a getJobName() method, which is used to make jobs visible in Oozie and Spark. This means the same job class can't be reused with different configuration under different names.
We can resolve this by removing the job name from that class and having the Schedule.Builder and StreamDescription.Builder specify the name of the job being submitted. This allows job implementations to be reused with different names and settings.