[jira] [Updated] (PIG-3031) Update Pig to use a newer version of joda-time
[ https://issues.apache.org/jira/browse/PIG-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated PIG-3031: - Attachment: PIG-3031_1.patch Hi Cheolsoo, The problem is that DateTimeZone#forID becomes case-insensitively when receiving the timezone ID. See the following url: http://joda-time.sourceforge.net/upgradeto200.html And please try the newest patch. In addition, I think it should be good to include the following link: http://joda-time.sourceforge.net/timezones.html somewhere in the Pig manual, such that users can know what timezone IDs they can input. Thanks, Zhijie > Update Pig to use a newer version of joda-time > -- > > Key: PIG-3031 > URL: https://issues.apache.org/jira/browse/PIG-3031 > Project: Pig > Issue Type: Bug >Reporter: Jonathan Coveney >Assignee: Zhijie Shen > Fix For: 0.12 > > Attachments: PIG-3031_1.patch, PIG-3031.patch > > > The current version is 1.6, which is quite old (~4 years at this point). Is > there any reason not to bring us up to a newer version? I tried to compile > the 1.6 source and it didn't work because dependencies are outdated, and so > on. Also, the interfaces have matured. -- 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
[jira] Subscription: PIG patch available
Issue Subscription Filter: PIG patch available (28 issues) Subscriber: pigdaily Key Summary PIG-3123Simplify Logical Plans By Removing Unneccessary Identity Projections https://issues.apache.org/jira/browse/PIG-3123 PIG-3122Operators should not implicitly become reserved keywords https://issues.apache.org/jira/browse/PIG-3122 PIG-3114Duplicated macro name error when using pigunit https://issues.apache.org/jira/browse/PIG-3114 PIG-3109Missing license headers https://issues.apache.org/jira/browse/PIG-3109 PIG-3108HBaseStorage returns empty maps when mixing wildcard- with other columns https://issues.apache.org/jira/browse/PIG-3108 PIG-3105Fix TestJobSubmission unit test failure. https://issues.apache.org/jira/browse/PIG-3105 PIG-3098Add another test for the self join case https://issues.apache.org/jira/browse/PIG-3098 PIG-3088Add a builtin udf which removes prefixes https://issues.apache.org/jira/browse/PIG-3088 PIG-3069Native Windows Compatibility for Pig E2E Tests and Harness https://issues.apache.org/jira/browse/PIG-3069 PIG-3028testGrunt dev test needs some command filters to run correctly without cygwin https://issues.apache.org/jira/browse/PIG-3028 PIG-3027pigTest unit test needs a newline filter for comparisons of golden multi-line https://issues.apache.org/jira/browse/PIG-3027 PIG-3026Pig checked-in baseline comparisons need a pre-filter to address OS-specific newline differences https://issues.apache.org/jira/browse/PIG-3026 PIG-3025TestPruneColumn unit test - SimpleEchoStreamingCommand perl inline script needs simplification https://issues.apache.org/jira/browse/PIG-3025 PIG-3024TestEmptyInputDir unit test - hadoop version detection logic is brittle https://issues.apache.org/jira/browse/PIG-3024 PIG-3015Rewrite of AvroStorage https://issues.apache.org/jira/browse/PIG-3015 PIG-3010Allow UDF's to flatten themselves https://issues.apache.org/jira/browse/PIG-3010 PIG-2959Add a pig.cmd for Pig to run under Windows https://issues.apache.org/jira/browse/PIG-2959 PIG-2955 Fix bunch of Pig e2e tests on Windows https://issues.apache.org/jira/browse/PIG-2955 PIG-2873Converting bin/pig shell script to python https://issues.apache.org/jira/browse/PIG-2873 PIG-2834MultiStorage requires unused constructor argument https://issues.apache.org/jira/browse/PIG-2834 PIG-2764Add a biginteger and bigdecimal type to pig https://issues.apache.org/jira/browse/PIG-2764 PIG-2661Pig uses an extra job for loading data in Pigmix L9 https://issues.apache.org/jira/browse/PIG-2661 PIG-2645PigSplit does not handle the case where SerializationFactory returns null https://issues.apache.org/jira/browse/PIG-2645 PIG-2507Semicolon in paramenters for UDF results in parsing error https://issues.apache.org/jira/browse/PIG-2507 PIG-2417Streaming UDFs - allow users to easily write UDFs in scripting languages with no JVM implementation. https://issues.apache.org/jira/browse/PIG-2417 PIG-2312NPE when relation and column share the same name and used in Nested Foreach https://issues.apache.org/jira/browse/PIG-2312 PIG-1942script UDF (jython) should utilize the intended output schema to more directly convert Py objects to Pig objects https://issues.apache.org/jira/browse/PIG-1942 PIG-1237Piggybank MutliStorage - specify field to write in output https://issues.apache.org/jira/browse/PIG-1237 You may edit this subscription at: https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=13225&filterId=12322384
[jira] [Commented] (PIG-3135) HExecutionEngine should look for resources in user passed Properties
[
https://issues.apache.org/jira/browse/PIG-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561272#comment-13561272
]
Prashant Kommireddi commented on PIG-3135:
--
To get around the current limitation of depending on *site.xml files being set
on classpath, we could add a property "pig.use.override.configs" to be able to
provide your own configs and have JobConf be built from that.
Currently:
{code}
jc = new JobConf();
{code}
Proposal:
1. If "pig.use.override.configs" is present, generate JobConf using properties
{code}
jc = new JobConf(ConfigurationUtil.toConfiguration(properties));
{code}
This change would be backward compatible, and those who wish to bypass
classpath limitation can do so by setting the override property.
Thoughts?
> HExecutionEngine should look for resources in user passed Properties
>
>
> Key: PIG-3135
> URL: https://issues.apache.org/jira/browse/PIG-3135
> Project: Pig
> Issue Type: Bug
>Affects Versions: 0.10.0
>Reporter: Prashant Kommireddi
>
> Looking at this snippet:
> {code}
> private void init(Properties properties) throws ExecException {
> .
> .
> .
> // Check existence of hadoop-site.xml or core-site.xml
> Configuration testConf = new Configuration();
> ClassLoader cl = testConf.getClassLoader();
> URL hadoop_site = cl.getResource( HADOOP_SITE );
> URL core_site = cl.getResource( CORE_SITE );
>
> if( hadoop_site == null && core_site == null ) {
> throw new ExecException("Cannot find hadoop configurations in
> classpath (neither hadoop-site.xml nor core-site.xml was found in the
> classpath)." +
> " If you plan to use local mode, please put -x local
> option in command line",
> 4010);
> }
> {code}
> This assumes the resources (*-site.xml) are set on the classpath, but this
> will not always be the case when run with Pig's Java APIs. One could want to
> programatically set the resources and the code here should additionally check
> if they are available in there.
> Example: When a Configuration object is created and resources are added
> before passing it on to Pig.
> {code}
> Configuration conf = new Configuration(false);
> conf.addResource("foo/core-site.xml");
> conf.addResource("bar/hadoop-site.xml");
> PigServer pServer = new PigServer(ExecType.MAPREDUCE, conf);
> {code}
> The above conf is not used right now to obtain resources.
--
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
[jira] [Updated] (PIG-3109) Missing license headers
[ https://issues.apache.org/jira/browse/PIG-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated PIG-3109: Attachment: bugPIG-3109.patch I'm attaching patch that incorporates Chelsoo's improvement to releaseaudit task and add the license header for following file types: * *.xml * *.java * *.pig After applying this patch, I can see roughly 150 files without valid license, mostly test input files. I'm afraid that I can't simply change those files as I would broke tests. > Missing license headers > > > Key: PIG-3109 > URL: https://issues.apache.org/jira/browse/PIG-3109 > Project: Pig > Issue Type: Task >Affects Versions: 0.10.0, 0.10.1 >Reporter: Ashutosh Chauhan >Assignee: Jarek Jarcec Cecho >Priority: Blocker > Fix For: 0.11 > > Attachments: bugPIG-3109.patch, PIG-3109.patch, > PIG-3109-releaseaudit.patch > > > Quite a few files are missing AL. Also, almost all html files don't have > apache headers either. -- 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
[jira] [Updated] (PIG-3073) POUserFunc creating log spam for large scripts
[ https://issues.apache.org/jira/browse/PIG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Coveney updated PIG-3073: -- Resolution: Fixed Status: Resolved (was: Patch Available) > POUserFunc creating log spam for large scripts > -- > > Key: PIG-3073 > URL: https://issues.apache.org/jira/browse/PIG-3073 > Project: Pig > Issue Type: Bug >Affects Versions: 0.11, 0.12 >Reporter: Jonathan Coveney >Assignee: Jonathan Coveney > Fix For: 0.12 > > Attachments: PIG-3073-0.patch, PIG-3073-1.patch > > > POUserFunc got some new logging in the case where a JobConf isn't available. > In certain cases (huge scripts with tons of UDFs), this is creating gigantic > logs. -- 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
[jira] [Updated] (PIG-3082) outputSchema of a UDF allows two usages when describing a Tuple schema
[ https://issues.apache.org/jira/browse/PIG-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Coveney updated PIG-3082: -- Resolution: Fixed Status: Resolved (was: Patch Available) > outputSchema of a UDF allows two usages when describing a Tuple schema > -- > > Key: PIG-3082 > URL: https://issues.apache.org/jira/browse/PIG-3082 > Project: Pig > Issue Type: Bug >Reporter: Julien Le Dem >Assignee: Jonathan Coveney > Fix For: 0.12 > > Attachments: PIG-3082-0.patch, PIG-3082-1.patch > > > When defining an evalfunc that returns a Tuple there are two ways you can > implement outputSchema(). > - The right way: return a schema that contains one Field that contains the > type and schema of the return type of the UDF > - The unreliable way: return a schema that contains more than one field and > it will be understood as a tuple schema even though there is no type (which > is in Field class) to specify that. This is particularly deceitful when the > output schema is derived from the input schema and the outputted Tuple > sometimes contain only one field. In such cases Pig understands the output > schema as a tuple only if there is more than one field. And sometimes it > works, sometimes it does not. > We should at least issue a warning (backward compatibility) if not plain > throw an exception when the output schema contains more than one Field. -- 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
[jira] [Commented] (PIG-3073) POUserFunc creating log spam for large scripts
[ https://issues.apache.org/jira/browse/PIG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561181#comment-13561181 ] Daniel Dai commented on PIG-3073: - +1 > POUserFunc creating log spam for large scripts > -- > > Key: PIG-3073 > URL: https://issues.apache.org/jira/browse/PIG-3073 > Project: Pig > Issue Type: Bug >Affects Versions: 0.11, 0.12 >Reporter: Jonathan Coveney >Assignee: Jonathan Coveney > Fix For: 0.12 > > Attachments: PIG-3073-0.patch, PIG-3073-1.patch > > > POUserFunc got some new logging in the case where a JobConf isn't available. > In certain cases (huge scripts with tons of UDFs), this is creating gigantic > logs. -- 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
[jira] [Created] (PIG-3136) Introduce a syntax making declared aliases optional
Jonathan Coveney created PIG-3136: - Summary: Introduce a syntax making declared aliases optional Key: PIG-3136 URL: https://issues.apache.org/jira/browse/PIG-3136 Project: Pig Issue Type: Improvement Reporter: Jonathan Coveney Assignee: Jonathan Coveney Fix For: 0.12 This is something Daniel and I have talked about before, and now that we have the @ syntax, this is easy to implement. The idea is that relation names are no longer required, and you can instead use a fat arrow (obviously that can be changed) to signify this. The benefit is not having to engage in the mental load of having to name everything. One other possibility is just making "alias =" optional. I fear that that could be a little TOO magical, but I welcome opinions. -- 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
[jira] [Updated] (PIG-3082) outputSchema of a UDF allows two usages when describing a Tuple schema
[ https://issues.apache.org/jira/browse/PIG-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Coveney updated PIG-3082: -- Attachment: PIG-3082-1.patch Updated with a better message. Testing then will commit > outputSchema of a UDF allows two usages when describing a Tuple schema > -- > > Key: PIG-3082 > URL: https://issues.apache.org/jira/browse/PIG-3082 > Project: Pig > Issue Type: Bug >Reporter: Julien Le Dem >Assignee: Jonathan Coveney > Fix For: 0.12 > > Attachments: PIG-3082-0.patch, PIG-3082-1.patch > > > When defining an evalfunc that returns a Tuple there are two ways you can > implement outputSchema(). > - The right way: return a schema that contains one Field that contains the > type and schema of the return type of the UDF > - The unreliable way: return a schema that contains more than one field and > it will be understood as a tuple schema even though there is no type (which > is in Field class) to specify that. This is particularly deceitful when the > output schema is derived from the input schema and the outputted Tuple > sometimes contain only one field. In such cases Pig understands the output > schema as a tuple only if there is more than one field. And sometimes it > works, sometimes it does not. > We should at least issue a warning (backward compatibility) if not plain > throw an exception when the output schema contains more than one Field. -- 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
[jira] [Updated] (PIG-3073) POUserFunc creating log spam for large scripts
[ https://issues.apache.org/jira/browse/PIG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Coveney updated PIG-3073: -- Attachment: PIG-3073-1.patch ok enough laziness. Here is a patch which removes it. > POUserFunc creating log spam for large scripts > -- > > Key: PIG-3073 > URL: https://issues.apache.org/jira/browse/PIG-3073 > Project: Pig > Issue Type: Bug >Affects Versions: 0.11, 0.12 >Reporter: Jonathan Coveney >Assignee: Jonathan Coveney > Fix For: 0.12 > > Attachments: PIG-3073-0.patch, PIG-3073-1.patch > > > POUserFunc got some new logging in the case where a JobConf isn't available. > In certain cases (huge scripts with tons of UDFs), this is creating gigantic > logs. -- 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
[jira] [Updated] (PIG-3073) POUserFunc creating log spam for large scripts
[ https://issues.apache.org/jira/browse/PIG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Coveney updated PIG-3073: -- Status: Patch Available (was: Open) > POUserFunc creating log spam for large scripts > -- > > Key: PIG-3073 > URL: https://issues.apache.org/jira/browse/PIG-3073 > Project: Pig > Issue Type: Bug >Affects Versions: 0.11, 0.12 >Reporter: Jonathan Coveney >Assignee: Jonathan Coveney > Fix For: 0.12 > > Attachments: PIG-3073-0.patch, PIG-3073-1.patch > > > POUserFunc got some new logging in the case where a JobConf isn't available. > In certain cases (huge scripts with tons of UDFs), this is creating gigantic > logs. -- 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
[jira] [Updated] (PIG-3124) Push FLATTENs After FILTERs If Possible
[ https://issues.apache.org/jira/browse/PIG-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-3124: Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Patch committed to trunk. Thanks Nick! > Push FLATTENs After FILTERs If Possible > --- > > Key: PIG-3124 > URL: https://issues.apache.org/jira/browse/PIG-3124 > Project: Pig > Issue Type: Improvement > Components: impl >Affects Versions: 0.10.0 >Reporter: Nick White >Assignee: Nick White > Fix For: 0.12 > > Attachments: PIG-3124.0.patch, PIG-3124.1.patch > > > When optimizing a logical plan, it's safe to push a FLATTEN after a FILTER if > the columns being flattened don't occur in the expression that the filter is > being done on. When the FILTER comes first the FLATTEN generates fewer rows > (usually), and so is more efficient. -- 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
[jira] [Commented] (PIG-3031) Update Pig to use a newer version of joda-time
[ https://issues.apache.org/jira/browse/PIG-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561045#comment-13561045 ] Cheolsoo Park commented on PIG-3031: Yes, I used the patch that you provided on this jira. Thanks for taking a look at it. > Update Pig to use a newer version of joda-time > -- > > Key: PIG-3031 > URL: https://issues.apache.org/jira/browse/PIG-3031 > Project: Pig > Issue Type: Bug >Reporter: Jonathan Coveney >Assignee: Zhijie Shen > Fix For: 0.12 > > Attachments: PIG-3031.patch > > > The current version is 1.6, which is quite old (~4 years at this point). Is > there any reason not to bring us up to a newer version? I tried to compile > the 1.6 source and it didn't work because dependencies are outdated, and so > on. Also, the interfaces have matured. -- 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
[jira] [Commented] (PIG-3031) Update Pig to use a newer version of joda-time
[ https://issues.apache.org/jira/browse/PIG-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561043#comment-13561043 ] Zhijie Shen commented on PIG-3031: -- Hi Cheolsoo, Which version are you going to upgrade to? 2.1? I'd like to investigate the problem. Thanks, Zhijie > Update Pig to use a newer version of joda-time > -- > > Key: PIG-3031 > URL: https://issues.apache.org/jira/browse/PIG-3031 > Project: Pig > Issue Type: Bug >Reporter: Jonathan Coveney >Assignee: Zhijie Shen > Fix For: 0.12 > > Attachments: PIG-3031.patch > > > The current version is 1.6, which is quite old (~4 years at this point). Is > there any reason not to bring us up to a newer version? I tried to compile > the 1.6 source and it didn't work because dependencies are outdated, and so > on. Also, the interfaces have matured. -- 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
[jira] [Commented] (PIG-3031) Update Pig to use a newer version of joda-time
[
https://issues.apache.org/jira/browse/PIG-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561028#comment-13561028
]
Cheolsoo Park commented on PIG-3031:
Unfortunately, there is a failure:
{code}
Testcase: testConversionBetweenDateTimeAndString took 0.041 sec
Caused an ERROR
The datetime zone id 'asia/singapore' is not recognised
java.lang.IllegalArgumentException: The datetime zone id 'asia/singapore' is
not recognised
at org.joda.time.DateTimeZone.forID(DateTimeZone.java:223)
at org.apache.pig.builtin.ToDate3ARGS.exec(ToDate3ARGS.java:21)
at
org.apache.pig.test.TestBuiltin.testConversionBetweenDateTimeAndString(TestBuiltin.java:408)
{code}
> Update Pig to use a newer version of joda-time
> --
>
> Key: PIG-3031
> URL: https://issues.apache.org/jira/browse/PIG-3031
> Project: Pig
> Issue Type: Bug
>Reporter: Jonathan Coveney
>Assignee: Zhijie Shen
> Fix For: 0.12
>
> Attachments: PIG-3031.patch
>
>
> The current version is 1.6, which is quite old (~4 years at this point). Is
> there any reason not to bring us up to a newer version? I tried to compile
> the 1.6 source and it didn't work because dependencies are outdated, and so
> on. Also, the interfaces have matured.
--
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
[jira] [Commented] (PIG-2645) PigSplit does not handle the case where SerializationFactory returns null
[
https://issues.apache.org/jira/browse/PIG-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561025#comment-13561025
]
Alan Gates commented on PIG-2645:
-
Reviewing this patch
> PigSplit does not handle the case where SerializationFactory returns null
> -
>
> Key: PIG-2645
> URL: https://issues.apache.org/jira/browse/PIG-2645
> Project: Pig
> Issue Type: Bug
> Components: impl
>Affects Versions: 0.10.0
>Reporter: Alex Levenson
> Labels: patch
> Attachments: patch_2645.patch, PIG-2645.patch
>
>
> In PigSplit.java, line 254:
> {code}
> SerializationFactory sf = new SerializationFactory(conf);
> Serializer s = sf.getSerializer(wrappedSplits[0].getClass());
> s.open((OutputStream) os);
> {code}
> sf.getSerializer returns null when it cannot find a serializer for a given
> object. Instead of handling this properly, a NPE is thrown when s.open() is
> called.
> This is easy to encounter when creating a custom InputSplit from the
> mapreduce package which is an abstract class that DOES NOT implement Writable.
> However it's easy to miss because InputSplit from the mapred package is an
> interface that extends Writable, and InputSplits often both extend and
> implement both the new and old InputSplit abstract class and interface
> (thereby becoming Writable).
--
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
[jira] [Updated] (PIG-3073) POUserFunc creating log spam for large scripts
[ https://issues.apache.org/jira/browse/PIG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated PIG-3073: Status: Open (was: Patch Available) Canceling patch since it seems the feedback was to take a different direction. > POUserFunc creating log spam for large scripts > -- > > Key: PIG-3073 > URL: https://issues.apache.org/jira/browse/PIG-3073 > Project: Pig > Issue Type: Bug >Affects Versions: 0.11, 0.12 >Reporter: Jonathan Coveney >Assignee: Jonathan Coveney > Fix For: 0.12 > > Attachments: PIG-3073-0.patch > > > POUserFunc got some new logging in the case where a JobConf isn't available. > In certain cases (huge scripts with tons of UDFs), this is creating gigantic > logs. -- 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
[jira] [Updated] (PIG-3086) Allow A Prefix To Be Added To URIs In PigUnit Tests
[ https://issues.apache.org/jira/browse/PIG-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated PIG-3086: Resolution: Fixed Status: Resolved (was: Patch Available) Patch checked in. Thanks Nick. > Allow A Prefix To Be Added To URIs In PigUnit Tests > > > Key: PIG-3086 > URL: https://issues.apache.org/jira/browse/PIG-3086 > Project: Pig > Issue Type: New Feature > Components: grunt, tools >Affects Versions: 0.10.0 >Reporter: Nick White >Assignee: Nick White > Fix For: 0.12 > > Attachments: PIG-3086.patch > > > When running PigUnit tests that use the local file system it'd be useful to > re-write absolute paths in the pig script under test so you can "jail" the > data the test uses to a known folder. -- 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
[jira] [Assigned] (PIG-3086) Allow A Prefix To Be Added To URIs In PigUnit Tests
[ https://issues.apache.org/jira/browse/PIG-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates reassigned PIG-3086: --- Assignee: Nick White > Allow A Prefix To Be Added To URIs In PigUnit Tests > > > Key: PIG-3086 > URL: https://issues.apache.org/jira/browse/PIG-3086 > Project: Pig > Issue Type: New Feature > Components: grunt, tools >Affects Versions: 0.10.0 >Reporter: Nick White >Assignee: Nick White > Fix For: 0.12 > > Attachments: PIG-3086.patch > > > When running PigUnit tests that use the local file system it'd be useful to > re-write absolute paths in the pig script under test so you can "jail" the > data the test uses to a known folder. -- 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
[jira] [Assigned] (PIG-2878) Pig current releases lack a UDF equalIgnoreCase.This function returns a Boolean value indicating whether string left is equal to string right. This check is case insensiti
[ https://issues.apache.org/jira/browse/PIG-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates reassigned PIG-2878: --- Assignee: Arjun K R > Pig current releases lack a UDF equalIgnoreCase.This function returns a > Boolean value indicating whether string left is equal to string right. This > check is case insensitive. > -- > > Key: PIG-2878 > URL: https://issues.apache.org/jira/browse/PIG-2878 > Project: Pig > Issue Type: Bug > Components: internal-udfs >Affects Versions: 0.10.0 >Reporter: Arjun K R >Assignee: Arjun K R > Labels: features > Attachments: PIG-2878.patch > > > Pig current releases lack a UDF equalIgnoreCase.This function returns a > Boolean value indicating whether string left is equal to string right. This > check is case insensitive. -- 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
[jira] [Updated] (PIG-2878) Pig current releases lack a UDF equalIgnoreCase.This function returns a Boolean value indicating whether string left is equal to string right. This check is case insensitiv
[ https://issues.apache.org/jira/browse/PIG-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated PIG-2878: Status: Open (was: Patch Available) First, let me apologize for taking so long to get to this. We should have reviewed it a lot sooner. The patch looks fine. It needs tests however. You need to add unit tests to check that this UDF correctly compares strings. > Pig current releases lack a UDF equalIgnoreCase.This function returns a > Boolean value indicating whether string left is equal to string right. This > check is case insensitive. > -- > > Key: PIG-2878 > URL: https://issues.apache.org/jira/browse/PIG-2878 > Project: Pig > Issue Type: Bug > Components: piggybank >Affects Versions: 0.10.0 >Reporter: Arjun K R > Labels: features > Attachments: PIG-2878.patch > > > Pig current releases lack a UDF equalIgnoreCase.This function returns a > Boolean value indicating whether string left is equal to string right. This > check is case insensitive. -- 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
[jira] [Updated] (PIG-2878) Pig current releases lack a UDF equalIgnoreCase.This function returns a Boolean value indicating whether string left is equal to string right. This check is case insensitiv
[ https://issues.apache.org/jira/browse/PIG-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated PIG-2878: Component/s: (was: piggybank) internal-udfs > Pig current releases lack a UDF equalIgnoreCase.This function returns a > Boolean value indicating whether string left is equal to string right. This > check is case insensitive. > -- > > Key: PIG-2878 > URL: https://issues.apache.org/jira/browse/PIG-2878 > Project: Pig > Issue Type: Bug > Components: internal-udfs >Affects Versions: 0.10.0 >Reporter: Arjun K R > Labels: features > Attachments: PIG-2878.patch > > > Pig current releases lack a UDF equalIgnoreCase.This function returns a > Boolean value indicating whether string left is equal to string right. This > check is case insensitive. -- 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
[jira] [Commented] (PIG-3005) TestLargeFile#testOrderBy is failing
[ https://issues.apache.org/jira/browse/PIG-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560836#comment-13560836 ] Cheolsoo Park commented on PIG-3005: Well, I take back what I said. :-) > TestLargeFile#testOrderBy is failing > > > Key: PIG-3005 > URL: https://issues.apache.org/jira/browse/PIG-3005 > Project: Pig > Issue Type: Bug > Environment: Mac OSX 10.6.8 >Reporter: Jonathan Coveney > Fix For: 0.12 > > > When run locally, at least, this test is failing for me. > Has anyone else noticed this failing? -- 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
