[
https://issues.apache.org/jira/browse/PIG-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811537#comment-13811537
]
Cheolsoo Park commented on PIG-3453:
------------------------------------
Usually, we create a feature branch for a big feature and merge it to trunk
after fully developed/tested. Although it's totally possible to develop it in
your personal repo and post a giant patch at one shot, the bigger the patch is,
the longer it takes to be reviewed. So I recommend to create subtasks and
incrementally commit small patches. To do that, you will need a svn branch
because you can't resolve jiras w/o committing patches.
The Pig git repo is a read-only mirror of svn repo. So unfortunately, patches
need to be posted in jiras to get committed. Since you don't have commit access
to svn repo, it will be helpful to have at least one committer in the loop.
Does this make sense?
> Implement a Storm backend to Pig
> --------------------------------
>
> Key: PIG-3453
> URL: https://issues.apache.org/jira/browse/PIG-3453
> Project: Pig
> Issue Type: New Feature
> Affects Versions: 0.13.0
> Reporter: Pradeep Gollakota
> Assignee: Jacob Perkins
> Labels: storm
> Fix For: 0.13.0
>
> Attachments: storm-integration.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
