Versions Compared

Old Version 5

changes.mady.by.user Gwen Shapira

Saved on

compared with

New Version 6

changes.mady.by.user Gwen Shapira

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Allow development of data connectors against a stable API, independent on Sqoop2 implementation internals (such as choice of execution engine, dependency on Hadoop components, etc). For example:  Oracle connector can't assume a tnsnames.ora exists in the environment,  Kite connector can't assume that hive-site.xml will exist. The connector can still ask for a location of hive-site.xml or tnsnames.ora as an input when creating a link though.
  • Connectors focus on how to get data in and out of data systems. The framework include execution life-cycle - kicking off tasks / workers and such. We never rely on the framework to handle data  reads and writes (even though most frameworks have IO capability) - this is the responsibility of the connectors.

 

 

 

 

 

 

Note

Adding some fun facts about the design are encouraged!