[
https://issues.apache.org/jira/browse/PIG-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Dai updated PIG-2317:
----------------------------
Attachment: PIG-2317-8_plus.patch
I tried the latest patch. Find couple of issues in e2e tests in mapreduce mode.
I attach PIG-2317-8_plus.patch on top of Jonathan's patch. Here is what I did:
1. The original patch ship way too much files to the backend, my job.jar is
larger than 20G. I fix it by only ship necessary ruby files
2. ruby.jar will be registered automatically only when ruby UDF is used, same
mechanism as jython UDF
3. drop the dependency of pigudf.rb on pig.jar. All pig classes is assumed to
be in classpath
4. pigudf.rb will be shipped automatically if ruby UDF is used
5. bin/pig and e2e test changes to support the above changes
Other than these, patch looks good. +1 for commit once Julien's comments are
addressed.
> Ruby/Jruby UDFs
> ---------------
>
> Key: PIG-2317
> URL: https://issues.apache.org/jira/browse/PIG-2317
> Project: Pig
> Issue Type: New Feature
> Reporter: Jacob Perkins
> Assignee: Jonathan Coveney
> Priority: Minor
> Attachments: PIG-2317-8.patch, PIG-2317-8_plus.patch, PigUdf.rb,
> PigUdf.rb, jruby_scripting.patch, jruby_scripting_2_real.patch,
> jruby_scripting_3.patch, jruby_scripting_4.patch, jruby_scripting_5.patch,
> jruby_scripting_6.patch, jruby_scripting_7.patch, pigjruby.rb, pigjruby.rb,
> pigjruby.rb, pigudf.rb
>
>
> It should be possible to write UDFs in Ruby. These UDFs will be registered in
> the same way as python and javascript UDFs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
