Top Level Entity

Represents a core entity that exposes config objects and used in sqoop job lifecycle.

Configurable have a associated version that acts as a identifier for connector config upgrades.

/**
 * Represents the sqoop entities that can own configs
 */
public enum MConfigurableType {
  /** Connector as a owner of config keys */
  CONNECTOR,
  /** Driver as a owner of config keys */
  DRIVER;
}

• HAS 1-n CONFIG objects
• HAS 1-n LINK objects

is a type of configurable

There can be many connectors registered to the sqoop server

• HAS 1-n CONFIG objects

is a type of configurable

There is only one Driver object representing sqoop in the system

MConfigType with supported config types are

public enum MConfigType {
  /** Unknown config type */
  OTHER,
  @Deprecated
  // NOTE: only exists to support the connector data upgrade path
  CONNECTION,
  /** link config type */ ( should have been  called connector config type !)
  LINK,
  /** Job config type */
  JOB;
}

MInput.java an abstract class and @Input annotation

Concrete classes for each supported types

MIntegerInput.java

MStringInput.java

• Associated with a CONFIG object

Represents the key-value pairs for a given config.

MInputTypes supported are

public enum MInputType {
  /** Unknown input type */
  OTHER,
  /** String input type */
  STRING,
  /** Map input type */
  MAP,
  /** Integer input type */
  INTEGER,
  /** Boolean input type */
  BOOLEAN,
  /** String based input that can contain only predefined values **/
  ENUM,
  ;
}

MLink.java

• Associated with a CONNECTOR
• HAS a CONFIG-INPUT object

Represents the config inputs required to physically connect to the data-source a connector represents. Hence it is associated with a connector.

It has mainly one config object represented by MLinkConfig

MJob.java

MFromConfig.java

MToConfig.java

MDriverConfig.java

• HAS 3 CONFIG-INPUT objects
• HAS 1-n SUBMISSIONS

Represents the sqoop job. It encapsulates all the required configs to run the sqoop job.

Primarily the sqoop job has the 3 main components, the FROM, TO and the DRIVER.

FROM and its related MFromConfig represent the config-inputs-values required to Extract data from the source

TO and its related MToConfig represent the config-inputs-values required to load data to the destination

DRIVER and its related MDriverConfig the config-inputs-values required by the execution engine that runs the sqoop job optimally.

Represents the job run details. Includes the job status, job counters and metrics from the job execution engine

http://sqoop.apache.org/docs/1.99.4/RESTAPI.html#v1-submissions-jname-jname-get-get-submissions-by-job