From 38bea385bad265440803429e701c5d5edb825306 Mon Sep 17 00:00:00 2001 From: Dave Syer Date: Wed, 6 Jul 2016 07:54:46 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- spring-cloud.html | 37 ++++++++++++++++++++++++++----------- 1 file changed, 26 insertions(+), 11 deletions(-) diff --git a/spring-cloud.html b/spring-cloud.html index 64107cbc..fbed5080 100644 --- a/spring-cloud.html +++ b/spring-cloud.html @@ -2058,6 +2058,21 @@ search).

+

Version Control Backend Filesystem Use

+
+ + + + + +
+
Warning
+		 +With VCS based backends (git, svn) files are checked out or cloned to the local filesystem. By default they are put in the system temporary directory with a prefix of config-repo-. On linux, for example it could be /tmp/config-repo-<randomid>. Some operating systems routinely clean out temporary directories. This can lead to unexpected behaviour such as missing properties. To avoid this problem, change the directory Config Server uses, by setting spring.cloud.config.server.git.basedir or spring.cloud.config.server.svn.basedir to a directory that does not reside in the system temp structure. +
+
+
+

File System Backend

There is also a "native" profile in the Config Server that doesn’t use @@ -2559,7 +2574,7 @@ as YAML or Java properties by adding a suffix to the resource path (".yml", ".yaml" or ".properties"). This can be useful for consumption by applications that do not care about the structure of the JSON endpoints, or the extra metadata they provide, for example an -application that is not using Spring might benefit fro mthe simplicity +application that is not using Spring might benefit from the simplicity of this approach.

@@ -3728,7 +3743,7 @@ for details on the properties available.

Note
-by default Spring Cloud allows Turbine to use the host and port to allow multiple processes per host, per cluster. If you want the native Netflix behaviour built into Turbine that does not allow multiple processes per host, per cluster (the key to the instance id is the hostname), then set the property turbine.combineHostPort=false. +by default the native Netflix behaviour built into Turbine does not allow multiple processes per host, per cluster (the key to the instance id is the hostname). Spring Cloud generalizes this a bit, allowing the host and port to be used as the key, but only if you set the property turbine.combineHostPort=true @@ -5585,8 +5600,8 @@ When doing this, different instances of an application are placed in a competing

Spring Cloud Stream models this behavior through the concept of a consumer group. (Spring Cloud Stream consumer groups are similar to and inspired by Kafka consumer groups.) -Each consumer binding can use the spring.cloud.stream.bindings.<channelName>.group property to specify a group name. -For the consumers shown in the following figure, this property would be set as spring.cloud.stream.bindings.<channelName>.group=hdfsWrite or spring.cloud.stream.bindings.<channelName>.group=average.

+Each consumer binding can use the spring.cloud.stream.bindings.input.group property to specify a group name. +For the consumers shown in the following figure, this property would be set as spring.cloud.stream.bindings.input.group=hdfsWrite or spring.cloud.stream.bindings.input.group=average.

@@ -6325,7 +6340,7 @@ The key represents an identifying name for the binder implementation, whereas th

Binder selection can either be performed globally, using the spring.cloud.stream.defaultBinder property (e.g., spring.cloud.stream.defaultBinder=rabbit) or individually, by configuring the binder on each channel binding. -For instance, a processor application (that has channels with the names input and output for read/write respectively) which reads from Kafka and writes to RabbitMQ can specify the following configuration:

+For instance, a processor application which reads from Kafka and writes to RabbitMQ can specify the following configuration:

@@ -7357,7 +7372,7 @@ You can achieve this scenario by correlating the input and output destinations o

Supposing that a design calls for the Time Source application to send data to the Log Sink application, you can use a common destination named ticktock for bindings within both applications.

-

Time Source (that has the channel name output) will set the following property:

+

Time Source will set the following property:

@@ -7365,7 +7380,7 @@ You can achieve this scenario by correlating the input and output destinations o
-

Log Sink (that has the channel name input) will set the following property:

+

Log Sink will set the following property:

@@ -7453,7 +7468,7 @@ If a topic already exists with a larger number of partitions than the maximum of
Configuring Input Bindings for Partitioning
-

An input binding (with the channel name input) is configured to receive partitioned data by setting its partitioned property, as well as the instanceIndex and instanceCount properties on the application itself, as in the following example:

+

An input binding is configured to receive partitioned data by setting its partitioned property, as well as the instanceIndex and instanceCount properties on the application itself, as in the following example:

@@ -7496,7 +7511,7 @@ The following example shows how to test both input and output channels on a proc
-
@RunWith(SpringJUnit4ClassRunner.class)
+
@RunWith(SpringJUnit4ClassRunner.class)
 @SpringApplicationConfiguration(classes = ExampleTest.MyProcessor.class)
 @IntegrationTest({"server.port=-1"})
 @DirtiesContext
@@ -10458,7 +10473,7 @@ $ sdk use springboot 1.3.5.RELEASE

 

 

 
$ mvn install
-$ spring install org.springframework.cloud:spring-cloud-cli:1.1.0.RELEASE

+$ spring install org.springframework.cloud:spring-cloud-cli:1.1.2.RELEASE
@@ -13074,7 +13089,7 @@ created during auto-configuration.