Open keith-turner opened 8 years ago
Is this still relevant? If so I'd like to give it a shot
@jkosh44 I am uncertain about this issue at the moment. There was the work done in #923 which should be considered. Also the scanner builder API has a byRow() method that would not make sense for multiple spans.
For the moment, I think many (but not all) of the use case for this are satisfied by the snap.get(Collection<RowColumn>)
method. Also, I have been thinking about an asynchronous API that may be more convenient than this and some of the other get methods. I need to write that up.
@jkosh44 would you be interested in prototyping #967 ? Its very open ended, I am not even sure what the best way to implement it is. If you are interested I can post some notes on what I think may be a possible way to implement it, but I am not sure if it would work.
I'd definitely be interested in giving it a shot.
The original intent of #626 was to support fetching multiple Spans. This was not done because the result may not fit into memory. At the time when #626 was worked on the Scanner API was in a bad state. After the scanner the scanner API improvements in #639, it would be relatively easy to add multiple spans to the API. Could support something like the following.
Multiple spans may result in out of order key iteration.