You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/06/03 20:40:00 UTC

[jira] [Commented] (HBASE-13583) AOT compile our JRuby

    [ https://issues.apache.org/jira/browse/HBASE-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125300#comment-17125300 ] 

Nick Dimiduk commented on HBASE-13583:
--------------------------------------

bq. which means we'll get neither startup speedup or java method invocation validation.

:(

> AOT compile our JRuby
> ---------------------
>
>                 Key: HBASE-13583
>                 URL: https://issues.apache.org/jira/browse/HBASE-13583
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, scripts, shell
>            Reporter: Nick Dimiduk
>            Priority: Major
>         Attachments: HBASE-13583.patch, HBASE-13583.v2.patch, HBASE-13583.v3.patch, HBASE-13583.v4.patch
>
>
> Our Jruby code seems to not keep up well with Java changes. We should investigate adding a compilation step for our shell and the rb scripts in bin to ensure they're calling methods that exist on classes that exist. This looks like as good a starting point as any: https://github.com/jruby/jruby/wiki/GeneratingJavaClasses



--
This message was sent by Atlassian Jira
(v8.3.4#803005)