[
https://issues.apache.org/jira/browse/IGNITE-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497061#comment-15497061
]
Igor Rudyak commented on IGNITE-3799:
-------------------------------------
Instead of throwing exceptions it's better to have POJO fields aliases concept
- two or more POJO fields could be mapped to the same Cassandra column if they
have the same type.
It's rather important case when working with POJO objects in Ignite through
JDBC. Key object and value object in Ignite cache could share the same fields
in this case. For example we can use "long" as a key and custom "Person" class
as a value, which at the same time already has "id" field storing the same
"long" value (person id).
> More descriptive exception for Cassandra column names duplicates
> -----------------------------------------------------------------
>
> Key: IGNITE-3799
> URL: https://issues.apache.org/jira/browse/IGNITE-3799
> Project: Ignite
> Issue Type: Bug
> Reporter: Igor Rudyak
> Assignee: Igor Rudyak
>
> If POJO persistence strategy is used and cache key is mapped to the same
> column as one of the POJO fields, it's better to re-throw more descriptive
> exception instead of
> *com.datastax.driver.core.exceptions.InvalidQueryException: The column names
> contains duplicates*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
