You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2013/10/11 20:19:16 UTC
svn commit: r882191 - in /websites/production/camel/content:
book-component-appendix.html book-in-one-page.html cache/main.pageCache
hdfs.html
Author: buildbot
Date: Fri Oct 11 18:19:16 2013
New Revision: 882191
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-component-appendix.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/hdfs.html
Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Fri Oct 11 18:19:16 2013
@@ -6724,14 +6724,14 @@ The path is treated in the following way
<p>BYTES is also used with everything else, for example, in Camel a file is sent around as an InputStream, int this case is written in a sequence file or a map file as a sequence of bytes.</p>
<h3><a shape="rect" name="BookComponentAppendix-SplittingStrategy"></a>Splitting Strategy</h3>
-<p>In the current version of Hadoop opening a file in append mode is disabled since it's not enough reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p>
+<p>In the current version of Hadoop opening a file in append mode is disabled since it's not very reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p>
<ul><li>If the split strategy option has been defined, the actual file name will become a directory name and a <file name>/seg0 will be initially created.</li><li>Every time a splitting condition is met a new file is created with name <original file name>/segN where N is 1, 2, 3, etc.<br clear="none">
-The splitStrategy option is defined as a string with the following syntax:<br clear="none">
+The splitStrategy option is defined as a string with the following syntax:<br clear="none">
splitStrategy=<ST>:<value>,<ST>:<value>,*</li></ul>
<p>where <ST> can be:</p>
-<ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than <value></li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than <value></li><li>IDLE a new file is created, and the old is closed when no writing happened in the last <value> milliseconds</li></ul>
+<ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than <value></li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than <value></li><li>IDLE a new file is created, and the old is closed when no writing happened in the last <value> milliseconds</li></ul>
<p>for example:</p>
@@ -6746,13 +6746,13 @@ hdfs://localhost/tmp/simple-file?splitSt
<h3><a shape="rect" name="BookComponentAppendix-Controllingtoclosefilestream"></a>Controlling to close file stream</h3>
<p><b>Available as of Camel 2.10.4</b></p>
-<p>When using the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> producer <b>without</b> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicit close the stream later. For that you can use the header <tt>HdfsConstants.HDFS_CLOSE</tt> (value = <tt>"CamelHdfsClose"</tt>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p>
+<p>When using the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> producer <b>without</b> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicitly close the stream later. For that you can use the header <tt>HdfsConstants.HDFS_CLOSE</tt> (value = <tt>"CamelHdfsClose"</tt>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p>
-<p>Notice this does not apply if you use a split strategy, as there is varios strategy that control when the stream is closed.</p>
+<p>Notice this does not apply if you use a split strategy, as there are various strategies that can control when the stream is closed.</p>
<h3><a shape="rect" name="BookComponentAppendix-UsingthiscomponentinOSGi"></a>Using this component in OSGi</h3>
-<p>This component is fully functional in an OSGi environment however, it requires some actions from the user. Hadoop uses the thread context class loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p>
+<p>This component is fully functional in an OSGi environment, however, it requires some actions from the user. Hadoop uses the thread context class loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p>
<h2><a shape="rect" name="BookComponentAppendix-HibernateComponent"></a>Hibernate Component</h2>
<p>The <b>hibernate:</b> component allows you to work with databases using Hibernate as the object relational mapping technology to map POJOs to database tables. The <b>camel-hibernate</b> library is provided by the <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">Camel Extra</a> project which hosts all *GPL related components for Camel.</p>
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Fri Oct 11 18:19:16 2013
@@ -28201,14 +28201,14 @@ The path is treated in the following way
<p>BYTES is also used with everything else, for example, in Camel a file is sent around as an InputStream, int this case is written in a sequence file or a map file as a sequence of bytes.</p>
<h3><a shape="rect" name="BookInOnePage-SplittingStrategy"></a>Splitting Strategy</h3>
-<p>In the current version of Hadoop opening a file in append mode is disabled since it's not enough reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p>
+<p>In the current version of Hadoop opening a file in append mode is disabled since it's not very reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p>
<ul><li>If the split strategy option has been defined, the actual file name will become a directory name and a <file name>/seg0 will be initially created.</li><li>Every time a splitting condition is met a new file is created with name <original file name>/segN where N is 1, 2, 3, etc.<br clear="none">
-The splitStrategy option is defined as a string with the following syntax:<br clear="none">
+The splitStrategy option is defined as a string with the following syntax:<br clear="none">
splitStrategy=<ST>:<value>,<ST>:<value>,*</li></ul>
<p>where <ST> can be:</p>
-<ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than <value></li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than <value></li><li>IDLE a new file is created, and the old is closed when no writing happened in the last <value> milliseconds</li></ul>
+<ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than <value></li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than <value></li><li>IDLE a new file is created, and the old is closed when no writing happened in the last <value> milliseconds</li></ul>
<p>for example:</p>
@@ -28223,13 +28223,13 @@ hdfs://localhost/tmp/simple-file?splitSt
<h3><a shape="rect" name="BookInOnePage-Controllingtoclosefilestream"></a>Controlling to close file stream</h3>
<p><b>Available as of Camel 2.10.4</b></p>
-<p>When using the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> producer <b>without</b> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicit close the stream later. For that you can use the header <tt>HdfsConstants.HDFS_CLOSE</tt> (value = <tt>"CamelHdfsClose"</tt>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p>
+<p>When using the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> producer <b>without</b> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicitly close the stream later. For that you can use the header <tt>HdfsConstants.HDFS_CLOSE</tt> (value = <tt>"CamelHdfsClose"</tt>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p>
-<p>Notice this does not apply if you use a split strategy, as there is varios strategy that control when the stream is closed.</p>
+<p>Notice this does not apply if you use a split strategy, as there are various strategies that can control when the stream is closed.</p>
<h3><a shape="rect" name="BookInOnePage-UsingthiscomponentinOSGi"></a>Using this component in OSGi</h3>
-<p>This component is fully functional in an OSGi environment however, it requires some actions from the user. Hadoop uses the thread context class loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p>
+<p>This component is fully functional in an OSGi environment, however, it requires some actions from the user. Hadoop uses the thread context class loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p>
<h2><a shape="rect" name="BookInOnePage-HibernateComponent"></a>Hibernate Component</h2>
<p>The <b>hibernate:</b> component allows you to work with databases using Hibernate as the object relational mapping technology to map POJOs to database tables. The <b>camel-hibernate</b> library is provided by the <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">Camel Extra</a> project which hosts all *GPL related components for Camel.</p>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/hdfs.html
==============================================================================
--- websites/production/camel/content/hdfs.html (original)
+++ websites/production/camel/content/hdfs.html Fri Oct 11 18:19:16 2013
@@ -128,14 +128,14 @@ The path is treated in the following way
<p>BYTES is also used with everything else, for example, in Camel a file is sent around as an InputStream, int this case is written in a sequence file or a map file as a sequence of bytes.</p>
<h3><a shape="rect" name="HDFS-SplittingStrategy"></a>Splitting Strategy</h3>
-<p>In the current version of Hadoop opening a file in append mode is disabled since it's not enough reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p>
+<p>In the current version of Hadoop opening a file in append mode is disabled since it's not very reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p>
<ul><li>If the split strategy option has been defined, the actual file name will become a directory name and a <file name>/seg0 will be initially created.</li><li>Every time a splitting condition is met a new file is created with name <original file name>/segN where N is 1, 2, 3, etc.<br clear="none">
-The splitStrategy option is defined as a string with the following syntax:<br clear="none">
+The splitStrategy option is defined as a string with the following syntax:<br clear="none">
splitStrategy=<ST>:<value>,<ST>:<value>,*</li></ul>
<p>where <ST> can be:</p>
-<ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than <value></li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than <value></li><li>IDLE a new file is created, and the old is closed when no writing happened in the last <value> milliseconds</li></ul>
+<ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than <value></li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than <value></li><li>IDLE a new file is created, and the old is closed when no writing happened in the last <value> milliseconds</li></ul>
<p>for example:</p>
@@ -150,13 +150,13 @@ hdfs://localhost/tmp/simple-file?splitSt
<h3><a shape="rect" name="HDFS-Controllingtoclosefilestream"></a>Controlling to close file stream</h3>
<p><b>Available as of Camel 2.10.4</b></p>
-<p>When using the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> producer <b>without</b> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicit close the stream later. For that you can use the header <tt>HdfsConstants.HDFS_CLOSE</tt> (value = <tt>"CamelHdfsClose"</tt>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p>
+<p>When using the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> producer <b>without</b> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicitly close the stream later. For that you can use the header <tt>HdfsConstants.HDFS_CLOSE</tt> (value = <tt>"CamelHdfsClose"</tt>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p>
-<p>Notice this does not apply if you use a split strategy, as there is varios strategy that control when the stream is closed.</p>
+<p>Notice this does not apply if you use a split strategy, as there are various strategies that can control when the stream is closed.</p>
<h3><a shape="rect" name="HDFS-UsingthiscomponentinOSGi"></a>Using this component in OSGi</h3>
-<p>This component is fully functional in an OSGi environment however, it requires some actions from the user. Hadoop uses the thread context class loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p></div>
+<p>This component is fully functional in an OSGi environment, however, it requires some actions from the user. Hadoop uses the thread context class loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p></div>
</td>
<td valign="top">
<div class="navigation">