[
https://issues.apache.org/jira/browse/PIG-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584242#action_12584242
]
Charlie Groves commented on PIG-55:
-----------------------------------
Ahh, I didn't realize it was failing from ant for you as well. Ant didn't get
support for JUnit 4 tests until 1.7, so if you're running an earlier version,
its runner won't pick them up. I assumed JUnit 4 style tests were acceptable
for pig since several tests are using the @Test, @Before and @After
annotations, but it looks all of those tests are also using the JUnit 3 style
TestCase extension and method naming conventions. If we don't want to require
Ant 1.7, I'm fine with converting the test to be JUnit 3 style. However, if
we're going to do that, I'd like to fix the existing tests so they don't use
both JUnit 3 and 4 styles.
> Allow user control over split creation
> --------------------------------------
>
> Key: PIG-55
> URL: https://issues.apache.org/jira/browse/PIG-55
> Project: Pig
> Issue Type: Improvement
> Affects Versions: 0.0.0
> Reporter: Charlie Groves
> Fix For: 0.1.0
>
> Attachments: pig_chunker_split.patch, pig_chunker_split_v2.patch,
> pig_chunker_split_v3.patch, pig_chunker_split_v4.patch,
> pig_chunker_split_v5.patch, replaceable_PigSplit.diff,
> replaceable_PigSplit_v2.diff
>
>
> I have a dataset in HDFS that's stored in a file per column that I'd like to
> access from pig. This means I can't use LoadFunc to get at the data as it
> only allows the loader access to a single input stream at a time. To handle
> this usage, I've broken the existing split creation code out into a few
> classes and interfaces, and allowed user specified load functions to be used
> in place of the existing code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
