[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740159#comment-14740159 ] Daniel Dai commented on PIG-3294: - This should be a Parquet issue. I upload a patch to PARQUET-334. > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14719959#comment-14719959 ] li xiang commented on PIG-3294: --- Hi Daniel, just an update, no UT failure caused by the change above. > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14719960#comment-14719960 ] li xiang commented on PIG-3294: --- Hi Daniel, just an update, no UT failure caused by the change above. > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[
https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717037#comment-14717037
]
li xiang commented on PIG-3294:
---
Hi Daniel,
Sorry for not responding you quickly. I am trying to debug/fix a Parquet UT
failure which I found has something to do with the change on
ExpToPhyTranslationVisitor.java by this JIRA.
The test case is testPigScript() of
https://github.com/apache/parquet-mr/blob/master/parquet-pig/src/test/java/org/apache/parquet/pig/summary/TestSummary.java.
It failed with a null pointer exception(please see the first comment in
PARQUET-334).
Class Summary
(https://github.com/apache/parquet-mr/blob/master/parquet-pig/src/main/java/org/apache/parquet/pig/summary/Summary.java)
extends EvalFunc of Pig. EvalFunc has a private field inputSchemaInternal and
provides both setInputSchema() and getInputSchema() to set and return
inputSchemaInternal. But Summary provides a different one called
inputSchema(vs. inputSchemaInternal) and only provides the setter
setInputSchema(), no getter. I think it might not be reasonable, so opened
PARQUET-365 and provide the getter to return inputSchema as the fix.
In setInputSchema() of Summary, do you think it is reasonable to get the schema
of tuple by using the following?
{code}
this.inputSchema = input.getField(0).schema.getField(0).schema;
{code}
Further, the adding of "((EvalFunc)
f).setInputSchema(((POUserFunc)p).getFunc().getInputSchema())"(as follow) makes
setInputSchema() of Summary called twice. In ExpToPhyTranslationVisitor
{code}
510 if (((POUserFunc)p).getFunc().getInputSchema() == null) {
511((POUserFunc)p).setFuncInputSchema(op.getSignature()); <--
call setInputSchema()
512 ((EvalFunc)
f).setInputSchema(((POUserFunc)p).getFunc().getInputSchema());<-- add this
line, call setInputSchema() again
513 }
{code}
I printed the result of each step of "this.inputSchema =
input.getField(0).schema.getField(0).schema"
Here is the first call of setInputSchema(), by setFuncInputSechema() of
POUserFunc
==
In Summary - SetInputSchema() - input = {A: {(a: chararray,a1: chararray,b:
int,c: {t: (a2: chararray,b2: map[])})}}
In Summary - SetInputSchema() - input.getField(0) = A: bag({(a: chararray,a1:
chararray,b: int,c: {t: (a2: chararray,b2: map[])})})
In Summary - SetInputSchema() - input.getField(0).schema = {(a: chararray,a1:
chararray,b: int,c: {t: (a2: chararray,b2: map[])})}
In Summary - SetInputSchema() - input.getField(0).schema.getField(0) =
tuple({a: chararray,a1: chararray,b: int,c: {t: (a2: chararray,b2: map[])}})
In Summary - SetInputSchema() - input.getField(0).schema.getField(0).schema =
{a: chararray,a1: chararray,b: int,c: {t: (a2: chararray,b2: map[])}}
==
Here is the second call of setInputSchema(), by
{code}
((EvalFunc) f).setInputSchema(((POUserFunc)p).getFunc().getInputSchema())
{code}
==
In Summary - SetInputSchema() - input = {a: chararray,a1: chararray,b: int,c:
{t: (a2: chararray,b2: map[])}}
In Summary - SetInputSchema() - input.getField(0) = a: chararray
In Summary - SetInputSchema() - input.getField(0).schema = null <--- So the
null pointer exception is here.
==
So, to fix this error,
(1) do you think it is not quite reasonable to get the schema of tuple in class
Summary like this
{code}
this.inputSchema = input.getField(0).schema.getField(0).schema;
{code}
(2) Or on Pig side, does it make sense to check if the schema has been set
before calling setInputSchema() again, maybe like the following change onto
ExpToPhyTranslationVisitor
{code}
if (((POUserFunc)p).getFunc().getInputSchema() == null) {
System.out.println("In visit, if == null");
((POUserFunc)p).setFuncInputSchema(op.getSignature());
if (((POUserFunc)p).getFunc().getInputSchema() == null) { // Check before
calling again
((EvalFunc)
f).setInputSchema(((POUserFunc)p).getFunc().getInputSchema());
}
}
{code}
Thanks for your time, thanks!
> Allow Pig use Hive UDFs
> ---
>
> Key: PIG-3294
> URL: https://issues.apache.org/jira/browse/PIG-3294
> Project: Pig
> Issue Type: New Feature
>Reporter: Daniel Dai
>Assignee: Daniel Dai
> Labels: gsoc2013, java
> Fix For: 0.15.0
>
> Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch,
> PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch
>
>
> It would be nice if Pig provide some interoperability with Hive. We can wrap
> Hive UDF in Pig so we can use Hive UDF in Pig.
> This is a candidate project for Google summer of code 2013. More information
> about the program can be found at
> https://cwiki.apache.org/confluence/display/PIG/GSoc2013
--
This message
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653108#comment-14653108 ] Daniel Dai commented on PIG-3294: - setFuncInputSchema does invoke setInputSchema. However, there is a tiny difference. setFuncInputSchema skip setting setInputSchema when it cannot find schema from UDFContext for the alias. I want to set schema no matter the UDFContext is. Does it cause any trouble for you? > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[
https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628026#comment-14628026
]
li xiang commented on PIG-3294:
---
Thanks Jeff, I re-post my question here :
Regarding Daniel's change on ExpToPhyTranslationVisitor.java
{code}
510 if (((POUserFunc)p).getFunc().getInputSchema() == null) {
511((POUserFunc)p).setFuncInputSchema(op.getSignature());
<-- call setInputSchema()
512 ((EvalFunc)
f).setInputSchema(((POUserFunc)p).getFunc().getInputSchema());<-- add this
line, call setInputSchema() again
513 }
{code}
SetFuncInputSchema() of class POUserFunc will call setInputSchema(), as
{code}
619 public void setFuncInputSchema(String signature) {
620 Properties props =
UDFContext.getUDFContext().getUDFProperties(func.getClass());
621 Schema
tmpS=(Schema)props.get("pig.evalfunc.inputschema."+signature);
622 if(tmpS!=null) {
623 this.func.setInputSchema(tmpS); <-- here
624 }
625 }
{code}
My question if why you add a line to call setInputSchema() again. Thanks!
> Allow Pig use Hive UDFs
> ---
>
> Key: PIG-3294
> URL: https://issues.apache.org/jira/browse/PIG-3294
> Project: Pig
> Issue Type: New Feature
>Reporter: Daniel Dai
>Assignee: Daniel Dai
> Labels: gsoc2013, java
> Fix For: 0.15.0
>
> Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch,
> PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch
>
>
> It would be nice if Pig provide some interoperability with Hive. We can wrap
> Hive UDF in Pig so we can use Hive UDF in Pig.
> This is a candidate project for Google summer of code 2013. More information
> about the program can be found at
> https://cwiki.apache.org/confluence/display/PIG/GSoc2013
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[
https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626636#comment-14626636
]
Jeff Zhang commented on PIG-3294:
-
[~water] You can make your code formatted like this
{noformat}
{code}
// your code here
{code}
{noformat}
> Allow Pig use Hive UDFs
> ---
>
> Key: PIG-3294
> URL: https://issues.apache.org/jira/browse/PIG-3294
> Project: Pig
> Issue Type: New Feature
>Reporter: Daniel Dai
>Assignee: Daniel Dai
> Labels: gsoc2013, java
> Fix For: 0.15.0
>
> Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch,
> PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch
>
>
> It would be nice if Pig provide some interoperability with Hive. We can wrap
> Hive UDF in Pig so we can use Hive UDF in Pig.
> This is a candidate project for Google summer of code 2013. More information
> about the program can be found at
> https://cwiki.apache.org/confluence/display/PIG/GSoc2013
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626540#comment-14626540 ] li xiang commented on PIG-3294: --- HI Daniel, I do not know why the format is messed up... My question is : ((POUserFunc)p).setFuncInputSchema(op.getSignature()) already calls setInputSchema() of class EvalFunc. Why you add a line --> ((EvalFunc)f).setInputSchema(((POUserFunc)p).getFunc().getInputSchema()) to call getInputSchema() again ? > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[
https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626516#comment-14626516
]
li xiang commented on PIG-3294:
---
HI Daniel, this is xiang and I am reading the code relating to this JIRA.
Regarding your change on ExpToPhyTranslationVisitor.java
if (((POUserFunc)p).getFunc().getInputSchema() == null) {
((POUserFunc)p).setFuncInputSchema(op.getSignature()); <--
call setInputSchema()
((EvalFunc)
f).setInputSchema(((POUserFunc)p).getFunc().getInputSchema()); <-- add this
line, call setInputSchema() again
}
SetFuncInputSchema() of class POUserFunc will call setInputSchema(), as
/**
* Sets EvalFunc's inputschema based on the signature
* @param signature
*/
public void setFuncInputSchema(String signature) {
Properties props =
UDFContext.getUDFContext().getUDFProperties(func.getClass());
Schema tmpS=(Schema)props.get("pig.evalfunc.inputschema."+signature);
if(tmpS!=null) {
this.func.setInputSchema(tmpS); <-- here
}
}
But the line you added calls setInputSchema() in class EvalFunc again.
Why do you mean to call setInputSchema() twice ?
> Allow Pig use Hive UDFs
> ---
>
> Key: PIG-3294
> URL: https://issues.apache.org/jira/browse/PIG-3294
> Project: Pig
> Issue Type: New Feature
>Reporter: Daniel Dai
>Assignee: Daniel Dai
> Labels: gsoc2013, java
> Fix For: 0.15.0
>
> Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch,
> PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch
>
>
> It would be nice if Pig provide some interoperability with Hive. We can wrap
> Hive UDF in Pig so we can use Hive UDF in Pig.
> This is a candidate project for Google summer of code 2013. More information
> about the program can be found at
> https://cwiki.apache.org/confluence/display/PIG/GSoc2013
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548209#comment-14548209 ] Daniel Dai commented on PIG-3294: - [~cheolsoo], 1. If you are using Hive 0.14.0, you will need hive-exec-core.jar, hive-common.jar, hive-serde.jar, hive-shims.jar, hive-shims-common.jar, hive-shims-common-secure.jar, kryo.jar in classpath. Hive 0.15.0 need a slightly different jar list. 2. There are minor number of Hive UDFs do not work with Pig because of the mistakes in Hive UDF in Hive 0.14, that is what HIVE-9767 fix. However, almost all useful Hive UDFs work without HIVE-9767. HIVE-9766 is included in Pig 0.15.0 and will be removed in future with the patch checked into Hive codebase. > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548184#comment-14548184 ] Cheolsoo Park commented on PIG-3294: [~daijy], thank you for the great work! I am interested in deploying this feature in production. What I don't fully understand is its dependency on Hive. So my questions are- # What Hive jars do I need in classpath to use Hive UDFs in Pig (if there is any)? # What does HIVE-9767 do? Do I need to backport it to my Hive release? (Looks like HIVE-9766 is included in the patch.) > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484012#comment-14484012 ] Alan Gates commented on PIG-3294: - +1. I agree it makes sense to make HCatLoader/Storer share the conversion code. We can file a separate JIRA for that. > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-5.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393792#comment-14393792 ] Daniel Dai commented on PIG-3294: - bq. The checking in of Hive code is ugly. We need to make sure that gets removed before a release so we don't end up forking. Sure, the duplication is ugly. I already commented on the code "Will remove once we switch to use Hive 1.2.0". I expect to remove those classes in the next release. However, in this release, I don't want to create a dependency on Hive 1.2.0. That will complicate the release process. Those classes are simple enough and don't likely to cause trouble for a short while. bq. In POForEach you are visiting the physical plan at run time to determine if we need the last record Yes, I can cache the flag and not do this in the backend. Will update patch shortly. bq. HiveUtils.java: much of this code to convert Hive types to Pig types must already be in HCat. Is it not possible to re-use that? Sure, we can consolidate these code. Since Pig don't depend on HCat, but HCat depends on Pig, I guess we shall rework HCat to use the same code to do the type conversion. > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393057#comment-14393057 ] Alan Gates commented on PIG-3294: - The checking in of Hive code is ugly. We need to make sure that gets removed before a release so we don't end up forking. In POForEach you are visiting the physical plan at run time to determine if we need the last record. Could this not be done at compile time to save time and runtime? HiveUtils.java: much of this code to convert Hive types to Pig types must already be in HCat. Is it not possible to re-use that? > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PIG-3294) Allow Pig use Hive UDFs
[ https://issues.apache.org/jira/browse/PIG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391721#comment-14391721 ] Daniel Dai commented on PIG-3294: - One use case enabled by this patch is Hivemall, see: https://github.com/daijyc/hivemall/wiki/PigHome. > Allow Pig use Hive UDFs > --- > > Key: PIG-3294 > URL: https://issues.apache.org/jira/browse/PIG-3294 > Project: Pig > Issue Type: New Feature >Reporter: Daniel Dai >Assignee: Daniel Dai > Labels: gsoc2013, java > Fix For: 0.15.0 > > Attachments: PIG-3294-1.patch, PIG-3294-2.patch, PIG-3294-3.patch, > PIG-3294-4.patch, PIG-3294-before-refactory.patch > > > It would be nice if Pig provide some interoperability with Hive. We can wrap > Hive UDF in Pig so we can use Hive UDF in Pig. > This is a candidate project for Google summer of code 2013. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2013 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
