[GitHub] [samza] prateekm commented on a change in pull request #1189: Update Documentation

[GitBox <gi...@apache.org>]

prateekm commented on a change in pull request #1189: Update Documentation
URL: https://github.com/apache/samza/pull/1189#discussion_r335131814
 
 

 ##########
 File path: docs/learn/documentation/versioned/container/state-management.md
 ##########
 @@ -23,7 +23,7 @@ One of the more interesting features of Samza is stateful stream processing. Tas
 
 Some stream processing jobs don't require state: if you only need to transform one message at a time, or filter out messages based on some condition, your job can be simple. Every call to your task's [process method](../api/overview.html) handles one incoming message, and each message is independent of all the other messages.
 
-However, being able to maintain state opens up many possibilities for sophisticated stream processing jobs: joining input streams, grouping messages and aggregating groups of messages. By analogy to SQL, the *select* and *where* clauses of a query are usually stateless, but *join*, *group by* and aggregation functions like *sum* and *count* require state. Samza doesn't yet provide a higher-level SQL-like language, but it does provide lower-level primitives that you can use to implement streaming aggregation and joins.
+However, being able to maintain state opens up many possibilities for sophisticated stream processing jobs: joining input streams, grouping messages and aggregating groups of messages. By analogy to SQL, the *select* and *where* clauses of a query are usually stateless, but *join*, *group by* and aggregation functions like *sum* and *count* require state. Samza supports [Samza SQL](/learn/documentation/{{site.version}}/api/samza-sql.html) for higher-level SQL-like language and [Beam API](/learn/documentation/{{site.version}}/api/beam-api.html) for streaming aggregation and joins.
 
 Review comment:
   @kw2542 Is this page reachable from the existing documentation? Or is this part of the old documentation as well?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services