Merge remote-tracking branch 'upstream/master'

Author: weisong44

RELEASE.md

@@ -28,6 +28,7 @@ And before you proceed, do the following steps:
       version=$VERSION
    * change the samza_executable variable in samza-test/src/main/python/configs/tests.json to $VERSION w/o the suffix '-SNAPSHOT'. 
    * change the samza-test versions in samza-test/src/main/config/join/README to $VERSION w/o the suffix '-SNAPSHOT'.
+   * change the executable version in samza-test/src/main/python/stream_processor.py to $VERSION w/o the suffix '-SNAPSHOT'.
    * push the changes to the $VERSION branch
 
 Validate Samza using all our supported build matrix.
@@ -49,17 +50,34 @@ Alternatively, you can make a fresh clone of the repository to a separate direct
     git clone http://git-wip-us.apache.org/repos/asf/samza.git samza-release
     cd samza-release
 
-Then build the tarball:
+Then build the source and samza-tools tarballs:
 
-    ./gradlew clean sourceRelease
+    ./gradlew clean sourceRelease && ./gradlew releaseToolsTarGz
 
-Then sign it:
+Then sign them:
 
-    gpg --sign --armor --detach-sig build/distribution/source/apache-samza-*.tgz
+    gpg --sign --armor --detach-sig ./build/distribution/source/apache-samza-*.tgz
+    gpg --sign --armor --detach-sig ./samza-tools/build/distributions/samza-tools-*.tgz
+
+Create MD5 signatures:
 
-Create SHA1 signature:
+    gpg --print-md MD5 ./build/distribution/source/apache-samza-*.tgz > ./build/distribution/source/apache-samza-*.tgz.md5
+    gpg --print-md MD5 ./samza-tools/build/distributions/samza-tools-*.tgz > ./samza-tools/build/distributions/samza-tools-*.tgz.md5
+
+Create SHA1 signatures:
 
     gpg --print-md SHA1 ./build/distribution/source/apache-samza-*.tgz > ./build/distribution/source/apache-samza-*.tgz.sha1
+    gpg --print-md SHA1 ./samza-tools/build/distributions/samza-tools-*.tgz > ./samza-tools/build/distributions/samza-tools-*.tgz.sha1
+
+Upload the build artifacts to your Apache home directory:
+
+    sftp <apache-username>@home.apache.org
+    cd public_html
+    mkdir samza-$VERSION-rc0
+    cd samza-$VERSION-rc0
+    put ./build/distribution/source/apache-samza-$VERSION-src.* .
+    put ./samza-tools/build/distributions/samza-tools-$VERSION.* .
+    bye
 
 Make a signed git tag for the release candidate:
 
@@ -69,23 +87,7 @@ Push the release tag to remote repository:
 
     git push origin release-$VERSION-rc0
 
-Build the tarball for samza-tool:
-
-    ./gradlew releaseToolsTarGz
-
-Then sign it:
-
-    gpg --sign --armor --detach-sig ./samza-tools/build/distributions/samza-tools-*.tgz
-
-Create MD5 signature:
-
-    gpg --print-md MD5 ./samza-tools/build/distributions/samza-tools-*.tgz > ./samza-tools/build/distributions/samza-tools-*.tgz.md5
-
-Create SHA1 signature:
-
-    gpg --print-md SHA1 ./build/distribution/source/apache-samza-*.tgz > ./build/distribution/source/apache-samza-*.tgz.sha1
-
-Edit `$HOME/.gradle/gradle.properties` and add your GPG key information:
+Edit `$HOME/.gradle/gradle.properties` and add your GPG key information (without the comments):
 
     signing.keyId=01234567                          # Your GPG key ID, as 8 hex digits
     signing.secretKeyRingFile=/path/to/secring.gpg  # Normally in $HOME/.gnupg/secring.gpg
@@ -112,6 +114,7 @@ repository just created, and close it. This may take a minute or so. When it
 finishes, the UI shows a staging repository URL. This can be used in a project
 that depends on Samza, to test the release candidate.
 
+
 If the VOTE has successfully passed on the release candidate, you can log in to the 
 [repository web interface](https://repository.apache.org) (same as above) and "release" 
 the org.apache.samza repository listed under "Staging Repositories".

build.gradle

@@ -336,6 +336,34 @@ project(':samza-sql') {
   }
 }
 
