Hi Kishore, Thanks for the response. I looked at that, but was n't sure if I should be using it :P .
>>We really need a usage doc for property store api. +100 This is very common pattern, need for partition level metadata. Thanks Vinoth On Tue, Mar 10, 2015 at 2:57 PM, kishore g <[email protected]> wrote: > Databus consumer group maintains the offsets in property store. > > It provides a key value interface. > > > http://helix.apache.org/javadocs/0.6.4/reference/org/apache/helix/store/package-summary.html > > See HelixPropertyStore api, > http://helix.apache.org/javadocs/0.6.4/reference/org/apache/helix/store/HelixPropertyStore.html > > The base class for this is > http://helix.apache.org/javadocs/0.6.4/reference/org/apache/helix/BaseDataAccessor.html > > Entire Helix library uses this api underneath and property store is a > place where application can store additional information, subscribe to the > changes (recursively). When you subscribe(optional) to changes all values > are cached locally and updated on change. > > > We really need a usage doc for property store api. > > > thanks, > Kishore G > > > > > > On Tue, Mar 10, 2015 at 1:45 PM, Vinoth Chandar <[email protected]> wrote: > >> Hi, >> >> I am writing something very similar to the RabbitMQ Consumer group >> recipe. I would like to be able to remember a number/offset for each >> partition in the resource. Is there any built in support in Helix for doing >> this? >> >> PS: I am working off 0.6.4 release. Let me know if I should/can upgrade. >> >> Thanks >> Vinoth >> > >
