sqoop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jar...@apache.org
Subject svn commit: r1471791 [2/5] - in /sqoop/site/trunk/content/resources/docs/1.99.2: ./ _sources/ _static/ css/ images/ images/logos/
Date Thu, 25 Apr 2013 00:20:55 GMT
Added: sqoop/site/trunk/content/resources/docs/1.99.2/Sqoop5MinutesDemo.html
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/Sqoop5MinutesDemo.html?rev=1471791&view=auto
==============================================================================
--- sqoop/site/trunk/content/resources/docs/1.99.2/Sqoop5MinutesDemo.html (added)
+++ sqoop/site/trunk/content/resources/docs/1.99.2/Sqoop5MinutesDemo.html Thu Apr 25 00:20:54 2013
@@ -0,0 +1,198 @@
+
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+  <head>
+    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+    
+    <title>Sqoop 5 Minutes Demo &mdash; Apache Sqoop  documentation</title>
+    
+    <link rel="stylesheet" href="_static/haiku.css" type="text/css" />
+    <link rel="stylesheet" href="_static/pygments.css" type="text/css" />
+    <link rel="stylesheet" href="_static/print.css" type="text/css" />
+    
+    <script type="text/javascript">
+      var DOCUMENTATION_OPTIONS = {
+        URL_ROOT:    '',
+        VERSION:     '',
+        COLLAPSE_INDEX: false,
+        FILE_SUFFIX: '.html',
+        HAS_SOURCE:  true
+      };
+    </script>
+    <script type="text/javascript" src="_static/jquery.js"></script>
+    <script type="text/javascript" src="_static/underscore.js"></script>
+    <script type="text/javascript" src="_static/doctools.js"></script>
+    <script type="text/javascript" src="_static/theme_extras.js"></script>
+    <link rel="top" title="Apache Sqoop  documentation" href="index.html" /> 
+  </head>
+  <body>
+      <div class="header"><img class="rightlogo" src="_static/sqoop-logo.png" alt="Logo"/><h1 class="heading"><a href="index.html">
+          <span>Apache Sqoop  documentation</span></a></h1>
+        <h2 class="heading"><span>Sqoop 5 Minutes Demo</span></h2>
+      </div>
+      <div class="topnav">
+      
+        <p>
+        <a class="uplink" href="index.html">Contents</a>
+        </p>
+
+      </div>
+      <div class="content">
+        
+        
+  <div class="section" id="sqoop-5-minutes-demo">
+<h1>Sqoop 5 Minutes Demo<a class="headerlink" href="#sqoop-5-minutes-demo" title="Permalink to this headline">¶</a></h1>
+<p>This page will walk you through basic usage of Sqoop. You need to have installed and configured Sqoop server and client in order to follow this guide. Installation procedure is described on <a class="reference external" href="Installation.html">Installation page</a>. Please note that precise output shown in this page might differ from your as Sqoop develops. All major information should however remain the same.</p>
+<p>Sqoop is using numerical identifiers to identify various meta data structures (connectors, connections, jobs). Each meta data structures have it&#8217;s own pool of identifiers and thus it&#8217;s perfectly valid when Sqoop have connector with id 1, connection with id 1 and job with id 1 at the same time.</p>
+<div class="section" id="starting-client">
+<h2>Starting Client<a class="headerlink" href="#starting-client" title="Permalink to this headline">¶</a></h2>
+<p>Start client in interactive mode using following command:</p>
+<div class="highlight-none"><div class="highlight"><pre>./bin/sqoop.sh client
+</pre></div>
+</div>
+<p>Configure client to use your Sqoop server:</p>
+<div class="highlight-none"><div class="highlight"><pre>sqoop:000&gt; set server --host your.host.com --port 12000 --webapp sqoop
+</pre></div>
+</div>
+<p>Verify that connection is working by simple version checking:</p>
+<div class="highlight-none"><div class="highlight"><pre>sqoop:000&gt; show version --all
+Server version:
+  Sqoop 2.0.0-SNAPSHOT revision Unknown
+  Compiled by jarcec on Wed Nov 21 16:15:51 PST 2012
+Client version:
+  Sqoop 2.0.0-SNAPSHOT revision Unknown
+  Compiled by jarcec on Wed Nov 21 16:15:51 PST 2012
+Protocol version:
+  [1]
+</pre></div>
+</div>
+<p>You should received similar output as shown describing versions of both your client and remote server as well as negotiated protocol version.</p>
+</div>
+<div class="section" id="creating-connection-object">
+<h2>Creating Connection Object<a class="headerlink" href="#creating-connection-object" title="Permalink to this headline">¶</a></h2>
+<p>Check what connectors are available on your Sqoop server:</p>
+<div class="highlight-none"><div class="highlight"><pre>sqoop:000&gt; show connector --all
+1 connector(s) to show:
+Connector with id 1:
+  Name: generic-jdbc-connector
+  Class: org.apache.sqoop.connector.jdbc.GenericJdbcConnector
+  Supported job types: [EXPORT, IMPORT]
+...
+</pre></div>
+</div>
+<p>Our example contains one connector called <tt class="docutils literal"><span class="pre">generic-jdbc-connector</span></tt>. This is basic connector that is relying on Java JDBC interface for doing data transfers. It should work on most common databases that are providing JDBC drivers. Please note that you must install JDBC drivers separately. They are not bundled in Sqoop due to incompatible licenses.</p>
+<p>Generic JDBC Connector have in our example id 1 and we will use this value to create new connection object for this connector:</p>
+<div class="highlight-none"><div class="highlight"><pre>sqoop:000&gt; create connection --cid 1
+Creating connection for connector with id 1
+Please fill following values to create new connection object
+Name: First connection
+
+Configuration configuration
+JDBC Driver Class: com.mysql.jdbc.Driver
+JDBC Connection String: jdbc:mysql://mysql.server/database
+Username: sqoop
+Password: *****
+JDBC Connection Properties:
+There are currently 0 values in the map:
+entry#
+
+Security related configuration options
+Max connections: 0
+New connection was successfully created with validation status FINE and persistent id 1
+</pre></div>
+</div>
+<p>Our new connection object was created with assigned id 1.</p>
+</div>
+<div class="section" id="creating-job-object">
+<h2>Creating Job Object<a class="headerlink" href="#creating-job-object" title="Permalink to this headline">¶</a></h2>
+<p>Job objects have multiple types and each connector might not support all of them. Generic JDBC Connector supports job types <tt class="docutils literal"><span class="pre">import</span></tt> (importing data to Hadoop ecosystem) and <tt class="docutils literal"><span class="pre">export</span></tt> (exporting data from Hadoop ecosystem). List of supported job types for each connector might be seen in the output of <tt class="docutils literal"><span class="pre">show</span> <span class="pre">connector</span></tt> command:</p>
+<div class="highlight-none"><div class="highlight"><pre>sqoop:000&gt; show connector --all
+...
+  Name: generic-jdbc-connector
+...
+  Supported job types: [EXPORT, IMPORT]
+...
+</pre></div>
+</div>
+<p>Create import job for Connection object created in previous section:</p>
+<div class="highlight-none"><div class="highlight"><pre>sqoop:000&gt; create job --xid 1 --type import
+Creating job for connection with id 1
+Please fill following values to create new job object
+Name: First job
+
+Database configuration
+Table name: users
+Table SQL statement:
+Table column names:
+Partition column name:
+Boundary query:
+
+Output configuration
+Storage type:
+  0 : HDFS
+Choose: 0
+Output directory: /user/jarcec/users
+New job was successfully created with validation status FINE and persistent id 1
+</pre></div>
+</div>
+<p>Our new job object was created with assigned id 1.</p>
+</div>
+<div class="section" id="moving-data">
+<h2>Moving Data<a class="headerlink" href="#moving-data" title="Permalink to this headline">¶</a></h2>
+<p>When all meta data objects are in place we can start moving data around. You can submit Hadoop job using <tt class="docutils literal"><span class="pre">submission</span> <span class="pre">start</span></tt> command:</p>
+<div class="highlight-none"><div class="highlight"><pre>sqoop:000&gt; submission start --jid 1
+Submission details
+Job id: 1
+Status: BOOTING
+Creation date: 2012-12-23 13:20:34 PST
+Last update date: 2012-12-23 13:20:34 PST
+External Id: job_1353136146286_0004
+        http://hadoop.cluster.com:8088/proxy/application_1353136146286_0004/
+Progress: Progress is not available
+</pre></div>
+</div>
+<p>You can iteratively check your running job status with <tt class="docutils literal"><span class="pre">submission</span> <span class="pre">status</span></tt> command:</p>
+<div class="highlight-none"><div class="highlight"><pre>sqoop:000&gt; submission status --jid 1
+Submission details
+Job id: 1
+Status: RUNNING
+Creation date: 2012-12-23 13:21:45 PST
+Last update date: 2012-12-23 13:21:56 PST
+External Id: job_1353136146286_0005
+        http://hadoop.cluster.com:8088/proxy/application_1353136146286_0004/
+Progress: 0.00 %
+</pre></div>
+</div>
+<p>And finally you can stop running job at any time using <tt class="docutils literal"><span class="pre">submission</span> <span class="pre">stop</span></tt> command:</p>
+<div class="highlight-none"><div class="highlight"><pre>sqoop:000&gt; submission stop --jid 1
+Submission details
+Job id: 1
+Status: FAILED
+Creation date: 2012-12-23 13:22:39 PST
+Last update date: 2012-12-23 13:22:42 PST
+External Id: job_1353136146286_0006
+        http://hadoop.cluster.com:8088/proxy/application_1353136146286_0004/
+</pre></div>
+</div>
+</div>
+</div>
+
+
+      </div>
+      <div class="bottomnav">
+      
+        <p>
+        <a class="uplink" href="index.html">Contents</a>
+        </p>
+
+      </div>
+
+    <div class="footer">
+        &copy; Copyright 2009-2013 The Apache Software Foundation.
+    </div>
+  </body>
+</html>
\ No newline at end of file

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_sources/BuildingSqoop2.txt
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_sources/BuildingSqoop2.txt?rev=1471791&view=auto
==============================================================================
--- sqoop/site/trunk/content/resources/docs/1.99.2/_sources/BuildingSqoop2.txt (added)
+++ sqoop/site/trunk/content/resources/docs/1.99.2/_sources/BuildingSqoop2.txt Thu Apr 25 00:20:54 2013
@@ -0,0 +1,69 @@
+.. Licensed to the Apache Software Foundation (ASF) under one or more
+   contributor license agreements.  See the NOTICE file distributed with
+   this work for additional information regarding copyright ownership.
+   The ASF licenses this file to You under the Apache License, Version 2.0
+   (the "License"); you may not use this file except in compliance with
+   the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+
+================================
+Building Sqoop2 from source code
+================================
+
+This guide will show you how to build Sqoop2 from source code. Sqoop is using `maven <http://maven.apache.org/>`_ as build system. You you will need to use at least version 3.0 as older versions will not work correctly. All other dependencies will be downloaded by maven automatically. With exception of special JDBC drivers that are needed only for advanced integration tests.
+
+Downloading source code
+-----------------------
+
+Sqoop project is using git as a revision control system hosted at Apache Software Foundation. You can clone entire repository using following command:
+
+::
+
+  git clone https://git-wip-us.apache.org/repos/asf/sqoop.git sqoop2
+
+Sqoop2 is currently developed in special branch ``sqoop2`` that you need to check out after clone:
+
+::
+
+  cd sqoop2
+  git checkout sqoop2
+
+Building project
+----------------
+
+You can use usual maven targets like ``compile`` or ``package`` to build the project. Sqoop supports two major Hadoop revisions at the moment - 1.x and 2.x. As compiled code for one Hadoop major version can't be used on another, you must compile Sqoop against appropriate Hadoop version. You can change the target Hadoop version by specifying ``-Dhadoop.profile=$hadoopVersion`` on the maven command line. Possible values of ``$hadoopVersions`` are 100 and 200 for Hadoop version 1.x and 2.x respectively. Sqoop will compile against Hadoop 2 by default. Following example will compile Sqoop against Hadoop 1.x:
+
+::
+
+  mvn compile -Dhadoop.profile=100
+
+Maven target ``package`` can be used to create Sqoop packages similar to the ones that are officially available for download. Sqoop will build only source tarball by default. You need to specify ``-Pbinary`` to build binary distribution. You might need to explicitly specify Hadoop version if the default is not accurate.
+
+::
+
+  mvn package -Pbinary
+
+Running tests
+-------------
+
+Sqoop supports two different sets of tests. First smaller and much faster set is called unit tests and will be executed on maven target ``test``. Second larger set of integration tests will be executed on maven target ``integration-test``. Please note that integration tests might require manual steps for installing various JDBC drivers into your local maven cache.
+
+Example for running unit tests:
+
+::
+
+  mvn test
+
+Example for running integration tests:
+
+::
+
+  mvn integration-test

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_sources/ClientAPI.txt
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_sources/ClientAPI.txt?rev=1471791&view=auto
==============================================================================
--- sqoop/site/trunk/content/resources/docs/1.99.2/_sources/ClientAPI.txt (added)
+++ sqoop/site/trunk/content/resources/docs/1.99.2/_sources/ClientAPI.txt Thu Apr 25 00:20:54 2013
@@ -0,0 +1,319 @@
+.. Licensed to the Apache Software Foundation (ASF) under one or more
+   contributor license agreements.  See the NOTICE file distributed with
+   this work for additional information regarding copyright ownership.
+   The ASF licenses this file to You under the Apache License, Version 2.0
+   (the "License"); you may not use this file except in compliance with
+   the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+
+======================
+Sqoop Client API Guide
+======================
+
+This document will explain how to use Sqoop Client API with external application. Client API allows you to execute the functions of sqoop commands. It requires Sqoop Client JAR and its dependencies.
+
+Client API is explained using Generic JDBC Connector properties. Before executing the application using the sqoop client API, check whether sqoop server is running.
+
+Workflow
+========
+
+Given workflow has to be followed for executing a job in Sqoop server.
+
+  1. Create connection using Connector ID (cid) - Creates connection and returns connection ID (xid)
+  2. Create Job using Connection ID (xid)       - Create job and returns Job ID (jid)
+  3. Job submission with Job ID (jid)           - Submit sqoop Job to server
+
+Project Dependencies
+====================
+Here given maven dependency
+
+::
+
+  <dependency>
+    <groupId>org.apache.sqoop</groupId>
+      <artifactId>sqoop-client</artifactId>
+      <version>${requestedVersion}</version>
+  </dependency>
+
+Initialization
+==============
+
+First initialize the SqoopClient class with server URL as argument.
+
+::
+
+  String url = "http://localhost:12000/sqoop/";
+  SqoopClient client = new SqoopClient(url);
+
+Server URL value can be modfied by setting value to setServerUrl(String) method
+
+::
+
+  client.setServerUrl(newUrl);
+
+
+Connection
+==========
+
+Client API allows you to create, update and delete connection. For creating or updating connection requires Connector forms and Framwork Forms. User has to retrive the connector and framework forms, then update the values.
+
+Create Connection
+-----------------
+
+First create a new connection by invoking newConnection(cid) method with connector ID and returns a MConnection object with dummy id. Then fill the connection and framework forms as given below. Invoke create connection with updated connection object.
+
+::
+
+  //Dummy connection object
+  MConnection newCon = client.newConnection(1);
+
+  //Get connection and framework forms. Set name for connection
+  MConnectionForms conForms = newCon.getConnectorPart();
+  MConnectionForms frameworkForms = newCon.getFrameworkPart();
+  newCon.setName("MyConnection");
+
+  //Set connection forms values
+  conForms.getStringInput("connection.connectionString").setValue("jdbc:mysql://localhost/my");
+  conForms.getStringInput("connection.jdbcDriver").setValue("com.mysql.jdbc.Driver");
+  conForms.getStringInput("connection.username").setValue("root");
+  conForms.getStringInput("connection.password").setValue("root");
+
+  frameworkForms.getIntegerInput("security.maxConnections").setValue(0);
+
+  Status status  = client.createConnection(newCon);
+  if(status.canProceed()) {
+   System.out.println("Created. New Connection ID : " +newCon.getPersistenceId());
+  } else {
+   System.out.println("Check for status and forms error ");
+  }
+
+status.canProceed() returns true if status is FINE or ACCEPTABLE. Above code has given status after validation of connector and framework forms.
+
+On successful execution, new connection ID is assigned for the connection. getPersistenceId() method returns ID.
+User can retrieve a connection using below methods
+
++----------------------------+--------------------------------------+
+|   Method                   | Description                          |
++============================+======================================+
+| ``getConnection(xid)``     | Returns a connection object.         |
++----------------------------+--------------------------------------+
+| ``getConnections()``       | Returns list of connection object    |
++----------------------------+--------------------------------------+
+
+List of status code
+-------------------
+
++------------------+------------------------------------------------------------------------------------------------------------+
+| Function         | Description                                                                                                |
++==================+============================================================================================================+
+| ``FINE``         | There are no issues, no warnings.                                                                          |
++------------------+------------------------------------------------------------------------------------------------------------+
+| ``ACCEPTABLE``   | Validated entity is correct enough to be processed. There might be some warnings, but no errors.           |
++------------------+------------------------------------------------------------------------------------------------------------+
+| ``UNACCEPTABLE`` | There are serious issues with validated entity. We can't proceed until reported issues will be resolved.   |
++------------------+------------------------------------------------------------------------------------------------------------+
+
+View Error or Warning message
+-----------------------------
+
+In case of any UNACCEPTABLE AND ACCEPTABLE status, user has to iterate the connector part forms and framework part forms for getting actual error or warning message. Below piece of code describe how to itereate over the forms for input message.
+
+::
+
+ printMessage(newCon.getConnectorPart().getForms());
+ printMessage(newCon.getFrameworkPart().getForms());
+
+ private static void printMessage(List<MForm> formList) {
+   for(MForm form : formList) {
+     List<MInput<?>> inputlist = form.getInputs();
+     if (form.getValidationMessage() != null) {
+       System.out.println("Form message: " + form.getValidationMessage());
+     }
+     for (MInput minput : inputlist) {
+       if (minput.getValidationStatus() == Status.ACCEPTABLE) {
+         System.out.println("Warning:" + minput.getValidationMessage());
+       } else if (minput.getValidationStatus() == Status.UNACCEPTABLE) {
+         System.out.println("Error:" + minput.getValidationMessage());
+       }
+     }
+   }
+ }
+
+Job
+===
+
+A job object holds database configurations, input or output configurations and resources required for executing as a hadoop job. Create job object requires filling connector part and framework part forms.
+
+Below given code shows how to create a import job
+
+::
+
+  String url = "http://localhost:12000/sqoop/";
+  SqoopClient client = new SqoopClient(url);
+  //Creating dummy job object
+  MJob newjob = client.newJob(1, org.apache.sqoop.model.MJob.Type.IMPORT);
+  MJobForms connectorForm = newjob.getConnectorPart();
+  MJobForms frameworkForm = newjob.getFrameworkPart();
+
+  newjob.setName("ImportJob");
+  //Database configuration
+  connectorForm.getStringInput("table.schemaName").setValue("");
+  //Input either table name or sql
+  connectorForm.getStringInput("table.tableName").setValue("table");
+  //connectorForm.getStringInput("table.sql").setValue("select id,name from table where ${CONDITIONS}");
+  connectorForm.getStringInput("table.columns").setValue("id,name");
+  connectorForm.getStringInput("table.partitionColumn").setValue("id");
+  //Set boundary value only if required
+  //connectorForm.getStringInput("table.boundaryQuery").setValue("");
+
+  //Output configurations
+  frameworkForm.getEnumInput("output.storageType").setValue("HDFS");
+  frameworkForm.getEnumInput("output.outputFormat").setValue("TEXT_FILE");//Other option: SEQUENCE_FILE
+  frameworkForm.getStringInput("output.outputDirectory").setValue("/output");
+
+  //Job resources
+  frameworkForm.getIntegerInput("throttling.extractors").setValue(1);
+  frameworkForm.getIntegerInput("throttling.loaders").setValue(1);
+
+  Status status = client.createJob(newjob);
+  if(status.canProceed()) {
+   System.out.println("New Job ID: "+ newjob.getPersistenceId());
+  } else {
+   System.out.println("Check for status and forms error ");
+  }
+
+  //Print errors or warnings
+  printMessage(newjob.getConnectorPart().getForms());
+  printMessage(newjob.getFrameworkPart().getForms());
+
+
+Export job creation is same as import job, but only few input configuration changes
+
+::
+
+  String url = "http://localhost:12000/sqoop/";
+  SqoopClient client = new SqoopClient(url);
+  MJob newjob = client.newJob(1, org.apache.sqoop.model.MJob.Type.EXPORT);
+  MJobForms connectorForm = newjob.getConnectorPart();
+  MJobForms frameworkForm = newjob.getFrameworkPart();
+
+  newjob.setName("ExportJob");
+  //Database configuration
+  connectorForm.getStringInput("table.schemaName").setValue("");
+  //Input either table name or sql
+  connectorForm.getStringInput("table.tableName").setValue("table");
+  //connectorForm.getStringInput("table.sql").setValue("select id,name from table where ${CONDITIONS}");
+  connectorForm.getStringInput("table.columns").setValue("id,name");
+
+  //Input configurations
+  frameworkForm.getStringInput("input.inputDirectory").setValue("/input");
+
+  //Job resources
+  frameworkForm.getIntegerInput("throttling.extractors").setValue(1);
+  frameworkForm.getIntegerInput("throttling.loaders").setValue(1);
+
+  Status status = client.createJob(newjob);
+  if(status.canProceed()) {
+    System.out.println("New Job ID: "+ newjob.getPersistenceId());
+  } else {
+    System.out.println("Check for status and forms error ");
+  }
+
+  //Print errors or warnings
+  printMessage(newjob.getConnectorPart().getForms());
+  printMessage(newjob.getFrameworkPart().getForms());
+
+Managing connection and job
+---------------------------
+After creating connection or job object, you can update or delete a connection or job using given functions
+
++----------------------------------+------------------------------------------------------------------------------------+
+|   Method                         | Description                                                                        |
++==================================+====================================================================================+
+| ``updateConnection(connection)`` | Invoke update with connection object and check status for any errors or warnings   |
++----------------------------------+------------------------------------------------------------------------------------+
+| ``deleteConnection(xid)``        | Delete connection. Deletes only if specified connection is used by any job         |
++----------------------------------+------------------------------------------------------------------------------------+
+| ``updateJob(job)``               | Invoke update with job object and check status for any errors or warnings          |
++----------------------------------+------------------------------------------------------------------------------------+
+| ``deleteJob(jid)``               | Delete job                                                                         |
++----------------------------------+------------------------------------------------------------------------------------+
+
+Job Submission
+==============
+
+Job submission requires a job id. On successful submission, getStatus() method returns "BOOTING" or "RUNNING".
+
+::
+
+  //Job submission start
+  MSubmission submission = client.startSubmission(1);
+  System.out.println("Status : " + submission.getStatus());
+  if(submission.getStatus().isRunning() && submission.getProgress() != -1) {
+    System.out.println("Progress : " + String.format("%.2f %%", submission.getProgress() * 100));
+  }
+  System.out.println("Hadoop job id :" + submission.getExternalId());
+  System.out.println("Job link : " + submission.getExternalLink());
+  Counters counters = submission.getCounters();
+  if(counters != null) {
+    System.out.println("Counters:");
+    for(CounterGroup group : counters) {
+      System.out.print("\t");
+      System.out.println(group.getName());
+      for(Counter counter : group) {
+        System.out.print("\t\t");
+        System.out.print(counter.getName());
+        System.out.print(": ");
+        System.out.println(counter.getValue());
+      }
+    }
+  }
+  if(submission.getExceptionInfo() != null) {
+    System.out.println("Exception info : " +submission.getExceptionInfo());
+  }
+
+
+  //Check job status
+  MSubmission submission = client.getSubmissionStatus(1);
+  if(submission.getStatus().isRunning() && submission.getProgress() != -1) {
+    System.out.println("Progress : " + String.format("%.2f %%", submission.getProgress() * 100));
+  }
+
+  //Stop a running job
+  submission.stopSubmission(jid);
+
+Describe Forms
+==========================
+
+You can view the connection or job forms input values with labels of built-in resource bundle.
+
+::
+
+  String url = "http://localhost:12000/sqoop/";
+  SqoopClient client = new SqoopClient(url);
+  //Use getJob(jid) for describing job.
+  //While printing connection forms, pass connector id to getResourceBundle(cid).
+  describe(client.getConnection(1).getConnectorPart().getForms(), client.getResourceBundle(1));
+  describe(client.getConnection(1).getFrameworkPart().getForms(), client.getFrameworkResourceBundle());
+
+  void describe(List<MForm> forms, ResourceBundle resource) {
+    for (MForm mf : forms) {
+      System.out.println(resource.getString(mf.getLabelKey())+":");
+      List<MInput<?>> mis = mf.getInputs();
+      for (MInput mi : mis) {
+        System.out.println(resource.getString(mi.getLabelKey()) + " : " + mi.getValue());
+      }
+      System.out.println();
+    }
+  }
+
+
+Above Sqoop 2 Client API tutorial explained you how to create connection, create job and submit job.

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_sources/CommandLineClient.txt
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_sources/CommandLineClient.txt?rev=1471791&view=auto
==============================================================================
--- sqoop/site/trunk/content/resources/docs/1.99.2/_sources/CommandLineClient.txt (added)
+++ sqoop/site/trunk/content/resources/docs/1.99.2/_sources/CommandLineClient.txt Thu Apr 25 00:20:54 2013
@@ -0,0 +1,483 @@
+.. Licensed to the Apache Software Foundation (ASF) under one or more
+   contributor license agreements.  See the NOTICE file distributed with
+   this work for additional information regarding copyright ownership.
+   The ASF licenses this file to You under the Apache License, Version 2.0
+   (the "License"); you may not use this file except in compliance with
+   the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+
+===================
+Command Line Client
+===================
+
+Sqoop 2 provides command line client that is capable of communicating with Sqoop 2 server using REST interface. Client is able to run in two modes - interactive and batch mode. Commands ``create``, ``update`` and ``clone`` are not currently supported in batch mode. Interactive mode supports all available commands.
+
+You can start Sqoop 2 client in interactive mode using provided ``sqoop.sh`` shell script by passing argument ``client``: ::
+
+  sqoop.sh client
+
+Batch mode can be started by adding additional argument representing path to your Sqoop client script: ::
+
+  sqoop.sh client /path/to/your/script.sqoop
+
+Sqoop client script is expected to contain valid Sqoop client commands, empty lines and lines starting with ``#`` that are denoting comment lines. Comments and empty lines are ignored, all other lines are interpreted. Example script: ::
+
+  # Specify company server
+  set server --host sqoop2.company.net
+
+  # Executing given job
+  submission start --jid 1
+
+.. contents:: Table of Contents
+
+Resource file
+=============
+
+Sqoop 2 client have ability to load resource files similarly as other command line tools. At the beginning of execution Sqoop client will check existence of file ``.sqoop2rc`` in home directory of currently logged user. If such file exists, it will be interpreted before any additional actions. This file is loaded in both interactive and batch mode. It can be used to execute any batch compatible commands.
+
+Example resource file: ::
+
+  # Configure our Sqoop 2 server automatically
+  set server --host sqoop2.company.net
+
+  # Run in verbose mode by default
+  set option --name verbose --value true
+
+Commands
+========
+
+Sqoop 2 contains several commands that will be documented in this section. Each command have one more functions that are accepting various arguments. Not all commands are supported in both interactive and batch mode.
+
+Auxiliary Commands
+------------------
+
+Auxiliary commands are commands that are improving user experience and are running purely on client side. Thus they do not need working connection to the server.
+
+* ``exit`` Exit client immediately. This command can be also executed by sending EOT (end of transmission) character. It's CTRL+D on most common Linux shells like Bash or Zsh.
+* ``history`` Print out command history. Please note that Sqoop client is saving history from previous executions and thus you might see commands that you've executed in previous runs.
+* ``help`` Show all available commands with short in-shell documentation.
+
+Set Command
+-----------
+
+Set command allows to set various properties of the client. Similarly as auxiliary commands, set do not require connection to Sqoop server. Set commands is not used to reconfigure Sqoop server.
+
+Available functions:
+
++---------------+------------------------------------------+
+| Function      | Description                              |
++===============+==========================================+
+| ``server``    | Set connection configuration for server  |
++---------------+------------------------------------------+
+| ``option``    | Set various client side options          |
++---------------+------------------------------------------+
+
+Set Server Function
+~~~~~~~~~~~~~~~~~~~
+
+Configure connection to Sqoop server - host port and web application name. Available arguments:
+
++-----------------------+---------------+--------------------------------------------------+
+| Argument              | Default value | Description                                      |
++=======================+===============+==================================================+
+| ``-h``, ``--host``    | localhost     | Server name (FQDN) where Sqoop server is running |
++-----------------------+---------------+--------------------------------------------------+
+| ``-p``, ``--port``    | 12000         | TCP Port                                         |
++-----------------------+---------------+--------------------------------------------------+
+| ``-w``, ``--webapp``  | sqoop         | Tomcat's web application name                    |
++-----------------------+---------------+--------------------------------------------------+
+
+Example: ::
+
+  set server --host sqoop2.company.net --port 80 --webapp sqoop
+
+Set Option Function
+~~~~~~~~~~~~~~~~~~~
+
+Configure Sqoop client related options. This function have two required arguments ``name`` and ``value``. Name represents internal property name and value holds new value that should be set. List of available option names follows:
+
++-------------------+---------------+---------------------------------------------------------------------+
+| Option name       | Default value | Description                                                         |
++===================+===============+=====================================================================+
+| ``verbose``       | false         | Client will print additional information if verbose mode is enabled |
++-------------------+---------------+---------------------------------------------------------------------+
+
+Example: ::
+
+  set option --name verbose --value true
+
+Show Command
+------------
+
+Show commands displays various information including server and protocol versions or all stored meta data.
+
+Available functions:
+
++----------------+--------------------------------------------------------------------------------------------------------+
+| Function       | Description                                                                                            |
++================+========================================================================================================+
+| ``server``     | Display connection information to the server (host, port, webapp)                                      |
++----------------+--------------------------------------------------------------------------------------------------------+
+| ``option``     | Display various client side options                                                                    |
++----------------+--------------------------------------------------------------------------------------------------------+
+| ``version``    | Show version of both client and server (build numbers, supported protocols)                            |
++----------------+--------------------------------------------------------------------------------------------------------+
+| ``connector``  | Show connector meta data - set of parameters that connectors needs to create connections and jobs      |
++----------------+--------------------------------------------------------------------------------------------------------+
+| ``framework``  | Show framework meta data - set of parameters that Sqoop framework needs to create connections and jobs |
++----------------+--------------------------------------------------------------------------------------------------------+
+| ``connection`` | Show created connection meta data objects                                                              |
++----------------+--------------------------------------------------------------------------------------------------------+
+| ``job``        | Show created job meta data objects                                                                     |
++----------------+--------------------------------------------------------------------------------------------------------+
+
+Show Server Function
+~~~~~~~~~~~~~~~~~~~~
+
+Show details about configuration connection to Sqoop server.
+
++-----------------------+--------------------------------------------------------------+
+| Argument              |  Description                                                 |
++=======================+==============================================================+
+| ``-a``, ``--all``     | Show all connection related information (host, port, webapp) |
++-----------------------+--------------------------------------------------------------+
+| ``-h``, ``--host``    | Show host                                                    |
++-----------------------+--------------------------------------------------------------+
+| ``-p``, ``--port``    | Show port                                                    |
++-----------------------+--------------------------------------------------------------+
+| ``-w``, ``--webapp``  | Show web application name                                    |
++-----------------------+--------------------------------------------------------------+
+
+Example: ::
+
+  show server --all
+
+Show Option Function
+~~~~~~~~~~~~~~~~~~~~
+
+Show values of various client side options. This function will show all client options when called without arguments.
+
++-----------------------+--------------------------------------------------------------+
+| Argument              |  Description                                                 |
++=======================+==============================================================+
+| ``-n``, ``--name``    | Show client option value with given name                     |
++-----------------------+--------------------------------------------------------------+
+
+Please check table in `Set Option Function`_ section to get a list of all supported option names.
+
+Example: ::
+
+  show option --name verbose
+
+Show Version Function
+~~~~~~~~~~~~~~~~~~~~~
+
+Show versions of both client and server as well as supported protocols.
+
++------------------------+-----------------------------------------------+
+| Argument               |  Description                                  |
++========================+===============================================+
+| ``-a``, ``--all``      | Show all versions (server, client, protocols) |
++------------------------+-----------------------------------------------+
+| ``-c``, ``--client``   | Show client version                           |
++------------------------+-----------------------------------------------+
+| ``-s``, ``--server``   | Show server version                           |
++------------------------+-----------------------------------------------+
+| ``-p``, ``--protocol`` | Show protocol support on client or server     |
++------------------------+-----------------------------------------------+
+
+Example: ::
+
+  show version --all
+
+Show Connector Function
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Show connector meta data - parameters that connectors need in order to create new connection and job objects.
+
++-----------------------+------------------------------------------------+
+| Argument              |  Description                                   |
++=======================+================================================+
+| ``-a``, ``--all``     | Show information for all connectors            |
++-----------------------+------------------------------------------------+
+| ``-c``, ``--cid <x>`` | Show information for connector with id ``<x>`` |
++-----------------------+------------------------------------------------+
+
+Example: ::
+
+  show connector --all
+
+Show Framework Function
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Show framework meta data - parameters that Sqoop framework need in order to create new connection and job objects.
+
+This function do not have any extra arguments.
+
+Example: ::
+
+  show framework
+
+Show Connection Function
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+Show persisted connection objects.
+
++-----------------------+------------------------------------------------------+
+| Argument              |  Description                                         |
++=======================+======================================================+
+| ``-a``, ``--all``     | Show all available connections from all connectors   |
++-----------------------+------------------------------------------------------+
+| ``-x``, ``--xid <x>`` | Show connection with id ``<x>``                      |
++-----------------------+------------------------------------------------------+
+
+Example: ::
+
+  show connection --all
+
+Show Job Function
+~~~~~~~~~~~~~~~~~
+
+Show persisted job objects.
+
++-----------------------+----------------------------------------------+
+| Argument              |  Description                                 |
++=======================+==============================================+
+| ``-a``, ``--all``     | Show all available jobs from all connectors  |
++-----------------------+----------------------------------------------+
+| ``-j``, ``--jid <x>`` | Show job with id ``<x>``                     |
++-----------------------+----------------------------------------------+
+
+Example: ::
+
+  show job --all
+
+Create Command
+--------------
+
+Creates new connection and job objects. This command is supported only in interactive mode. It will query user for all parameters that are required by specific connector and framework and persist them in Sqoop server for later use.
+
+Available functions:
+
++----------------+-------------------------------------------------+
+| Function       | Description                                     |
++================+=================================================+
+| ``connection`` | Create new connection object                    |
++----------------+-------------------------------------------------+
+| ``job``        | Create new job object                           |
++----------------+-------------------------------------------------+
+
+Create Connection Function
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Create new connection object.
+
++------------------------+-------------------------------------------------------------+
+| Argument               |  Description                                                |
++========================+=============================================================+
+| ``-c``, ``--cid <x>``  |  Create new connection object for connector with id ``<x>`` |
++------------------------+-------------------------------------------------------------+
+
+
+Example: ::
+
+  create connection --cid 1
+
+Create Job Function
+~~~~~~~~~~~~~~~~~~~
+
+Create new job object.
+
++------------------------+------------------------------------------------------------------+
+| Argument               |  Description                                                     |
++========================+==================================================================+
+| ``-x``, ``--xid <x>``  | Create new job object for connection with id ``<x>``             |
++------------------------+------------------------------------------------------------------+
+| ``-t``, ``--type <t>`` | Create new job object with type ``<t>`` (``import``, ``export``) |
++------------------------+------------------------------------------------------------------+
+
+Example: ::
+
+  create job --xid 1
+
+Update Command
+--------------
+
+Update commands allows you to edit connection and job objects - change persisted meta data. This command is supported only in interactive mode.
+
+Update Connection Function
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Update existing connection object.
+
++-----------------------+---------------------------------------------+
+| Argument              |  Description                                |
++=======================+=============================================+
+| ``-x``, ``--xid <x>`` |  Update existing connection with id ``<x>`` |
++-----------------------+---------------------------------------------+
+
+Example: ::
+
+  update connection --xid 1
+
+Update Job Function
+~~~~~~~~~~~~~~~~~~~
+
+Update existing job object.
+
++-----------------------+--------------------------------------------+
+| Argument              |  Description                               |
++=======================+============================================+
+| ``-j``, ``--jid <x>`` | Update existing job object with id ``<x>`` |
++-----------------------+--------------------------------------------+
+
+Example: ::
+
+  update job --jid 1
+
+
+Delete Command
+--------------
+
+Deletes connection and job objects from Sqoop server.
+
+Delete Connection Function
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Delete existing connection object.
+
++-----------------------+-------------------------------------------+
+| Argument              |  Description                              |
++=======================+===========================================+
+| ``-x``, ``--xid <x>`` |  Delete connection object with id ``<x>`` |
++-----------------------+-------------------------------------------+
+
+Example: ::
+
+  delete connection --xid 1
+
+
+Delete Job Function
+~~~~~~~~~~~~~~~~~~~
+
+Delete existing job object.
+
++-----------------------+------------------------------------------+
+| Argument              |  Description                             |
++=======================+==========================================+
+| ``-j``, ``--jid <x>`` | Delete job object with id ``<x>``        |
++-----------------------+------------------------------------------+
+
+Example: ::
+
+  delete job --jid 1
+
+
+Clone Command
+-------------
+
+Clone command will load existing connection or job object from Sqoop server and allow user in place changes that will result in creation of new connection or job object. This command is not supported in batch mode.
+
+Clone Connection Function
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Clone existing connection object.
+
++-----------------------+------------------------------------------+
+| Argument              |  Description                             |
++=======================+==========================================+
+| ``-x``, ``--xid <x>`` |  Clone connection object with id ``<x>`` |
++-----------------------+------------------------------------------+
+
+Example: ::
+
+  clone connection --xid 1
+
+
+Clone Job Function
+~~~~~~~~~~~~~~~~~~
+
+Clone existing job object.
+
++-----------------------+------------------------------------------+
+| Argument              |  Description                             |
++=======================+==========================================+
+| ``-j``, ``--jid <x>`` | Clone job object with id ``<x>``         |
++-----------------------+------------------------------------------+
+
+Example: ::
+
+  clone job --jid 1
+
+
+Submission Command
+------------------
+
+Submission command is entry point for executing actual data transfers. It allows you to start, stop and retrieve status of currently running jobs.
+
+Available functions:
+
++----------------+-------------------------------------------------+
+| Function       | Description                                     |
++================+=================================================+
+| ``start``      | Start job                                       |
++----------------+-------------------------------------------------+
+| ``stop``       | Interrupt running job                           |
++----------------+-------------------------------------------------+
+| ``status``     | Retrieve status for given job                   |
++----------------+-------------------------------------------------+
+
+Submission Start Function
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Start job (submit new submission). Starting already running job is considered as invalid operation.
+
++-----------------------+---------------------------+
+| Argument              |  Description              |
++=======================+===========================+
+| ``-j``, ``--jid <x>`` | Start job with id ``<x>`` |
++-----------------------+---------------------------+
+
+Example: ::
+
+  submission start --jid 1
+
+
+Submission Stop Function
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Interrupt running job.
+
++-----------------------+------------------------------------------+
+| Argument              |  Description                             |
++=======================+==========================================+
+| ``-j``, ``--jid <x>`` | Interrupt running job with id ``<x>``    |
++-----------------------+------------------------------------------+
+
+Example: ::
+
+  submission stop --jid 1
+
+Submission Status Function
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Retrieve last status for given job.
+
++-----------------------+------------------------------------------+
+| Argument              |  Description                             |
++=======================+==========================================+
+| ``-j``, ``--jid <x>`` | Retrieve status for job with id ``<x>``  |
++-----------------------+------------------------------------------+
+
+Example: ::
+
+  submission status --jid 1
+

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_sources/DevEnv.txt
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_sources/DevEnv.txt?rev=1471791&view=auto
==============================================================================
--- sqoop/site/trunk/content/resources/docs/1.99.2/_sources/DevEnv.txt (added)
+++ sqoop/site/trunk/content/resources/docs/1.99.2/_sources/DevEnv.txt Thu Apr 25 00:20:54 2013
@@ -0,0 +1,57 @@
+.. Licensed to the Apache Software Foundation (ASF) under one or more
+   contributor license agreements.  See the NOTICE file distributed with
+   this work for additional information regarding copyright ownership.
+   The ASF licenses this file to You under the Apache License, Version 2.0
+   (the "License"); you may not use this file except in compliance with
+   the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+
+=====================================
+Sqoop 2 Development Environment Setup
+=====================================
+
+This document describes you how to setup development environment for Sqoop 2.
+
+System Requirement
+==================
+
+Java
+----
+
+Sqoop written in Java and using version 1.6. You can `download java <http://www.oracle.com/technetwork/java/javase/downloads/index.html>`_ and install. Locate JAVA_HOME to installed directroy, e.g. export JAVA_HOME=/usr/lib/jvm/jdk1.6.0_32.
+
+Maven
+-----
+
+Sqoop uses Maven 3 for building the project. Download `Maven <http://maven.apache.org/download.cgi>`_ and its Installation instructions given in `link <http://maven.apache.org/download.cgi#Maven_Documentation>`_.
+
+Eclipse Setup
+=============
+
+Steps for downloading source code is given in `Building Sqoop2 <BuildingSqoop2.html>`_
+
+Sqoop 2 project has multiple modules where one module is depend on another module for e.g. sqoop 2 client module has sqoop 2 common module dependency. Follow below step for creating eclipse's project and classpath for each module.
+
+::
+
+  //Install all package into local maven repository
+  mvn clean install -DskipTests
+
+  //Adding M2_REPO variable to eclipse workspace
+  mvn eclipse:configure-workspace -Declipse.workspace=<path-to-eclipse-workspace-dir-for-sqoop-2>
+
+  //Eclipse project creation with optional parameters
+  mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
+
+Alternatively, for manually adding M2_REPO classpath variable as maven repository path in eclipse-> window-> Java ->Classpath Variables ->Click "New" ->In new dialog box, input Name as M2_REPO and Path as $HOME/.m2/repository ->click Ok.
+
+On successful execution of above maven commands, Then import the sqoop project modules into eclipse-> File -> Import ->General ->Existing Projects into Workspace-> Click Next-> Browse Sqoop 2 directory ($HOME/git/sqoop2) ->Click Ok ->Import dialog shows multiple projects (sqoop-client, sqoop-common, etc.) -> Select all modules -> click Finish.
+

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_sources/Installation.txt
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_sources/Installation.txt?rev=1471791&view=auto
==============================================================================
--- sqoop/site/trunk/content/resources/docs/1.99.2/_sources/Installation.txt (added)
+++ sqoop/site/trunk/content/resources/docs/1.99.2/_sources/Installation.txt Thu Apr 25 00:20:54 2013
@@ -0,0 +1,88 @@
+.. Licensed to the Apache Software Foundation (ASF) under one or more
+   contributor license agreements.  See the NOTICE file distributed with
+   this work for additional information regarding copyright ownership.
+   The ASF licenses this file to You under the Apache License, Version 2.0
+   (the "License"); you may not use this file except in compliance with
+   the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF lANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+
+=======================================
+Installation
+=======================================
+
+Sqoop ships as one binary package however it's compound from two separate parts - client and server. You need to install server on single node in your cluster. This node will then serve as an entry point for all connecting Sqoop clients. Server acts as a mapreduce client and therefore Hadoop must be installed and configured on machine hosting Sqoop server. Clients can be installed on any arbitrary number of machines. Client is not acting as a mapreduce client and thus you do not need to install Hadoop on nodes that will act only as a Sqoop client.
+
+Server installation
+===================
+
+Copy Sqoop artifact on machine where you want to run Sqoop server. This machine must have installed and configured Hadoop. You don't need to run any Hadoop related services there, however the machine must be able to act as an Hadoop client. You should be able to list a HDFS for example: ::
+
+  hadoop dfs -ls
+
+Sqoop server supports multiple Hadoop versions. However as Hadoop major versions are not compatible with each other, Sqoop have multiple binary artefacts - one for each supported major version of Hadoop. You need to make sure that you're using appropriated binary artifact for your specific Hadoop version. To install Sqoop server decompress appropriate distribution artifact in location at your convenience and change your working directory to this folder. ::
+
+  # Decompress Sqoop distribution tarball
+  tar -xvf sqoop-<version>-bin-hadoop<hadoop-version>.tar.gz
+
+  # Move decompressed content to any location
+  mv sqoop-<version>-bin-hadoop<hadoop version>.tar.gz /usr/lib/sqoop
+
+  # Change working directory
+  cd /usr/lib/sqoop
+
+
+Installing Dependencies
+-----------------------
+
+You need to install Hadoop libraries into Sqoop server war file. Sqoop provides convenience script ``addtowar.sh`` to do so. If you have installed Hadoop in usual location in ``/usr/lib`` and executable ``hadoop`` is in your path, you can use automatic Hadoop installation procedure: ::
+
+  ./bin/addtowar.sh -hadoop-auto
+
+In case that you have Hadoop installed in different location, you will need to manually specify Hadoop version and path to Hadoop libraries. You can use parameter ``-hadoop-version`` for specifying Hadoop major version, we're currently support versions 1.x and 2.x. Path to Hadoop libraries can be specified using ``-hadoop-path`` parameter. In case that your Hadoop libraries are in multiple different folders, you can specify all of them separated by ``:``.  Example of manual installation: ::
+
+  ./bin/addtowar.sh -hadoop-version 2.0 -hadoop-path /usr/lib/hadoop-common:/usr/lib/hadoop-hdfs:/usr/lib/hadoop-yarn
+
+Lastly you might need to install JDBC drivers that are not bundled with Sqoop because of incompatible licenses. You can add any arbitrary java jar file to Sqoop server using script ``addtowar.sh`` with ``-jars`` parameter. Similarly as in case of hadoop path you can enter multiple jars separated with ``:``. Example of installing MySQL JDBC driver to Sqoop server: ::
+
+  ./bin/addtowar.sh -jars /path/to/jar/mysql-connector-java-*-bin.jar
+
+Configuring Server
+------------------
+
+Before starting server you should revise configuration to match your specific environment. Server configuration files are stored in ``server/config`` directory of distributed artifact along side with other configuration files of Tomcat.
+
+File ``sqoop_bootstrap.properties`` specifies which configuration provider should be used for loading configuration for rest of Sqoop server. Default value ``PropertiesConfigurationProvider`` should be sufficient.
+
+
+Second configuration file ``sqoop.properties`` contains remaining configuration properties that can affect Sqoop server. File is very well documented, so check if all configuration properties fits your environment. Default or very little tweaking should be sufficient most common cases.
+
+Server Life Cycle
+-----------------
+
+After installation and configuration you can start Sqoop server with following command: ::
+
+  ./bin/sqoop.sh server start
+
+Similarly you can stop server using following command: ::
+
+  ./bin/sqoop.sh server stop
+
+
+Client installation
+===================
+
+Client do not need extra installation and configuration steps. Just copy Sqoop distribution artifact on target machine and unzip it in desired location. You can start client with following command: ::
+
+  bin/sqoop.sh client
+
+You can find more documentation to Sqoop client in `Command Line Client <CommandLineClient.html>`_ section.
+
+

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_sources/Sqoop5MinutesDemo.txt
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_sources/Sqoop5MinutesDemo.txt?rev=1471791&view=auto
==============================================================================
--- sqoop/site/trunk/content/resources/docs/1.99.2/_sources/Sqoop5MinutesDemo.txt (added)
+++ sqoop/site/trunk/content/resources/docs/1.99.2/_sources/Sqoop5MinutesDemo.txt Thu Apr 25 00:20:54 2013
@@ -0,0 +1,159 @@
+.. Licensed to the Apache Software Foundation (ASF) under one or more
+   contributor license agreements.  See the NOTICE file distributed with
+   this work for additional information regarding copyright ownership.
+   The ASF licenses this file to You under the Apache License, Version 2.0
+   (the "License"); you may not use this file except in compliance with
+   the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+
+====================
+Sqoop 5 Minutes Demo
+====================
+
+This page will walk you through basic usage of Sqoop. You need to have installed and configured Sqoop server and client in order to follow this guide. Installation procedure is described on `Installation page <Installation.html>`_. Please note that precise output shown in this page might differ from your as Sqoop develops. All major information should however remain the same.
+
+Sqoop is using numerical identifiers to identify various meta data structures (connectors, connections, jobs). Each meta data structures have it's own pool of identifiers and thus it's perfectly valid when Sqoop have connector with id 1, connection with id 1 and job with id 1 at the same time.
+
+Starting Client
+===============
+
+Start client in interactive mode using following command: ::
+
+  ./bin/sqoop.sh client
+
+Configure client to use your Sqoop server: ::
+
+  sqoop:000> set server --host your.host.com --port 12000 --webapp sqoop
+
+Verify that connection is working by simple version checking: ::
+
+  sqoop:000> show version --all
+  Server version:
+    Sqoop 2.0.0-SNAPSHOT revision Unknown
+    Compiled by jarcec on Wed Nov 21 16:15:51 PST 2012
+  Client version:
+    Sqoop 2.0.0-SNAPSHOT revision Unknown
+    Compiled by jarcec on Wed Nov 21 16:15:51 PST 2012
+  Protocol version:
+    [1]
+
+You should received similar output as shown describing versions of both your client and remote server as well as negotiated protocol version.
+
+Creating Connection Object
+==========================
+
+Check what connectors are available on your Sqoop server: ::
+
+  sqoop:000> show connector --all
+  1 connector(s) to show:
+  Connector with id 1:
+    Name: generic-jdbc-connector
+    Class: org.apache.sqoop.connector.jdbc.GenericJdbcConnector
+    Supported job types: [EXPORT, IMPORT]
+  ...
+
+Our example contains one connector called ``generic-jdbc-connector``. This is basic connector that is relying on Java JDBC interface for doing data transfers. It should work on most common databases that are providing JDBC drivers. Please note that you must install JDBC drivers separately. They are not bundled in Sqoop due to incompatible licenses.
+
+Generic JDBC Connector have in our example id 1 and we will use this value to create new connection object for this connector: ::
+
+  sqoop:000> create connection --cid 1
+  Creating connection for connector with id 1
+  Please fill following values to create new connection object
+  Name: First connection
+
+  Configuration configuration
+  JDBC Driver Class: com.mysql.jdbc.Driver
+  JDBC Connection String: jdbc:mysql://mysql.server/database
+  Username: sqoop
+  Password: *****
+  JDBC Connection Properties:
+  There are currently 0 values in the map:
+  entry#
+
+  Security related configuration options
+  Max connections: 0
+  New connection was successfully created with validation status FINE and persistent id 1
+
+Our new connection object was created with assigned id 1.
+
+Creating Job Object
+===================
+
+Job objects have multiple types and each connector might not support all of them. Generic JDBC Connector supports job types ``import`` (importing data to Hadoop ecosystem) and ``export`` (exporting data from Hadoop ecosystem). List of supported job types for each connector might be seen in the output of ``show connector`` command: ::
+
+  sqoop:000> show connector --all
+  ...
+    Name: generic-jdbc-connector
+  ...
+    Supported job types: [EXPORT, IMPORT]
+  ...
+
+Create import job for Connection object created in previous section: ::
+
+  sqoop:000> create job --xid 1 --type import
+  Creating job for connection with id 1
+  Please fill following values to create new job object
+  Name: First job
+
+  Database configuration
+  Table name: users
+  Table SQL statement:
+  Table column names:
+  Partition column name:
+  Boundary query:
+
+  Output configuration
+  Storage type:
+    0 : HDFS
+  Choose: 0
+  Output directory: /user/jarcec/users
+  New job was successfully created with validation status FINE and persistent id 1
+
+Our new job object was created with assigned id 1.
+
+Moving Data
+===========
+
+When all meta data objects are in place we can start moving data around. You can submit Hadoop job using ``submission start`` command: ::
+
+  sqoop:000> submission start --jid 1
+  Submission details
+  Job id: 1
+  Status: BOOTING
+  Creation date: 2012-12-23 13:20:34 PST
+  Last update date: 2012-12-23 13:20:34 PST
+  External Id: job_1353136146286_0004
+          http://hadoop.cluster.com:8088/proxy/application_1353136146286_0004/
+  Progress: Progress is not available
+
+You can iteratively check your running job status with ``submission status`` command: ::
+
+  sqoop:000> submission status --jid 1
+  Submission details
+  Job id: 1
+  Status: RUNNING
+  Creation date: 2012-12-23 13:21:45 PST
+  Last update date: 2012-12-23 13:21:56 PST
+  External Id: job_1353136146286_0005
+          http://hadoop.cluster.com:8088/proxy/application_1353136146286_0004/
+  Progress: 0.00 %
+
+And finally you can stop running job at any time using ``submission stop`` command: ::
+
+  sqoop:000> submission stop --jid 1
+  Submission details
+  Job id: 1
+  Status: FAILED
+  Creation date: 2012-12-23 13:22:39 PST
+  Last update date: 2012-12-23 13:22:42 PST
+  External Id: job_1353136146286_0006
+          http://hadoop.cluster.com:8088/proxy/application_1353136146286_0004/
+

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_sources/index.txt
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_sources/index.txt?rev=1471791&view=auto
==============================================================================
--- sqoop/site/trunk/content/resources/docs/1.99.2/_sources/index.txt (added)
+++ sqoop/site/trunk/content/resources/docs/1.99.2/_sources/index.txt Thu Apr 25 00:20:54 2013
@@ -0,0 +1,63 @@
+.. Licensed to the Apache Software Foundation (ASF) under one or more
+   contributor license agreements.  See the NOTICE file distributed with
+   this work for additional information regarding copyright ownership.
+   The ASF licenses this file to You under the Apache License, Version 2.0
+   (the "License"); you may not use this file except in compliance with
+   the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+
+=======================================
+Apache Sqoop documentation
+=======================================
+
+Apache Sqoop is a tool designed for efficiently transferring bulk data between Apache Hadoop and structured datastores such as relational databases.
+
+License
+-------
+
+::
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+        http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+
+Overview
+--------
+
+- `Download Apache Sqoop <http://www.apache.org/dyn/closer.cgi/sqoop>`_
+- `Sqoop Wiki <https://cwiki.apache.org/confluence/display/SQOOP/Home>`_
+- `Sqoop Issue Tracking (JIRA) <https://issues.apache.org/jira/browse/SQOOP>`_
+- `Sqoop Source Code <https://git-wip-us.apache.org/repos/asf?p=sqoop.git;a=summary>`_
+
+User Documentation
+------------------
+
+- `Installation <Installation.html>`_
+- `5 Minutes Demo <Sqoop5MinutesDemo.html>`_
+- `Command Line Client <CommandLineClient.html>`_
+
+Developer Guide
+---------------
+
+- `Building Sqoop2 <BuildingSqoop2.html>`_
+- `Development Environment Setup <DevEnv.html>`_
+- `Java Client API Guide <ClientAPI.html>`_

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_static/ajax-loader.gif
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_static/ajax-loader.gif?rev=1471791&view=auto
==============================================================================
Binary file - no diff available.

