8:45am PDT
> > To: dev@samza.apache.org
> > Subject: Re: Required vs. optional methods for KeyValueStore
> >
> > Hi Ken,
> >
> > We use putAll(list) when restoring from changelog. So, unless you don't
> > want your store to have support for changelog
T
> To: dev@samza.apache.org
> Subject: Re: Required vs. optional methods for KeyValueStore
>
> Hi Ken,
>
> We use putAll(list) when restoring from changelog. So, unless you don't
> want your store to have support for changelog, the implementation is
> required.
>
> I o
Hi Ken,
We use putAll(list) when restoring from changelog. So, unless you don't
want your store to have support for changelog, the implementation is
required.
I only have a high-level overview of what Solr is. Perhaps, others on the
mailing list have experience with Solr and can provide more usef
Hi all,
I'm looking at using embedded Solr as the KeyValueStore, as that lets me
extract ranked results from the state to publish as part of the task's
operation.
Some of the methods defined by KeyValueStore are problematic, though -
specifically the range() and all() methods that return itera
