[
https://issues.apache.org/jira/browse/ACCUMULO-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419978#comment-13419978
]
John Vines commented on ACCUMULO-697:
-------------------------------------
I don't know why this is something we want to integrate into our API. A utility
can easily be written to do whatever transformations you want on top of the
scanner's iterator, so why push this down into our api? I think a change like
this could only serve to make the api harder to use for little to no real gain.
> 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
