[
https://issues.apache.org/jira/browse/PIG-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764307#comment-13764307
]
Jacob Perkins commented on PIG-3453:
------------------------------------
I like the idea of a PoC. I hadn't really thought about the case that you'd
want to run the same aggregations in real time as you would against your
warehouse. It sure makes a lot of sense. Mostly I was thinking of language
reuse; complex stream aggregations using the same familiar data flow syntax of
Pig.
More examples of the translation from Pig scripts to trident topologies would
be helpful. It'd be motivation enough to see the amount of boilerplate, etc,
required to write a trident topology versus a pig script side by side. I've
been working from a word count since it's sort of the canonical example.
I'm currently focusing on mapping Pig's LogicalPlan to a TridentTopology. Other
really helpful things (that I'm less likely to make fast progress on) include
defining a new operator for spouts, called 'tap' and some planning/discussion
for a new operator for persisting state.
[~pradeepg26] - Anything else? It'd be nice to get a sense of who's
working/willing to work on this and where we're at now.
> Implement a Storm backend to Pig
> --------------------------------
>
> Key: PIG-3453
> URL: https://issues.apache.org/jira/browse/PIG-3453
> Project: Pig
> Issue Type: New Feature
> Reporter: Pradeep Gollakota
> Labels: storm
>
> There is a lot of interest around implementing a Storm backend to Pig for
> streaming processing. The proposal and initial discussions can be found at
> https://cwiki.apache.org/confluence/display/PIG/Pig+on+Storm+Proposal
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
