[
https://issues.apache.org/jira/browse/SAMZA-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14140904#comment-14140904
]
Jay Kreps commented on SAMZA-390:
---------------------------------
I agree that the overwhelming advantage of something SQL-like is the fact that
95+% of engineers know it. Since we are trying to popularize a streaming model
of computation that is unfamilar to perhaps 98% of people having something that
is simple to understand and has a close analogy to something people already
know would be ideal.
I think another aspect to consider is access to state. I think having a notion
of tables and streams would be good. So say you have a changelog stream for
your user database and want to augment page views with the company of the user
viewing the page you would do something like
{code}
create table user_companies as select user_id, company_id from users keyed by
user_id;
create stream as select u.company_id, p.* from user_companies u join pageviews
p on u.user_id = p.user_id;
{code}
> High-Level Language for Samza
> -----------------------------
>
> Key: SAMZA-390
> URL: https://issues.apache.org/jira/browse/SAMZA-390
> Project: Samza
> Issue Type: New Feature
> Reporter: Raul Castro Fernandez
> Priority: Minor
> Labels: project
>
> Discussion about high-level languages to define Samza queries. Queries are
> defined in this language and transformed to a dataflow graph where the nodes
> are Samza jobs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
