Page History

...

Top level structure that contains one instance of MJobForms for one corresponding connector. Forms will contained filled values.

Class relationship

...

Example

Let's assume some JDBC based Connector.

...

MConnector

...

• For connection: Contains list of one MForm called "Connection" containing three inputs "JDBC URL", "Username" and "Password".
• For job: Contains list of one MForm called "Source" containing single input "Table".

...

MFramework

...

• For connection: Contains empty list - e.g. no values are required
• For job: Contains one MForm called "Target" containing single input "HDFS Directory"

Administrators might create two different connections based on this example connector:

...

Connection 1:

...

• Connector part: Contain values for connector "JDBC URL" contains "jdbc:mysql://development/test", "Username" contains "letest" and "Password" contains "letest".
• Framework part: Contain values for framework. As framework did not specified any MForms, this will be empty.

...

Connection 2:

...

• Connector part: Contain values for connector "JDBC URL" contains "jdbc:mysql://production/test", "Username" contains "production-user" and "Password" contains "aosdf792r7asfhas8sd-9a7(&(&@#&$(Vosfs9fya9d7(&SD(F*&S(*F&SDF&VChsdfhsdf" (Damn good password).
• Framework part: Contain values for framework. As framework did not specified any MForms, this will be empty.

Operation did not yet have time to utilize connection 2 as it's still playing with connection 1. He however already created couple of jobs based on this connection: 

...

Job 1:

...

• Is based on Connection 1
• Connector part: Contain values for connector, "Table" contains "traffic_details".
• Framework part: Contain values for framework, "HDFS Directory" contains "/storage/traffic_details"

...

Job 2:

...

• Is based on Connection 1
• Connector part: Contain values for connector, "Table" contains "log".
• Framework part: Contain values for framework, "HDFS Directory" contains "/storage/log"