accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Loss (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1993) proxy classes conflict with Ruby system classes
Date Mon, 09 Dec 2013 19:24:08 GMT

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

Brian Loss commented on ACCUMULO-1993:
--------------------------------------

It depends... At the thrift communication level, it doesn't cause any problems.  Anyone who
uses the new IDL to generate Ruby proxies would have to modify their Ruby code to reflect
the namespace change.  But, they'd be able to use the Range class.  It seems much less fragile
than renaming the Range class, but that's just my $0.02.

While I'm thinking about it, does Python have a range class too?  Will we run into the same
problem there?

> proxy classes conflict with Ruby system classes
> -----------------------------------------------
>
>                 Key: ACCUMULO-1993
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1993
>             Project: Accumulo
>          Issue Type: Bug
>          Components: proxy
>    Affects Versions: 1.4.4, 1.5.0
>            Reporter: Brian Loss
>
> The proxy declares the Range class, however this class also exists as a Ruby system class,
which causes problems when attempting to construct ranges.  Really, all the generated classes
for Ruby should be placed in an Accumulo namespace.  Add the appropriate declaration, such
as
> {code}
> namespace rb Accumulo
> {code}
> to the proxy thrift IDL.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message