You cannot feasibly hold onto some intermediate batch of nodes in
memory. You're invalidating the general premise of how Accumulo
iterators are meant to work in doing this. Further, an Iterator can
_only_ safely operate within one row of a table. Two adjacent rows may
be located on two different physical machines.
Would suggest you read through this presentation and try to take some
time to understand why they did it this way:
http://www.pdl.cmu.edu/SDI/2013/slides/big_graph_nsa_rd_2013_56002v1.pdf.
You might also be able to take something from Shana Hutchison's work on
Graphulo: https://arxiv.org/abs/1606.07085
On 3/29/19 2:20 PM, Enas Alkawasmi wrote:
Thank you for this suggestion. i have one question, c I pass options to the
new source that are from the result of the current iterator? . the new
iterator need to get the parent nodes from the the current one how can
enforce the iterator to wait for the result form its preceding iterator?
--
Sent from: http://apache-accumulo.1065345.n5.nabble.com/Developers-f3.html
