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

Josh Elser commented on ACCUMULO-697:
-------------------------------------

John, I should have mentioned that the "inspiration" for something like this 
came from the TypedValueCombiner. If someone is already instrumenting code to 
run in Accumulo (writing an SKVI), I see no reason why to not let them actually 
deal in the types which they want, rather than forcing them to deal with 
everything in terms of Key/Value.

Adam and Bill definitely hit on a larger issue of how far you can go with such 
an idea, but the scope of what I'll attempt here is much smaller than that.
                
> Break Scanner parameterization from Key,Value to Key,{Something}
> ----------------------------------------------------------------
>
>                 Key: ACCUMULO-697
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-697
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>
> When writing a custom iterator, many times the iterator has some semantic 
> knowledge of what each Key/Value being returned actually means (e.g. A word 
> count could be returning Key/Value but really is returning an Integer/Long 
> count in the Value). This forces the client to know what is going to be 
> returned and handle the cast/transformation.
> I believe it should be fairly straightforward to encapsulate this 
> transformation inside the Accumulo client code. I plan on investigating the 
> possibility of changing the ScannerBase impl, or perhaps making a 
> TypedScannerBase, in which the iterator at the "top" of the stack for a scan 
> can return something other than a Value to the client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to