Hi, Razs, Thanks for you interest. Please open a Jira ticket and work on it. You can refer to https://cwiki.apache.org/confluence/display/PIG/HowToContribute
Daniel On Tue, Aug 19, 2014 at 8:34 AM, Razs Apps <razs.a...@gmail.com> wrote: > Hey guys, > > I've been using Pig for a couple months now. Like a lot of people online I > have had to write my own framework for helping with mocking in Pig as well > as other features. I would like to contribute to help improve PigUnit. I > wasn't sure of the best approach how to do this. The contribution page > said to send out an email or submit a Jira ticket. I wasn't sure which was > preferred or even how the community would want the issues broken down. > > Should I submit a ticket with a patch in it? > > I saw this existing issue that had mocking for as many variables as > possible: > https://issues.apache.org/jira/browse/PIG-2692 > > I didn't know if I should just create a Jira account and start working on > it and submit a patch? > > I also want to do just more than mocking and wanted to make to see if you > guys think it should be separated into different commits/patches or rolled > up into one improvement? Agile practices say separate them, but I'm not > sure how this project prefers the tasks to be broken down. > > * Allow mocking of as many aliases as possible mimicking the assertOutput > mock functionality > * By default STORE is disabled for all aliases. I'd like to make it that it > would allow specific aliases to be written out > * I want to investigate a better way for mocking more complex data sets > (bags, tuples, maps) since they do not currently mock that well given the > current format > * Create a builder for PigUnit/Constructor - I've found in the past wanting > to pass specific arguments to the constructor that I couldn't pass paired > with other variables. I also thought having a builder would help with > passing in parameters to execute the test. > > I will do wiki updates as well (I might need some direction on how to make > the updates when the time comes though). -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
