anchor.diff:  If neither a `partitionSelectorClass` nor a `partitionSelectorExpression` is
   present the result is `key.hashCode() % partitionCount`.
   
  +
  +==== Overriding application properties during stream deployment
  +
  +Application properties that are defined during deployment override the same properties defined during the stream creation.
  +
  +For example, the following stream has application properties defined during stream creation:
  +
  +[source,bash]
  +----
  +dataflow:> stream create --definition "time --fixed-delay=5 | log --level=WARN" --name ticktock
  +----
  +
  +To override these application properties, one can specify the new property values during deployment:
  +
  +[source,bash]
  +----
  +dataflow:>stream deploy ticktock --properties "app.time.fixed-delay=4,app.log.level=ERROR"
  +----
  +
  +
  +=== Deployment properties
  +
  +When deploying the stream, properties that control the deployment of the apps into the target platform are known as `deployment` properties.
  +For instance, one can specify how many instances need to be deployed for the specific application defined in the stream using the deployment property called `count`.
  +
  +==== Passing instance count as deployment property
  +
  +If you would like to have multiple instances of an application in the stream, you
  +can include a property with the deploy command:
  +
  +[source,bash]
  +----
  +dataflow:> stream deploy --name ticktock --properties "app.time.count=3"
  +----
  +
  +Note that `count` is the *reserved* property name used by the underlying deployer. Hence, if the application also has a custom property named `count`, it is *not* supported
  + when specified in 'short-form' form during stream _deployment_ as it could conflict with the _instance_ count deployer property. Instead, the `count` as a custom application property can be
  + specified in its _fully qualified_ form (example: `app.foo.bar.count`) during stream _deployment_ or it can be specified using 'short-form' or _fully qualified_ form during the stream _creation_
  + where it will be considered as an app property.
  +
  +IMPORTANT: See <<spring-cloud-dataflow-stream-app-labels>>.
  +
   ==== Inline vs file reference properties
   
   When using the Spring Cloud Dataflow Shell, there are two ways to provide deployment
  
positive.code:   use the `--properties` shell option and list properties as a comma separated
    list of key=value pairs, like so:
  
  [source,bash,subs=attributes]
  ----
  stream deploy foo
      --properties "app.transform.count=2,app.transform.producer.partitionKeyExpression=payload"
  
negative.code:   `:` delimiter, etc.) although we recommend using `=` as a key-value pair delimiter
    for consistency:
  
  [source,bash]
  ----
  stream deploy foo --propertiesFile myprops.properties
  ----
  