THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Some of the well known quirks for the Sqoop2 integration test suite is documented here so that developers can be aware of what to expect when running
mvn clean integration-test
What DB does integration tests use today for storing the Sqoop entities ?
By default it is embedded Derby
*/ public class DerbyProvider extends DatabaseProvider { private static final Logger LOG = Logger.getLogger(DerbyProvider.class); public static final String DRIVER = "org.apache.derby.jdbc.ClientDriver"; // Used port for this instance int port; NetworkServerControl server = null; @Override public void start() { // Start embedded server try { port = NetworkUtils.findAvailablePort(); LOG.info("Will bind to port " + port); server = new NetworkServerControl(InetAddress.getByName("localhost"), port); server.start(new LoggerWriter(LOG, Level.INFO)); // Start won't thrown an exception in case that it fails to start, one // have to explicitly call ping() in order to verify if the server is // up. Check DERBY-1465 for more details. server.ping(); } catch (Exception e) { LOG.error("Can't start Derby network server", e); throw new RuntimeException("Can't derby server", e); } super.start(); }
Where to look for MR Job related logs in the integration tests?
Some related tickets that is in place to fix some of these quirks
- SQOOP-1840 - DerbyProvider quirks,
- SQOOP-1844 -
- SQOOP-1832
- SQOOP-1831 - MR file names now logged