Hello,

Which version are you on?
Also, please share your configuration. Does the same
behaviour persists if you do it using Java API?

> Also I would like to know if there is any way in c++ to obtain the key
> object  using QueryFieldsCursor

You should use SQL query like "select _key, ... from YourType" and then
just retrieve key as any other column.

Best Regards,
Igor

On Tue, Aug 1, 2017 at 5:55 PM, kotamrajuyashasvi <
kotamrajuyasha...@gmail.com> wrote:

> I am running c++ ignite client, with cassandra as persistent store. The
> cache
> has custom object as key. The key class is mapped in c++ and Java Pojo
> using
> BinaryType object. I also implemented hashcode and equals in java pojo.
> When
> I use cache.Get(key object) in c++ client I am able to retrieve the row .
> The issue is that after I loadCache in c++ and all entries are loaded(
> which
> I could tell from cache size and also when I query I'm able to retrieve all
> rows), If I call cache.ContainsKey(key object), its returning false. But If
> i call cache.Get(key object) and then call  cache.ContainsKey then its
> returning true.
>
> Also after cache.Get(key object) in c++ client, cache size is increasing by
> one even though all entries are fully loaded.But once I call cache.Get
> after
> that how many times I call the cache.Get(key object) again and again even
> with same key fields(key class variables representing the primary key) but
> new key objects.. the size is remaining same its not increasing. So overall
> the problem is that after loadCache in c++, even though a valid key object
> is given its not able to find it in cache and loading again. But after that
> it is able to identify that the key is loaded.
>
> Also I would like to know if there is any way in c++ to obtain the key
> object  using QueryFieldsCursor
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/c-ignite-cache-ContainsKey-key-object-
> method-returns-false-even-when-key-is-present-tp15862.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Reply via email to