accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Holiday (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3718) not possible to create a Mutation object from scala w/o some extra helper code
Date Thu, 09 Apr 2015 16:52:12 GMT


David Holiday commented on ACCUMULO-3718:

poop - i can't promise to deliver by next week. we've got a deadline next week that i can't
blow off. i would like to start participating more though. let me talk to my team lead and
see if i can't get them to let me devote a bit of time to this per week. me digging into the
accumulo code will definitely help me be a more effective engineer leveraging it. 

> not possible to create a Mutation object from scala w/o some extra helper code
> ------------------------------------------------------------------------------
>                 Key: ACCUMULO-3718
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.5.2, 1.6.2
>            Reporter: David Holiday
>            Priority: Blocker
>             Fix For: 1.5.3, 1.7.0, 1.6.3
> issue: 
> it's not possible to create a Mutation object from scala without employing a standalone
java jar wrapper. the preferred method for creating the object has you do it in two stages:
create with table row, then employ Mutation.put() to populate the object with the actual mutation
data. when you do this in scala, you get a
> java.lang.IllegalStateException: Can not add to mutation after serializing it at
at at
> error. I *think* this has something to do with the byte array going out of scope in Scala
but somehow not in Java. If you concat the operations (constuctor().put(data, data, ...) you
don't run into the error, but scala sees a Unit return type, so you can't actually add the
mutation to a BatchWriter. The only way I was able to get around this was to create a stand-alone
jar with a method that created then returned a populated mutation object. 
> I wasn't sure whether or not to call this a bug or an enhancement. given that you probably
want Accumulo to play nice with Scala I decided to call it a bug. 
> below is a link to the stack overflow thread I created whilst figuring all this out:


This message was sent by Atlassian JIRA

View raw message