Resync 0.10.1 documentation

Project: http://git-wip-us.apache.org/repos/asf/kafka-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/kafka-site/commit/b2433ce9
Tree: http://git-wip-us.apache.org/repos/asf/kafka-site/tree/b2433ce9
Diff: http://git-wip-us.apache.org/repos/asf/kafka-site/diff/b2433ce9

Branch: refs/heads/asf-site
Commit: b2433ce997e09cff4e5043c9965578536a811682
Parents: 20f2876
Author: Jason Gustafson <ja...@confluent.io>
Authored: Mon Oct 10 20:14:57 2016 -0700
Committer: Jason Gustafson <ja...@confluent.io>
Committed: Mon Oct 10 20:14:57 2016 -0700

----------------------------------------------------------------------
 0101/api.html                       |   2 +-
 0101/configuration.html             |   2 +-
 0101/connect.html                   |   4 +-
 0101/design.html                    | 378 +++++++++++++++++++++++--------
 0101/documentation.html             |   1 -
 0101/generated/connect_config.html  |   6 +-
 0101/generated/consumer_config.html |   4 +-
 0101/generated/kafka_config.html    |   4 +-
 0101/generated/producer_config.html |   6 +-
 0101/generated/topic_config.html    |   4 +-
 0101/images/kafka-apis.png          | Bin 0 -> 86640 bytes
 0101/images/log_consumer.png        | Bin 0 -> 139658 bytes
 0101/implementation.html            |   2 +-
 0101/introduction.html              |  12 +-
 0101/ops.html                       |  11 +-
 0101/quickstart.html                |   8 +-
 0101/security.html                  |   6 +-
 0101/upgrade.html                   |   4 +-
 18 files changed, 318 insertions(+), 136 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka-site/blob/b2433ce9/0101/api.html
----------------------------------------------------------------------
diff --git a/0101/api.html b/0101/api.html
index d7da07f..2a24a32 100644
--- a/0101/api.html
+++ b/0101/api.html
@@ -89,6 +89,6 @@ Those who want to implement custom connectors can see the <a 
href="/0101/javadoc
 <h3><a id="legacyapis" href="#streamsapi">Legacy APIs</a></h3>
 
 <p>
-A more limited legacy producer and consumer api is also included in Kafka. 
These old Scala APIs are deprecated and only still available for compatability 
purposes. Information on them can be found here <a 
href="/081/documentation.html#producerapi"  title="Kafka 0.8.1 Docs">
+A more limited legacy producer and consumer api is also included in Kafka. 
These old Scala APIs are deprecated and only still available for compatibility 
purposes. Information on them can be found here <a 
href="/081/documentation.html#producerapi"  title="Kafka 0.8.1 Docs">
 here</a>.
 </p>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/b2433ce9/0101/configuration.html
----------------------------------------------------------------------
diff --git a/0101/configuration.html b/0101/configuration.html
index 35f1475..53343fa 100644
--- a/0101/configuration.html
+++ b/0101/configuration.html
@@ -101,7 +101,7 @@ The essential old consumer configurations are the following:
       <td colspan="1"></td>
           <td>Specifies the ZooKeeper connection string in the form 
<code>hostname:port</code> where host and port are the host and port of a 
ZooKeeper server. To allow connecting through other ZooKeeper nodes when that 
ZooKeeper machine is down you can also specify multiple hosts in the form 
<code>hostname1:port1,hostname2:port2,hostname3:port3</code>.
         <p>
-    The server may also have a ZooKeeper chroot path as part of it's ZooKeeper 
connection string which puts its data under some path in the global ZooKeeper 
namespace. If so the consumer should use the same chroot path in its connection 
string. For example to give a chroot path of <code>/chroot/path</code> you 
would give the connection string as  
<code>hostname1:port1,hostname2:port2,hostname3:port3/chroot/path</code>.</td>
+    The server may also have a ZooKeeper chroot path as part of its ZooKeeper 
connection string which puts its data under some path in the global ZooKeeper 
namespace. If so the consumer should use the same chroot path in its connection 
string. For example to give a chroot path of <code>/chroot/path</code> you 
would give the connection string as  
<code>hostname1:port1,hostname2:port2,hostname3:port3/chroot/path</code>.</td>
     </tr>
     <tr>
       <td>consumer.id</td>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/b2433ce9/0101/connect.html
----------------------------------------------------------------------
diff --git a/0101/connect.html b/0101/connect.html
index d8431a8..d3fc7d7 100644
--- a/0101/connect.html
+++ b/0101/connect.html
@@ -101,11 +101,11 @@ For any other options, you should consult the 
documentation for the connector.
 
 <h4><a id="connect_rest" href="#connect_rest">REST API</a></h4>
 
-Since Kafka Connect is intended to be run as a service, it also provides a 
REST API for managing connectors. By default this service runs on port 8083. 
The following are the currently supported endpoints:
+Since Kafka Connect is intended to be run as a service, it also provides a 
REST API for managing connectors. By default, this service runs on port 8083. 
The following are the currently supported endpoints:
 
 <ul>
     <li><code>GET /connectors</code> - return a list of active connectors</li>
-    <li><code>POST /connectors</code> - create a new connector; the request 
body should be a JSON object containing a string <code>name</code> field and a 
object <code>config</code> field with the connector configuration 
parameters</li>
+    <li><code>POST /connectors</code> - create a new connector; the request 
body should be a JSON object containing a string <code>name</code> field and an 
object <code>config</code> field with the connector configuration 
parameters</li>
     <li><code>GET /connectors/{name}</code> - get information about a specific 
connector</li>
     <li><code>GET /connectors/{name}/config</code> - get the configuration 
parameters for a specific connector</li>
     <li><code>PUT /connectors/{name}/config</code> - update the configuration 
parameters for a specific connector</li>

Reply via email to