You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gary Helmling (JIRA)" <ji...@apache.org> on 2011/06/28 20:40:20 UTC
[jira] [Resolved] (HBASE-3516) Coprocessors: add test cases for
loading coprocessor jars from hdfs and local fs.
[ https://issues.apache.org/jira/browse/HBASE-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Helmling resolved HBASE-3516.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.92.0
Committed to trunk. Thanks for the patch Mingjie. And thanks Ted and Stack for the reviews.
> Coprocessors: add test cases for loading coprocessor jars from hdfs and local fs.
> ----------------------------------------------------------------------------------
>
> Key: HBASE-3516
> URL: https://issues.apache.org/jira/browse/HBASE-3516
> Project: HBase
> Issue Type: Improvement
> Components: coprocessors
> Affects Versions: 0.90.0
> Reporter: Mingjie Lai
> Assignee: Mingjie Lai
> Fix For: 0.92.0
>
> Attachments: HBase3516-2.patch
>
>
> Loading coprocessors classes from jar files (at hdfs or local fs) is supported from CP framework right now. We used to have a test case to cover this scenario which uses an base-64 encoded string at the test case to represent a compiled jar file. This hardcoded way was not acceptable as a valid test case, so we removed it eventually.
> We need to have a better way to redo this case. Option 1) modify maven file in order to compile a test cp class into jar, and put it to hdfs and local fs, and run the cp class loading test; option 2) use Java 6.0 Compiler API to compile the test case at runtime and create the jar file?
> Need more time to investigate which one is better.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira