Valentin,
You right, it's rather easy to handle such kind of exception and re-throw
more descriptive one. Here is a new ticket for this:
https://issues.apache.org/jira/browse/IGNITE-3799
Igor
On Mon, Aug 29, 2016 at 8:29 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Igor,
>
Igor,
Thanks! How do you think, is there a way to validate this on the earlier
stages and throw more descriptive exception? Currently this looks like a
usability issue.
-Val
On Mon, Aug 29, 2016 at 8:05 PM, Igor Rudyak wrote:
> Hi Valentin,
>
> You are right - the reason is in "id" field. Acco
Hi Valentin,
You are right - the reason is in "id" field. According to the persistence
descriptor, cache key will be stored in "id" field, but at the same time
User POJO class also has such field. There are several options to fix this:
1) Specify another column mapping for Ignite cache key. For e
Hi Igor,
Will you have a chance to take another look at user's issue [1]? As far as
I understand, this happens because the key column name is "id" and there is
"id" field in the value class. Is this a valid configuration?
[1]
http://apache-ignite-users.70518.x6.nabble.com/Ignite-with-Cassandra-td
