Anil, yes its a kind of custom hash (which involves calculating hash on all
fields of row). Have to stick to the predefined mechanism based on which
source files are generated.
It would be great help if some-one guide me about any available *server-side
internal API that provides bucket level data
About api: I would not recommend using bucketId in api, as it is internal
and there are other internal/external apis that rely on bucket id
calculations; which could be compromised here.
Instead of adding new APIs, probably looking at minimizing/reducing the
time spent may be a good start.
Bucket
Thanks Den, Anil and Udo for your inputs. Extremely sorry for late rely as
I took bit of time to explore and understand geode internals.
It seems BucketRegion/Bucket terminology is not exposed to user but still i
am trying to achieve something that is uncommon and for which client API is
not expos
Thanks Kirk, that’s a really helpful description. As far as expectations go, I
agree with John. If a user:
- creates a cache
- closes the cache
- checks the isClosed flag
- and is unable to create a new cache in some cases
That sounds like a bug. Preventing the early exit sounds like a promis
Looking back at history the native library has always only ever set that
findDurable flag to false. I traced it back to its initial commit. Aside from
the annoying log message, does client durable connection work correctly?
> On Apr 14, 2020, at 10:56 PM, Jakov Varenina wrote:
>
> Hi all,
>
>
