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

Chris McCubbin commented on ACCUMULO-482:
-----------------------------------------

I just uploaded a patch that addresses many of the issues raised here and on 
the review board. Major changes include:

-Scanners can be closed and the map they are stored in is now a Guava cache set 
for LRU kickout and time-based kickout.
-Writers can be one-shot as before, or you can create one and re-use it.
-The data classes are now proxy-specific and the thrift does not depend on 
accumulo's internal thrift. Most of the data classes are named P* when there is 
a identically named accumulo class (PKey, etc). I know that's not so attractive 
but it makes the code much less error-prone when converting between accumulo 
Keys and PKeys.
-PMutations have been added for writing. Adam and I discussed the fact that 
column updates can be confusing to create directly so this class has a set of 
key-values to add and a set to delete. An exception is thrown if the key's row 
doesn't match the mutation's row.
-Bugfixes and additional unit tests

Please review and let me know if you have more suggestions. Thanks.
                
> Add a thrift proxy server
> -------------------------
>
>                 Key: ACCUMULO-482
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-482
>             Project: Accumulo
>          Issue Type: New Feature
>            Reporter: Sapan Shah
>            Assignee: Chris McCubbin
>         Attachments: accumulo482patch-A.diff, accumulo482patch.diff
>
>
> Add a thrift proxy server to make integration with other languages besides 
> Java a bit easier.  This should work like 
> http://wiki.apache.org/hadoop/Hbase/ThriftApi.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to