In the latests release I noticed I get a LazyStoreClient back - which
for some reason breaks a particular part of my code (don't know why
yet). Is there a way to force the factory to give me a DefaultClient
or to force the LazyClient to initialize?
Anyway, that would make debugging a lot easier :-)
--Maarten
I am still curious how to get a DefaultStoreClient in stead of the
LazyStoreClient.
--Maarten
We made LazyStoreClient the default after some observations over the
years that Voldemort has been in production at LinkedIn.
However, it can be disabled. The property setting is: "enable-lazy"
(if you pass in a properties object), or .setEnableLazy on the
ClientConfig object.
Thanks,
- Alex
On Tue, Nov 29, 2011 at 10:22 AM, Maarten Koopmans
<maarten....@gmail.com> wrote:
> The question still stands, but.... if you use Scala and have a lazy
> val as StoreClient, AND the Store client is lazy, things blow up.
> Changing the lazy val to a normal val will solve that. For the
> archives.....
>
> I am still curious how to get a DefaultStoreClient in stead of the
> LazyStoreClient.
>
>
> --Maarten
>
> On Tue, Nov 29, 2011 at 11:55 AM, Maarten Koopmans
> <maarten....@gmail.com> wrote:
>> Hi,
>>
>> In the latests release I noticed I get a LazyStoreClient back - which
>> for some reason breaks a particular part of my code (don't know why
>> yet). Is there a way to force the factory to give me a DefaultClient
>> or to force the LazyClient to initialize?
>>
>> Anyway, that would make debugging a lot easier :-)
>>
>> --Maarten
>
> --
> You received this message because you are subscribed to the Google Groups "project-voldemort" group.
> To post to this group, send email to project-...@googlegroups.com.
> To unsubscribe from this group, send email to project-voldem...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/project-voldemort?hl=en.
>