[DOCS] Update the docs & blogs for 1.5.0 release (#1399)

docs/_blog/2020-07-01-announcing-the-release-of-apache-samza--1.5.0.md

@@ -0,0 +1,144 @@
+---
+layout: blog
+title: Announcing the release of Apache Samza 1.5.0
+icon: git-pull-request
+authors:
+    - name: Bharath Kumarasubramanian
+      website:
+      image:
+excerpt_separator: <!--more-->
+---
+
+<!--
+   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.
+-->
+
+# **Announcing the release of Apache Samza 1.5.0**
+
+
+<!--more-->
+
+**IMPORTANT NOTE**: As noted in the last release, this release contains **backward incompatible changes regarding samza job submission**. Details can be found on [SEP-23: Simplify Job Runner](https://cwiki.apache.org/confluence/display/SAMZA/SEP-23%3A+Simplify+Job+Runner)
+
+We are thrilled to announce the release of Apache Samza 1.5.0.
+
+Today, Samza forms the backbone of hundreds of real-time production applications across a multitude of companies, such as LinkedIn, Slack, and Redfin, among many others. Samza provides leading support for large-scale stateful stream processing with:
+
+* First class support for local states (with RocksDB store). This allows a stateful application to scale up to 1.1 Million events/sec on a single machine with SSD.
+
+* Support for incremental checkpointing of state instead of full snapshots. This enables Samza to scale to applications with very large states.
+
+* A fully asynchronous programming model that makes parallelizing remote calls efficient and effortless.
+
+* High level API for expressing complex stream processing pipelines in a few lines of code.
+
+* Beam Samza Runner that marries Beam’s best in class support for EventTime based windowed processing and sophisticated triggering with Samza’s stable and scalable stateful processing model.
+
+* A fully pluggable model for input sources (e.g. Kafka, Kinesis, DynamoDB streams etc.) and output systems (HDFS, Kafka, ElastiCache etc.).
+
+* A Table API that provides a common abstraction for accessing remote or local databases and allows developers to “join” an input event stream with such a Table.
+
+* Flexible deployment model for running the applications in any hosting environment and with cluster managers other than YARN.
+
+### New Features, Upgrades and Bug Fixes:
+This release brings the following features, upgrades, and capabilities (highlights):
+
+#### Samza Container Placement
+Container Placements API gives you the ability to move / restart one or more containers (either active or standby) of your cluster based applications from one host to another without restarting your application. You can use these API to build maintenance, balancing & remediation tools. 
+
+#### Simplify Job Runner & Configs
+Job Runner will now simply submit Samza job to Yarn RM without executing any user code and job planning will happen on ClusterBasedJobCoordinator instead. This simplified workflow addresses security requirements where job submissions need to be isolated in order to execute user code as well as operational pain points where deployment failure could happen at multiple places.
+
+Full list of the jiras addressed in this release can be found [here](https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20and%20fixVersion%20in%20(1.5)).
+
+### Upgrading your application to Apache Samza 1.5.0
+ConfigFactory is deprecated as Job Runner does not load full job config anymore. Instead, ConfigLoaderFactory is introduced to be executed on ClusterBasedJobCoordinator to fetch full job config.
+If you are using the default PropertiesConfigFactory, simply switching to use the default PropertiesConfigLoaderFactory will work, otherwise if you are using a custom ConfigFactory, kindly creates its new counterpart following ConfigLoaderFactory. 
+
+Configs related to job submission must be explicitly provided to Job Runner as it is no longer loading full job config anymore. These configs include
+
+* Configs directly related to job submission, such as yarn.package.path, job.name etc.
+* Configs needed by the config loader on AM to fetch job config, such as path to the property file in the tarball, all of such configs will have a job.config.loader.properties prefix.
+* Configs that users would like to override
+
+Full list of the job submission configurations can be found [here](https://cwiki.apache.org/confluence/display/SAMZA/SEP-23%3A+Simplify+Job+Runner#SEP23:SimplifyJobRunner-References)
+
+#### Usage Instructions
+Alternative way when submitting job,
+{% highlight bash %}
+deploy/samza/bin/run-app.sh
+ --config yarn.package.path=<package_path>
+ --config job.name=<job_name>
+{% endhighlight %}
+can be simplified to
+{% highlight bash %}
+deploy/samza/bin/run-app.sh
+ --config-path=/path/to/submission/properties/file/submission.properties
+{% endhighlight %}
+where submission.properties contains
+{% highlight jproperties %}
+yarn.package.path=<package_path>
+job.name=<job_name>
+{% endhighlight %}
+
+#### Rollback Instructions
+In case of a problem in Samza 1.5, users can rollback to Samza 1.4 and keep the old start up flow using _config-path_ & _config-factory_.
+
+### Simplify Job Runner & Configs
+[SAMZA-2488](https://issues.apache.org/jira/browse/SAMZA-2488) Add JobCoordinatorLaunchUtil to handle common logic when launching job coordinator
+
+[SAMZA-2471](https://issues.apache.org/jira/browse/SAMZA-2471) Simplify CommandLine
+
+[SAMZA-2458](https://issues.apache.org/jira/browse/SAMZA-2458) Update ProcessJobFactory and ThreadJobFactory to load full job config
+
+[SAMZA-2453](https://issues.apache.org/jira/browse/SAMZA-2453) Update ClusterBasedJobCoordinator to support Beam jobs
+
+[SAMZA-2441](https://issues.apache.org/jira/browse/SAMZA-2441) Update ApplicationRunnerMain#ApplicationRunnerCommandLine not to load local file
+
+[SAMZA-2420](https://issues.apache.org/jira/browse/SAMZA-2420) Update CommandLine to use config loader for local config file
+
+### Container Placement API
+[SAMZA-2402](https://issues.apache.org/jira/browse/SAMZA-2402) Tie Container placement service and Container placement handler and validate placement requests
+
+[SAMZA-2379](https://issues.apache.org/jira/browse/SAMZA-2379) Support Container Placements for job running in degraded state
+
+[SAMZA-2378](https://issues.apache.org/jira/browse/SAMZA-2378) Container Placements support for Standby containers enabled jobs
+
+
+### Bug Fixes
+[SAMZA-2515](https://issues.apache.org/jira/browse/SAMZA-2515) Thread safety for Kafka consumer in KafkaConsumerProxy
+
+[SAMZA-2511](https://issues.apache.org/jira/browse/SAMZA-2511) Handle container-stop-fail in case of standby container failover
+
+[SAMZA-2510](https://issues.apache.org/jira/browse/SAMZA-2510) Incorrect shutdown status due to race between runloop thread and process callback thread
+
+[SAMZA-2506](https://issues.apache.org/jira/browse/SAMZA-2506) Inconsistent end of stream semantics in SystemStreamPartitionMetadata
+
+[SAMZA-2464](https://issues.apache.org/jira/browse/SAMZA-2464) Container shuts down when task fails to remove old state checkpoint dirs
+
+[SAMZA-2468](https://issues.apache.org/jira/browse/SAMZA-2468) Standby container needs to respond to shutdown request
+
+### Other Improvements
+[SAMZA-2519](https://issues.apache.org/jira/browse/SAMZA-2519) Support duplicate timer registration
+
+[SAMZA-2508](https://issues.apache.org/jira/browse/SAMZA-2508) Use cytodynamics classloader to launch job container
+
+[SAMZA-2478](https://issues.apache.org/jira/browse/SAMZA-2478) Add new metrics to track key and value size of records written to RocksDb
+
+[SAMZA-2462](https://issues.apache.org/jira/browse/SAMZA-2462) Adding metric for container thread pool size
+
+### Sources downloads
+A source download of Samza 1.5.0 is available [here](https://dist.apache.org/repos/dist/release/samza/1.5.0/), and is also available in Apache’s Maven repository. See Samza’s download [page](https://samza.apache.org/startup/download/) for details and Samza’s feature preview for new features.

docs/_config.yml

@@ -25,7 +25,7 @@ exclude: [_docs]
 baseurl: http://samza.apache.org
 version: latest
 # this is the version you will go if you click 'switch version' in "latest" pages.
-latest-release: '1.4.0'
+latest-release: '1.5.0'
 collections:
   menu:
     output: false

docs/_menu/index.html

@@ -12,6 +12,8 @@
     items_attributes: 'data-documentation="/learn/documentation/version/"'
   - menu_title: Releases
     items:
+      - menu_title: 1.5.0
+        url: '/releases/1.5.0'
       - menu_title: 1.4.0
         url: '/releases/1.4.0'
       - menu_title: 1.3.1

docs/_releases/1.5.0.md

@@ -0,0 +1,135 @@
+---
+version: '1.5.0'
+order: 150
+layout: page
+menu_title: '1.5'
+title: Apache Samza 1.5 <a href="/learn/documentation/1.5.0/">      [Docs] </a>
+---
+<!--
+   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.
+-->
+
+**IMPORTANT NOTE**: As noted in the last release, this release contains **backward incompatible changes regarding samza job submission**. Details can be found on [SEP-23: Simplify Job Runner](https://cwiki.apache.org/confluence/display/SAMZA/SEP-23%3A+Simplify+Job+Runner)
+
+We are thrilled to announce the release of Apache Samza 1.5.0.
+
+Today, Samza forms the backbone of hundreds of real-time production applications across a multitude of companies, such as LinkedIn, Slack, and Redfin, among many others. Samza provides leading support for large-scale stateful stream processing with:
+
+* First class support for local states (with RocksDB store). This allows a stateful application to scale up to 1.1 Million events/sec on a single machine with SSD.
+
+* Support for incremental checkpointing of state instead of full snapshots. This enables Samza to scale to applications with very large states.
+
+* A fully asynchronous programming model that makes parallelizing remote calls efficient and effortless.
+
+* High level API for expressing complex stream processing pipelines in a few lines of code.
+
+* Beam Samza Runner that marries Beam’s best in class support for EventTime based windowed processing and sophisticated triggering with Samza’s stable and scalable stateful processing model.
+
+* A fully pluggable model for input sources (e.g. Kafka, Kinesis, DynamoDB streams etc.) and output systems (HDFS, Kafka, ElastiCache etc.).
+
+* A Table API that provides a common abstraction for accessing remote or local databases and allows developers to “join” an input event stream with such a Table.
+
+* Flexible deployment model for running the applications in any hosting environment and with cluster managers other than YARN.
+
+### New Features, Upgrades and Bug Fixes:
+This release brings the following features, upgrades, and capabilities (highlights):
+
+#### Samza Container Placement
+Container Placements API gives you the ability to move / restart one or more containers (either active or standby) of your cluster based applications from one host to another without restarting your application. You can use these api to build maintenance, balancing & remediation tools. 
+
+#### Simplify Job Runner & Configs
+Job Runner will now simply submit Samza job to Yarn RM without executing any user code and job planning will happen on ClusterBasedJobCoordinator instead. This simplified workflow addresses security requirements where job submissions need to be isolated in order to execute user code as well as operational pain points where deployment failure could happen at multiple places.
+
+Full list of the jiras addressed in this release can be found [here](https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20and%20fixVersion%20in%20(1.5)).
+
+### Upgrading your application to Apache Samza 1.5.0
+ConfigFactory is deprecated as Job Runner does not load full job config anymore. Instead, ConfigLoaderFactory is introduced to be executed on ClusterBasedJobCoordinator to fetch full job config.
+If you are using the default PropertiesConfigFactory, simply switching to use the default PropertiesConfigLoaderFactory will work, otherwise if you are using a custom ConfigFactory, kindly creates its new counterpart following ConfigLoaderFactory. 
+
+Configs related to job submission must be explicitly provided to Job Runner as it is no longer loading full job config anymore. These configs include
+
+* Configs directly related to job submission, such as yarn.package.path, job.name etc.
+* Configs needed by the config loader on AM to fetch job config, such as path to the property file in the tarball, all of such configs will have a job.config.loader.properties prefix.
+* Configs that users would like to override
+
+Full list of the job submission configurations can be found [here](https://cwiki.apache.org/confluence/display/SAMZA/SEP-23%3A+Simplify+Job+Runner#SEP23:SimplifyJobRunner-References)
+
+#### Usage Instructions
+Alternative way when submitting job,
+{% highlight bash %}
+deploy/samza/bin/run-app.sh
+ --config yarn.package.path=<package_path>
+ --config job.name=<job_name>
+{% endhighlight %}
+can be simplified to
+{% highlight bash %}
+deploy/samza/bin/run-app.sh
+ --config-path=/path/to/submission/properties/file/submission.properties
+{% endhighlight %}
+where submission.properties contains
+{% highlight jproperties %}
+yarn.package.path=<package_path>
+job.name=<job_name>
+{% endhighlight %}
+
+#### Rollback Instructions
+In case of a problem in Samza 1.5, users can rollback to Samza 1.4 and keep the old start up flow using _config-path_ & _config-factory_.
+
+### Simplify Job Runner
+[SAMZA-2488](https://issues.apache.org/jira/browse/SAMZA-2488) Add JobCoordinatorLaunchUtil to handle common logic when launching job coordinator
+
+[SAMZA-2471](https://issues.apache.org/jira/browse/SAMZA-2471) Simplify CommandLine
+
+[SAMZA-2458](https://issues.apache.org/jira/browse/SAMZA-2458) Update ProcessJobFactory and ThreadJobFactory to load full job config
+
+[SAMZA-2453](https://issues.apache.org/jira/browse/SAMZA-2453) Update ClusterBasedJobCoordinator to support Beam jobs
+
+[SAMZA-2441](https://issues.apache.org/jira/browse/SAMZA-2441) Update ApplicationRunnerMain#ApplicationRunnerCommandLine not to load local file
+
+[SAMZA-2420](https://issues.apache.org/jira/browse/SAMZA-2420) Update CommandLine to use config loader for local config file
+
+### Container Placement API
+[SAMZA-2402](https://issues.apache.org/jira/browse/SAMZA-2402) Tie Container placement service and Container placement handler and validate placement requests
+
+[SAMZA-2379](https://issues.apache.org/jira/browse/SAMZA-2379) Support Container Placements for job running in degraded state
+
+[SAMZA-2378](https://issues.apache.org/jira/browse/SAMZA-2378) Container Placements support for Standby containers enabled jobs
+
+
+### Bug Fixes
+[SAMZA-2515](https://issues.apache.org/jira/browse/SAMZA-2515) Thread safety for Kafka consumer in KafkaConsumerProxy
+
+[SAMZA-2511](https://issues.apache.org/jira/browse/SAMZA-2511) Handle container-stop-fail in case of standby container failover
+
+[SAMZA-2510](https://issues.apache.org/jira/browse/SAMZA-2510) Incorrect shutdown status due to race between runloop thread and process callback thread
+
+[SAMZA-2506](https://issues.apache.org/jira/browse/SAMZA-2506) Inconsistent end of stream semantics in SystemStreamPartitionMetadata
+
+[SAMZA-2464](https://issues.apache.org/jira/browse/SAMZA-2464) Container shuts down when task fails to remove old state checkpoint dirs
+
+[SAMZA-2468](https://issues.apache.org/jira/browse/SAMZA-2468) Standby container needs to respond to shutdown request
+
+### Other Improvements
+[SAMZA-2519](https://issues.apache.org/jira/browse/SAMZA-2519) Support duplicate timer registration
+
+[SAMZA-2508](https://issues.apache.org/jira/browse/SAMZA-2508) Use cytodynamics classloader to launch job container
+
+[SAMZA-2478](https://issues.apache.org/jira/browse/SAMZA-2478) Add new metrics to track key and value size of records written to RocksDb
+
+[SAMZA-2462](https://issues.apache.org/jira/browse/SAMZA-2462) Adding metric for container thread pool size
+
+### Sources downloads
+A source download of Samza 1.5.0 is available [here](https://dist.apache.org/repos/dist/release/samza/1.5.0/), and is also available in Apache’s Maven repository. See Samza’s download [page](https://samza.apache.org/startup/download/) for details and Samza’s feature preview for new features.

docs/archive/index.html

@@ -27,6 +27,14 @@ <h4 id="latest">Latest Release</h4>
   <li><a href="../startup/hello-samza/latest">Hello Samza</a></li>
 </ul>
 
+<h4 id="1.5">1.5 Release</h4>
+
+<ul class="documentation-list">
+    <li><a href="../learn/documentation/1.5.0">Documentation</a></li>
+    <li><a href="../learn/tutorials/1.5.0">Tutorials</a></li>
+    <li><a href="../startup/hello-samza/1.5.0">Hello Samza</a></li>
+</ul>
+
 <h4 id="1.4">1.4 Release</h4>
 
 <ul class="documentation-list">

docs/learn/tutorials/versioned/hello-samza-high-level-yarn.md

@@ -63,7 +63,7 @@ Then, you can continue w/ the following command in hello-samza project:
 {% highlight bash %}
 mvn clean package
 mkdir -p deploy/samza
-tar -xvf ./target/hello-samza-1.4.0-SNAPSHOT-dist.tar.gz -C deploy/samza
+tar -xvf ./target/hello-samza-1.6.0-SNAPSHOT-dist.tar.gz -C deploy/samza
 {% endhighlight %}
 
 ### Run a Samza Application

docs/learn/tutorials/versioned/hello-samza-high-level-zk.md

@@ -59,7 +59,7 @@ With the environment setup complete, let us move on to building the hello-samza
 {% highlight bash %}
 mvn clean package
 mkdir -p deploy/samza
-tar -xvf ./target/hello-samza-1.4.0-SNAPSHOT-dist.tar.gz -C deploy/samza
+tar -xvf ./target/hello-samza-1.6.0-SNAPSHOT-dist.tar.gz -C deploy/samza
 {% endhighlight %}
 
 We are now all set to deploy the application locally.

docs/learn/tutorials/versioned/samza-rest-getting-started.md

@@ -48,7 +48,7 @@ Run the following commands:
 {% highlight bash %}
 cd samza-rest/build/distributions/
 mkdir -p deploy/samza-rest
-tar -xvf ./samza-rest_2.11-1.4.0-SNAPSHOT.tgz -C deploy/samza-rest
+tar -xvf ./samza-rest_2.11-1.6.0-SNAPSHOT.tgz -C deploy/samza-rest
 {% endhighlight %}
 
 #### Configure the Installations Path