Propchange: sqoop/site/trunk/content/resources/docs/1.99.2/_static/ajax-loader.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_static/alert_info_32.png
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_static/alert_info_32.png?rev=1471791&view=auto
==============================================================================
Binary file - no diff available.

Propchange: sqoop/site/trunk/content/resources/docs/1.99.2/_static/alert_info_32.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_static/alert_warning_32.png
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_static/alert_warning_32.png?rev=1471791&view=auto
==============================================================================
Binary file - no diff available.

Propchange: sqoop/site/trunk/content/resources/docs/1.99.2/_static/alert_warning_32.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_static/basic.css
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_static/basic.css?rev=1471791&view=auto
==============================================================================
--- sqoop/site/trunk/content/resources/docs/1.99.2/_static/basic.css (added)
+++ sqoop/site/trunk/content/resources/docs/1.99.2/_static/basic.css Thu Apr 25 00:20:54 2013
@@ -0,0 +1,540 @@
+/*
+ * basic.css
+ * ~~~~~~~~~
+ *
+ * Sphinx stylesheet -- basic theme.
+ *
+ * :copyright: Copyright 2007-2011 by the Sphinx team, see AUTHORS.
+ * :license: BSD, see LICENSE for details.
+ *
+ */
+
+/* -- main layout ----------------------------------------------------------- */
+
+div.clearer {
+    clear: both;
+}
+
+/* -- relbar ---------------------------------------------------------------- */
+
+div.related {
+    width: 100%;
+    font-size: 90%;
+}
+
+div.related h3 {
+    display: none;
+}
+
+div.related ul {
+    margin: 0;
+    padding: 0 0 0 10px;
+    list-style: none;
+}
+
+div.related li {
+    display: inline;
+}
+
+div.related li.right {
+    float: right;
+    margin-right: 5px;
+}
+
+/* -- sidebar --------------------------------------------------------------- */
+
+div.sphinxsidebarwrapper {
+    padding: 10px 5px 0 10px;
+}
+
+div.sphinxsidebar {
+    float: left;
+    width: 230px;
+    margin-left: -100%;
+    font-size: 90%;
+}
+
+div.sphinxsidebar ul {
+    list-style: none;
+}
+
+div.sphinxsidebar ul ul,
+div.sphinxsidebar ul.want-points {
+    margin-left: 20px;
+    list-style: square;
+}
+
+div.sphinxsidebar ul ul {
+    margin-top: 0;
+    margin-bottom: 0;
+}
+
+div.sphinxsidebar form {
+    margin-top: 10px;
+}
+
+div.sphinxsidebar input {
+    border: 1px solid #98dbcc;
+    font-family: sans-serif;
+    font-size: 1em;
+}
+
+div.sphinxsidebar input[type="text"] {
+    width: 170px;
+}
+
+div.sphinxsidebar input[type="submit"] {
+    width: 30px;
+}
+
+img {
+    border: 0;
+}
+
+/* -- search page ----------------------------------------------------------- */
+
+ul.search {
+    margin: 10px 0 0 20px;
+    padding: 0;
+}
+
+ul.search li {
+    padding: 5px 0 5px 20px;
+    background-image: url(file.png);
+    background-repeat: no-repeat;
+    background-position: 0 7px;
+}
+
+ul.search li a {
+    font-weight: bold;
+}
+
+ul.search li div.context {
+    color: #888;
+    margin: 2px 0 0 30px;
+    text-align: left;
+}
+
+ul.keywordmatches li.goodmatch a {
+    font-weight: bold;
+}
+
+/* -- index page ------------------------------------------------------------ */
+
+table.contentstable {
+    width: 90%;
+}
+
+table.contentstable p.biglink {
+    line-height: 150%;
+}
+
+a.biglink {
+    font-size: 1.3em;
+}
+
+span.linkdescr {
+    font-style: italic;
+    padding-top: 5px;
+    font-size: 90%;
+}
+
+/* -- general index --------------------------------------------------------- */
+
+table.indextable {
+    width: 100%;
+}
+
+table.indextable td {
+    text-align: left;
+    vertical-align: top;
+}
+
+table.indextable dl, table.indextable dd {
+    margin-top: 0;
+    margin-bottom: 0;
+}
+
+table.indextable tr.pcap {
+    height: 10px;
+}
+
+table.indextable tr.cap {
+    margin-top: 10px;
+    background-color: #f2f2f2;
+}
+
+img.toggler {
+    margin-right: 3px;
+    margin-top: 3px;
+    cursor: pointer;
+}
+
+div.modindex-jumpbox {
+    border-top: 1px solid #ddd;
+    border-bottom: 1px solid #ddd;
+    margin: 1em 0 1em 0;
+    padding: 0.4em;
+}
+
+div.genindex-jumpbox {
+    border-top: 1px solid #ddd;
+    border-bottom: 1px solid #ddd;
+    margin: 1em 0 1em 0;
+    padding: 0.4em;
+}
+
+/* -- general body styles --------------------------------------------------- */
+
+a.headerlink {
+    visibility: hidden;
+}
+
+h1:hover > a.headerlink,
+h2:hover > a.headerlink,
+h3:hover > a.headerlink,
+h4:hover > a.headerlink,
+h5:hover > a.headerlink,
+h6:hover > a.headerlink,
+dt:hover > a.headerlink {
+    visibility: visible;
+}
+
+div.body p.caption {
+    text-align: inherit;
+}
+
+div.body td {
+    text-align: left;
+}
+
+.field-list ul {
+    padding-left: 1em;
+}
+
+.first {
+    margin-top: 0 !important;
+}
+
+p.rubric {
+    margin-top: 30px;
+    font-weight: bold;
+}
+
+img.align-left, .figure.align-left, object.align-left {
+    clear: left;
+    float: left;
+    margin-right: 1em;
+}
+
+img.align-right, .figure.align-right, object.align-right {
+    clear: right;
+    float: right;
+    margin-left: 1em;
+}
+
+img.align-center, .figure.align-center, object.align-center {
+  display: block;
+  margin-left: auto;
+  margin-right: auto;
+}
+
+.align-left {
+    text-align: left;
+}
+
+.align-center {
+    text-align: center;
+}
+
+.align-right {
+    text-align: right;
+}
+
+/* -- sidebars -------------------------------------------------------------- */
+
+div.sidebar {
+    margin: 0 0 0.5em 1em;
+    border: 1px solid #ddb;
+    padding: 7px 7px 0 7px;
+    background-color: #ffe;
+    width: 40%;
+    float: right;
+}
+
+p.sidebar-title {
+    font-weight: bold;
+}
+
+/* -- topics ---------------------------------------------------------------- */
+
+div.topic {
+    border: 1px solid #ccc;
+    padding: 7px 7px 0 7px;
+    margin: 10px 0 10px 0;
+}
+
+p.topic-title {
+    font-size: 1.1em;
+    font-weight: bold;
+    margin-top: 10px;
+}
+
+/* -- admonitions ----------------------------------------------------------- */
+
+div.admonition {
+    margin-top: 10px;
+    margin-bottom: 10px;
+    padding: 7px;
+}
+
+div.admonition dt {
+    font-weight: bold;
+}
+
+div.admonition dl {
+    margin-bottom: 0;
+}
+
+p.admonition-title {
+    margin: 0px 10px 5px 0px;
+    font-weight: bold;
+}
+
+div.body p.centered {
+    text-align: center;
+    margin-top: 25px;
+}
+
+/* -- tables ---------------------------------------------------------------- */
+
+table.docutils {
+    border: 0;
+    border-collapse: collapse;
+}
+
+table.docutils td, table.docutils th {
+    padding: 1px 8px 1px 5px;
+    border-top: 0;
+    border-left: 0;
+    border-right: 0;
+    border-bottom: 1px solid #aaa;
+}
+
+table.field-list td, table.field-list th {
+    border: 0 !important;
+}
+
+table.footnote td, table.footnote th {
+    border: 0 !important;
+}
+
+th {
+    text-align: left;
+    padding-right: 5px;
+}
+
+table.citation {
+    border-left: solid 1px gray;
+    margin-left: 1px;
+}
+
+table.citation td {
+    border-bottom: none;
+}
+
+/* -- other body styles ----------------------------------------------------- */
+
+ol.arabic {
+    list-style: decimal;
+}
+
+ol.loweralpha {
+    list-style: lower-alpha;
+}
+
+ol.upperalpha {
+    list-style: upper-alpha;
+}
+
+ol.lowerroman {
+    list-style: lower-roman;
+}
+
+ol.upperroman {
+    list-style: upper-roman;
+}
+
+dl {
+    margin-bottom: 15px;
+}
+
+dd p {
+    margin-top: 0px;
+}
+
+dd ul, dd table {
+    margin-bottom: 10px;
+}
+
+dd {
+    margin-top: 3px;
+    margin-bottom: 10px;
+    margin-left: 30px;
+}
+
+dt:target, .highlighted {
+    background-color: #fbe54e;
+}
+
+dl.glossary dt {
+    font-weight: bold;
+    font-size: 1.1em;
+}
+
+.field-list ul {
+    margin: 0;
+    padding-left: 1em;
+}
+
+.field-list p {
+    margin: 0;
+}
+
+.refcount {
+    color: #060;
+}
+
+.optional {
+    font-size: 1.3em;
+}
+
+.versionmodified {
+    font-style: italic;
+}
+
+.system-message {
+    background-color: #fda;
+    padding: 5px;
+    border: 3px solid red;
+}
+
+.footnote:target  {
+    background-color: #ffa;
+}
+
+.line-block {
+    display: block;
+    margin-top: 1em;
+    margin-bottom: 1em;
+}
+
+.line-block .line-block {
+    margin-top: 0;
+    margin-bottom: 0;
+    margin-left: 1.5em;
+}
+
+.guilabel, .menuselection {
+    font-family: sans-serif;
+}
+
+.accelerator {
+    text-decoration: underline;
+}
+
+.classifier {
+    font-style: oblique;
+}
+
+abbr, acronym {
+    border-bottom: dotted 1px;
+    cursor: help;
+}
+
+/* -- code displays --------------------------------------------------------- */
+
+pre {
+    overflow: auto;
+    overflow-y: hidden;  /* fixes display issues on Chrome browsers */
+}
+
+td.linenos pre {
+    padding: 5px 0px;
+    border: 0;
+    background-color: transparent;
+    color: #aaa;
+}
+
+table.highlighttable {
+    margin-left: 0.5em;
+}
+
+table.highlighttable td {
+    padding: 0 0.5em 0 0.5em;
+}
+
+tt.descname {
+    background-color: transparent;
+    font-weight: bold;
+    font-size: 1.2em;
+}
+
+tt.descclassname {
+    background-color: transparent;
+}
+
+tt.xref, a tt {
+    background-color: transparent;
+    font-weight: bold;
+}
+
+h1 tt, h2 tt, h3 tt, h4 tt, h5 tt, h6 tt {
+    background-color: transparent;
+}
+
+.viewcode-link {
+    float: right;
+}
+
+.viewcode-back {
+    float: right;
+    font-family: sans-serif;
+}
+
+div.viewcode-block:target {
+    margin: -1px -10px;
+    padding: 0 10px;
+}
+
+/* -- math display ---------------------------------------------------------- */
+
+img.math {
+    vertical-align: middle;
+}
+
+div.body div.math p {
+    text-align: center;
+}
+
+span.eqno {
+    float: right;
+}
+
+/* -- printout stylesheet --------------------------------------------------- */
+
+@media print {
+    div.document,
+    div.documentwrapper,
+    div.bodywrapper {
+        margin: 0 !important;
+        width: 100%;
+    }
+
+    div.sphinxsidebar,
+    div.related,
+    div.footer,
+    #top-link {
+        display: none;
+    }
+}
\ No newline at end of file

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_static/bg-page.png
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_static/bg-page.png?rev=1471791&view=auto
==============================================================================
Binary file - no diff available.

Propchange: sqoop/site/trunk/content/resources/docs/1.99.2/_static/bg-page.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_static/bullet_orange.png
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_static/bullet_orange.png?rev=1471791&view=auto
==============================================================================
Binary file - no diff available.

Propchange: sqoop/site/trunk/content/resources/docs/1.99.2/_static/bullet_orange.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_static/comment-bright.png
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_static/comment-bright.png?rev=1471791&view=auto
==============================================================================
Binary file - no diff available.

Propchange: sqoop/site/trunk/content/resources/docs/1.99.2/_static/comment-bright.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_static/comment-close.png
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_static/comment-close.png?rev=1471791&view=auto
==============================================================================
Binary file - no diff available.

Propchange: sqoop/site/trunk/content/resources/docs/1.99.2/_static/comment-close.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: sqoop/site/trunk/content/resources/docs/1.99.2/_static/comment.png
URL: http://svn.apache.org/viewvc/sqoop/site/trunk/content/resources/docs/1.99.2/_static/comment.png?rev=1471791&view=auto
==============================================================================
Binary file - no diff available.

Propchange: sqoop/site/trunk/content/resources/docs/1.99.2/_static/comment.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream



Mime
View raw message