+project(':samza-sql-shell') {
+  apply plugin: 'java'
+
+  dependencies {
+    compile project(':samza-sql')
+    compile project(':samza-tools')
+    compile project(":samza-core_$scalaVersion")
+    compile project(':samza-api')
+    compile project(":samza-kafka_$scalaVersion")
+    compile project(':samza-azure')
+    compile "net.java.dev.jna:jna:$jnaVersion"
+    compile "org.jline:jline:$jlineVersion"
+
+    testCompile "junit:junit:$junitVersion"
+  }
+
+  tasks.create(name: "releaseSqlShellTarGz", dependsOn: configurations.archives.artifacts, type: Tar) {
+    into "samza-sql-shell-${version}"
+    compression = Compression.GZIP
+    from(project.file("./scripts")) { into "scripts/" }
+    from(project.file("./conf")) { into "conf/" }
+    from(project(':samza-shell').file("src/main/bash/run-class.sh")) { into "scripts/" }
+    from(configurations.runtime) { into("lib/") }
+    from(configurations.archives.artifacts.files) { into("lib/") }
+    duplicatesStrategy 'exclude'
+  }
+}
+
 project(':samza-tools') {
   apply plugin: 'java'
 

checkstyle/checkstyle-suppressions.xml

@@ -1,8 +1,8 @@
 <?xml version="1.0"?>
 
 <!DOCTYPE suppressions PUBLIC
-     "-//Puppy Crawl//DTD Suppressions 1.0//EN"
-     "http://www.puppycrawl.com/dtds/suppressions_1_0.dtd">
+        "-//Checkstyle//DTD SuppressionFilter Configuration 1.2//EN"
+        "https://checkstyle.org/dtds/suppressions_1_2.dtd">
 
 <!--
      // Licensed to the Apache Software Foundation (ASF) under one or more
@@ -22,15 +22,10 @@
 -->
 
 <suppressions>
-<!-- example
-    <suppress checks="Indentation"
-           files="TestZkProcessorLatch.java"
-           lines="91-275"/>
-           -->
   <suppress checks="ConstantName"
             files="ApplicationStatus.java"
             lines="26-29"/>
-  <suppress checks="UnusedImports"
-            files="StreamApplication.java"/>
+  <suppress id="preventJavadocUnusedImports"
+            files=".*samza-api.*"/>
 </suppressions>
 

checkstyle/checkstyle.xml

@@ -34,7 +34,14 @@
   <module name="TreeWalker">
 
     <!-- code cleanup -->
-    <module name="UnusedImports"/>
+    <module name="UnusedImports">
+      <property name="id" value="allowJavadocUnusedImports"/>
+      <property name="processJavadoc" value="true"/>
+    </module>
+    <module name="UnusedImports"> <!-- suppressed for samza-api -->
+      <property name="id" value="preventJavadocUnusedImports"/>
+      <property name="processJavadoc" value="false"/>
+    </module>
     <module name="FileContentsHolder"/>
     <module name="RedundantImport"/>
     <module name="IllegalImport" />

docs/_blog/2017-08-27-announcing-the-release-of-apache-samza--0.13.1.md

@@ -26,7 +26,8 @@ excerpt_separator: <!--more-->
 -->
 
 
-Testing the excerpt
+A stability release to make Samza as an embedded library production ready   
+Samza as a library is part of Samza’s Flexible Deployment model
 
 <!--more-->
 

docs/_blog/2018-01-31-announcing-the-release-of-apache-samza--0.14.0.md

@@ -26,7 +26,10 @@ excerpt_separator: <!--more-->
 -->
 
 
-Testing the excerpt
+A major release with following highly anticipated features:  
+-   Samza SQL  
+-   Azure EventHubs producer, consumer and checkpoint provider  
+-   AWS Kinesis consumer  
 
 <!--more-->
 

docs/_blog/2018-07-19-stream_processing-meetup-summary.md

@@ -1,6 +1,6 @@
 ---
 layout: blog
-title: Recap of Stream Processing with Apache Kafka & Apache Samza (July '18)
+title: Our July 2018 meetup - A Report
 icon: analytics
 authors:
     - name:
@@ -25,18 +25,14 @@ excerpt_separator: <!--more-->
    limitations under the License.
 -->
 
-A look back at July edition of quarterly stream processing meetup
+On July 19, 2018, we hosted a community meetup at LinkedIn focussing on Apache Kafka, Apache Samza, and related streaming technologies.
+The event featured technical deep dives by engineers from LinkedIn and Uber on the latest in the stream processing space...
 
 <!--more-->
 
-
-On July 19th another successful stream processing meetup was hosted by LinkedIn! 
-This event focused on Apache Kafka, Apache Samza, and related streaming technologies. 
-This meetup was a full house and had techincal deep dives by engineers from LinkedIn and Uber on the latest
-and greatest in streaming tech
-
-<br>
-
+July 2018 - On July 19, 2018, we hosted a community meetup at LinkedIn focussing on Apache Kafka, Apache Samza, and related streaming technologies.
+The event featured technical deep dives by engineers from LinkedIn and Uber on the latest in the stream processing space. Here is a brief summary
+of the talks that were presented.
 
 ### [Beam me up Samza: How we built a Samza Runner for Apache Beam](https://youtu.be/o5GaifLoZho)
 

docs/_blog/2018-09-26-stangeloop-recap.md

@@ -1,12 +1,13 @@
 ---
 layout: blog
-title: Recap of Chasing Stream Processing Utopia
+title: On chasing the Stream Processing Utopia
 icon: analytics
 authors:
     - name:
       website: 
       image: 
 excerpt_separator: <!--more-->
+exclude_from_loop: true
 ---
 <!--
    Licensed to the Apache Software Foundation (ASF) under one or more
@@ -25,7 +26,8 @@ excerpt_separator: <!--more-->
    limitations under the License.
 -->
 
-Strange Loop, St. Louis, MO
+Talk By Kartik Paramasivam (Director of Engineering, Linkedin)   
+@Strange Loop, St. Louis, MO
 
 <!--more-->
 

docs/_case-studies/linkedin.md

@@ -5,6 +5,7 @@ title: Air Traffic Controller with Samza at LinkedIn
 study_domain: linkedin.com # just the domain, not the protocol
 priority: 4
 menu_title: LinkedIn # what shows up in the menu
+logo_url: https://upload.wikimedia.org/wikipedia/commons/c/ca/LinkedIn_logo_initials.png
 excerpt_separator: <!--more-->
 ---
 <!--

docs/_case-studies/optimizely.md

@@ -1,7 +1,7 @@
 ---
 layout: case-study
 hide_title: true # so we have control in case-study layout, but can still use page
-title: Real Time Session Aggregation
+title: On using Samza at Optimizely to compute analytics over session windows.
 study_domain: optimizely.com
 priority: 2
 menu_title: Optimizely
@@ -25,7 +25,7 @@ excerpt_separator: <!--more-->
    limitations under the License.
 -->
 
-Real Time Session Aggregation
+On using Samza at Optimizely to compute analytics over session windows
 
 <!--more-->