Hi Ilya,
After the Map or List is created it will work like a normal in memory java
List or Map. We can simplify instantiating the object further though by
automatically generating the Key Prefixes in the StateFactory object and
only requiring the bucket to be specified once on the StateFactory li
Could this be an opportunity to abstract away the bucket/key relation? This is
a rather cumbersome mechanism. For the user, having a primary and secondary key
in this instance seems like it makes it more difficult to use the system easily.
Sent with Good (www.good.com)
Hi Tim,
+1
I think this is a very good idea. The only recommendation I have is to work
on this after ManagedState is reviewed and merged to Malhar.
IMO an interface needs to be backed by multiple implementations (at least
one). The AddressableState ( Store is too generic, just nitpicking) needs
a
There's a bug :)
should be
public void add(VALUE value)
{
addressableStore.set(size, value);
size++;
}
On Tue, Dec 8, 2015 at 11:57 AM, Timothy Farkas wrote:
> Hi all,
>
> There is currently a need for Spooled Lists and Heaps. I'd like to be able
> to leverage Chandni's large sta
