review comments
diff --git a/docs/README.md b/docs/README.md
index f87b134..56da003 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -33,6 +33,7 @@
To test the site, run:
bundle exec jekyll serve --watch --baseurl ""
+(add --host 0.0.0.0 if you want it to be visible from other hosts)
## Versioning
diff --git a/docs/_blog/2019-06-11-announcing-the-release-of-apache-samza--1.2.0.md b/docs/_blog/2019-06-11-announcing-the-release-of-apache-samza--1.2.0.md
index 5cda4fa..bf0b769 100644
--- a/docs/_blog/2019-06-11-announcing-the-release-of-apache-samza--1.2.0.md
+++ b/docs/_blog/2019-06-11-announcing-the-release-of-apache-samza--1.2.0.md
@@ -60,7 +60,7 @@
* Beam integration with tables and integration with CouchBase
-* Async high level api
+* Async high level API
* Bug fixes
@@ -69,53 +69,53 @@
### Kafka upgrade
-[SAMZA-2127](/https://issues.apache.org/jira/browse/SAMZA-2127) Upgrade to Kafka 2.0
+[SAMZA-2127](https://issues.apache.org/jira/browse/SAMZA-2127) Upgrade to Kafka 2.0
### Async API for high level
-[SAMZA-2055](/https://issues.apache.org/jira/browse/SAMZA-2055) Design and Implement async API for high level
+[SAMZA-2055](https://issues.apache.org/jira/browse/SAMZA-2055) Design and Implement async API for high level
-[SAMZA-2172](/https://issues.apache.org/jira/browse/SAMZA-2172) Async High Level API does not schedule StreamOperatorTasks on separate threads
+[SAMZA-2172](https://issues.apache.org/jira/browse/SAMZA-2172) Async High Level API does not schedule StreamOperatorTasks on separate threads
-#### Starpoint
-[SAMZA-2192](/https://issues.apache.org/jira/browse/SAMZA-2192) Add StartpointVisitor implementation for EventHub.
+#### Startpoint
+[SAMZA-2192](https://issues.apache.org/jira/browse/SAMZA-2192) Add StartpointVisitor implementation for EventHub.
-[SAMZA-2189](/https://issues.apache.org/jira/browse/SAMZA-2189) Integrate startpoint resolution workflow with SamzaContainer startup sequence.
+[SAMZA-2189](https://issues.apache.org/jira/browse/SAMZA-2189) Integrate startpoint resolution workflow with SamzaContainer startup sequence.
-[SAMZA-2179](/https://issues.apache.org/jira/browse/SAMZA-2179) Move the StartpointVisitor abstraction to SystemAdmin interface.
+[SAMZA-2179](https://issues.apache.org/jira/browse/SAMZA-2179) Move the StartpointVisitor abstraction to SystemAdmin interface.
-[SAMZA-2046](/https://issues.apache.org/jira/browse/SAMZA-2046) Startpoints - Fanout of SSP-only keyed Startpoints to SSP+TaskName
+[SAMZA-2046](https://issues.apache.org/jira/browse/SAMZA-2046) Startpoints - Fanout of SSP-only keyed Startpoints to SSP+TaskName
-[SAMZA-2132](/https://issues.apache.org/jira/browse/SAMZA-2132) Startpoint - flatten serialized key
+[SAMZA-2132](https://issues.apache.org/jira/browse/SAMZA-2132) Startpoint - flatten serialized key
#### Table API
-[SAMZA-2185](/https://issues.apache.org/jira/browse/SAMZA-2185) Ability to expose remote data source specific features in remote table
+[SAMZA-2185](https://issues.apache.org/jira/browse/SAMZA-2185) Ability to expose remote data source specific features in remote table
-[SAMZA-2156](/https://issues.apache.org/jira/browse/SAMZA-2156) Couchbase Table Support for Samza Table API
+[SAMZA-2156](https://issues.apache.org/jira/browse/SAMZA-2156) Couchbase Table Support for Samza Table API
-[SAMZA-2153](/https://issues.apache.org/jira/browse/SAMZA-2153) Config for TableRetryPolicy
+[SAMZA-2153](https://issues.apache.org/jira/browse/SAMZA-2153) Config for TableRetryPolicy
-[SAMZA-2134](/https://issues.apache.org/jira/browse/SAMZA-2134) Enable remote table rate limiter by default
+[SAMZA-2134](https://issues.apache.org/jira/browse/SAMZA-2134) Enable remote table rate limiter by default
-[SAMZA-2116](/https://issues.apache.org/jira/browse/SAMZA-2116) Make sendTo operators non-terminal
+[SAMZA-2116](https://issues.apache.org/jira/browse/SAMZA-2116) Make sendTo operators non-terminal
#### Bug Fixes, Testing and Stability improvments
-[SAMZA-2202](/https://issues.apache.org/jira/browse/SAMZA-2202) Modify topic creation s.t. all log compacted topics are created with a 5MB message size limit.
+[SAMZA-2202](https://issues.apache.org/jira/browse/SAMZA-2202) Modify topic creation s.t. all log compacted topics are created with a 5MB message size limit.
-[SAMZA-2181](/https://issues.apache.org/jira/browse/SAMZA-2181) Ensure consistency of coordinator store creation and initialization
+[SAMZA-2181](https://issues.apache.org/jira/browse/SAMZA-2181) Ensure consistency of coordinator store creation and initialization
-[SAMZA-2178](/https://issues.apache.org/jira/browse/SAMZA-2178) Utils to directly inject custom IME to InMemorySystem streams
+[SAMZA-2178](https://issues.apache.org/jira/browse/SAMZA-2178) Utils to directly inject custom IME to InMemorySystem streams
-[SAMZA-2176](/https://issues.apache.org/jira/browse/SAMZA-2176) Ignore the configurations with serialized null values from coordinator stream.
+[SAMZA-2176](https://issues.apache.org/jira/browse/SAMZA-2176) Ignore the configurations with serialized null values from coordinator stream.
-[SAMZA-2171](/https://issues.apache.org/jira/browse/SAMZA-2171) Encapsulate creation and loading of metadata streams
+[SAMZA-2171](https://issues.apache.org/jira/browse/SAMZA-2171) Encapsulate creation and loading of metadata streams
-[SAMZA-2170](/https://issues.apache.org/jira/browse/SAMZA-2170) Enabling writing of both new and old format offset files for stores and side-input-stores
+[SAMZA-2170](https://issues.apache.org/jira/browse/SAMZA-2170) Enabling writing of both new and old format offset files for stores and side-input-stores
-[SAMZA-2169](/https://issues.apache.org/jira/browse/SAMZA-2169) Preventing task-shuffle after task mode addition
+[SAMZA-2169](https://issues.apache.org/jira/browse/SAMZA-2169) Preventing task-shuffle after task mode addition
-[SAMZA-2161](/https://issues.apache.org/jira/browse/SAMZA-2161) Move ChangelogPartitionManager and CoordinatorStream ConfigReader to MetadataStore
+[SAMZA-2161](https://issues.apache.org/jira/browse/SAMZA-2161) Move ChangelogPartitionManager and CoordinatorStream ConfigReader to MetadataStore
-[SAMZA-2135](/https://issues.apache.org/jira/browse/SAMZA-2135) Provide a way inject ExternalContext to TestRunner
+[SAMZA-2135](https://issues.apache.org/jira/browse/SAMZA-2135) Provide a way inject ExternalContext to TestRunner
### Sources downloads
A source download of Samza 1.2.0 is available [here](https://dist.apache.org/repos/dist/release/samza/1.2.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.
@@ -127,5 +127,5 @@
It’s a great time to get involved. You can start by reviewing the [tutorials](http://samza.apache.org/startup/preview/#try-it-out), signing up for the [mailing list](http://samza.apache.org/community/mailing-lists.html), and grabbing some [newbie JIRAs](https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20labels%20%3D%20newbie%20AND%20status%20%3D%20Open).
-I'd like to close by thanking everyone who’s been involved in the project. It’s been a great experience to be involved in this community, and I look forward to its continued growth.
+We'd like to close by thanking everyone who’s been involved in the project. It’s been a great experience to be involved in this community, and we are lookng forward to its continued growth.
diff --git a/docs/_releases/1.2.0.md b/docs/_releases/1.2.0.md
index 8d45319..7791669 100644
--- a/docs/_releases/1.2.0.md
+++ b/docs/_releases/1.2.0.md
@@ -52,7 +52,7 @@
* Beam integration with tables and integration with CouchBase
-* Async high level api
+* Async high level API
* Bug fixes
@@ -60,63 +60,54 @@
### **Upgrading your application to Apache Samza 1.2.0**
### Kafka upgrade
-[SAMZA-2127](/https://issues.apache.org/jira/browse/SAMZA-2127) Upgrade to Kafka 2.0
+[SAMZA-2127](https://issues.apache.org/jira/browse/SAMZA-2127) Upgrade to Kafka 2.0
### Async API for high level
-[SAMZA-2055](/https://issues.apache.org/jira/browse/SAMZA-2055) Design and Implement async API for high level
+[SAMZA-2055](https://issues.apache.org/jira/browse/SAMZA-2055) Design and Implement async API for high level
-[SAMZA-2172](/https://issues.apache.org/jira/browse/SAMZA-2172) Async High Level API does not schedule StreamOperatorTasks on separate threads
+[SAMZA-2172](https://issues.apache.org/jira/browse/SAMZA-2172) Async High Level API does not schedule StreamOperatorTasks on separate threads
-#### Starpoint
-[SAMZA-2192](/https://issues.apache.org/jira/browse/SAMZA-2192) Add StartpointVisitor implementation for EventHub.
+#### Startpoint
+[SAMZA-2192](https://issues.apache.org/jira/browse/SAMZA-2192) Add StartpointVisitor implementation for EventHub.
-[SAMZA-2189](/https://issues.apache.org/jira/browse/SAMZA-2189) Integrate startpoint resolution workflow with SamzaContainer startup sequence.
+[SAMZA-2189](https://issues.apache.org/jira/browse/SAMZA-2189) Integrate startpoint resolution workflow with SamzaContainer startup sequence.
-[SAMZA-2179](/https://issues.apache.org/jira/browse/SAMZA-2179) Move the StartpointVisitor abstraction to SystemAdmin interface.
+[SAMZA-2179](https://issues.apache.org/jira/browse/SAMZA-2179) Move the StartpointVisitor abstraction to SystemAdmin interface.
-[SAMZA-2046](/https://issues.apache.org/jira/browse/SAMZA-2046) Startpoints - Fanout of SSP-only keyed Startpoints to SSP+TaskName
+[SAMZA-2046](https://issues.apache.org/jira/browse/SAMZA-2046) Startpoints - Fanout of SSP-only keyed Startpoints to SSP+TaskName
-[SAMZA-2132](/https://issues.apache.org/jira/browse/SAMZA-2132) Startpoint - flatten serialized key
+[SAMZA-2132](https://issues.apache.org/jira/browse/SAMZA-2132) Startpoint - flatten serialized key
#### Table API
-[SAMZA-2185](/https://issues.apache.org/jira/browse/SAMZA-2185) Ability to expose remote data source specific features in remote table
+[SAMZA-2185](https://issues.apache.org/jira/browse/SAMZA-2185) Ability to expose remote data source specific features in remote table
-[SAMZA-2156](/https://issues.apache.org/jira/browse/SAMZA-2156) Couchbase Table Support for Samza Table API
+[SAMZA-2156](https://issues.apache.org/jira/browse/SAMZA-2156) Couchbase Table Support for Samza Table API
-[SAMZA-2153](/https://issues.apache.org/jira/browse/SAMZA-2153) Config for TableRetryPolicy
+[SAMZA-2153](https://issues.apache.org/jira/browse/SAMZA-2153) Config for TableRetryPolicy
-[SAMZA-2134](/https://issues.apache.org/jira/browse/SAMZA-2134) Enable remote table rate limiter by default
+[SAMZA-2134](https://issues.apache.org/jira/browse/SAMZA-2134) Enable remote table rate limiter by default
-[SAMZA-2116](/https://issues.apache.org/jira/browse/SAMZA-2116) Make sendTo operators non-terminal
+[SAMZA-2116](https://issues.apache.org/jira/browse/SAMZA-2116) Make sendTo operators non-terminal
#### Bug Fixes, Testing and Stability improvments
-[SAMZA-2202](/https://issues.apache.org/jira/browse/SAMZA-2202) Modify topic creation s.t. all log compacted topics are created with a 5MB message size limit.
+[SAMZA-2202](https://issues.apache.org/jira/browse/SAMZA-2202) Modify topic creation s.t. all log compacted topics are created with a 5MB message size limit.
-[SAMZA-2181](/https://issues.apache.org/jira/browse/SAMZA-2181) Ensure consistency of coordinator store creation and initialization
+[SAMZA-2181](https://issues.apache.org/jira/browse/SAMZA-2181) Ensure consistency of coordinator store creation and initialization
-[SAMZA-2178](/https://issues.apache.org/jira/browse/SAMZA-2178) Utils to directly inject custom IME to InMemorySystem streams
+[SAMZA-2178](https://issues.apache.org/jira/browse/SAMZA-2178) Utils to directly inject custom IME to InMemorySystem streams
-[SAMZA-2176](/https://issues.apache.org/jira/browse/SAMZA-2176) Ignore the configurations with serialized null values from coordinator stream.
+[SAMZA-2176](https://issues.apache.org/jira/browse/SAMZA-2176) Ignore the configurations with serialized null values from coordinator stream.
-[SAMZA-2171](/https://issues.apache.org/jira/browse/SAMZA-2171) Encapsulate creation and loading of metadata streams
+[SAMZA-2171](https://issues.apache.org/jira/browse/SAMZA-2171) Encapsulate creation and loading of metadata streams
-[SAMZA-2170](/https://issues.apache.org/jira/browse/SAMZA-2170) Enabling writing of both new and old format offset files for stores and side-input-stores
+[SAMZA-2170](https://issues.apache.org/jira/browse/SAMZA-2170) Enabling writing of both new and old format offset files for stores and side-input-stores
-[SAMZA-2169](/https://issues.apache.org/jira/browse/SAMZA-2169) Preventing task-shuffle after task mode addition
+[SAMZA-2169](https://issues.apache.org/jira/browse/SAMZA-2169) Preventing task-shuffle after task mode addition
-[SAMZA-2161](/https://issues.apache.org/jira/browse/SAMZA-2161) Move ChangelogPartitionManager and CoordinatorStream ConfigReader to MetadataStore
+[SAMZA-2161](https://issues.apache.org/jira/browse/SAMZA-2161) Move ChangelogPartitionManager and CoordinatorStream ConfigReader to MetadataStore
-[SAMZA-2135](/https://issues.apache.org/jira/browse/SAMZA-2135) Provide a way inject ExternalContext to TestRunner
+[SAMZA-2135](https://issues.apache.org/jira/browse/SAMZA-2135) Provide a way inject ExternalContext to TestRunner
### Sources downloads
A source download of Samza 1.2.0 is available [here](https://dist.apache.org/repos/dist/release/samza/1.2.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.
-## **Community Developments**
-Future Samza meetups can be found at [Stream Processing with Apache Kafka & Apache Samza meetup/symposium](https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/)
-
-##**Contribute**
-
-It’s a great time to get involved. You can start by reviewing the [tutorials](http://samza.apache.org/startup/preview/#try-it-out), signing up for the [mailing list](http://samza.apache.org/community/mailing-lists.html), and grabbing some [newbie JIRAs](https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20labels%20%3D%20newbie%20AND%20status%20%3D%20Open).
-
-I’d like to close by thanking everyone who’s been involved in the project. It’s been a great experience to be involved in this community, and I look forward to its continued growth.
-
