[
https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295635#comment-16295635
]
ASF GitHub Bot commented on IGNITE-6785:
----------------------------------------
GitHub user dolphin1414 opened a pull request:
https://github.com/apache/ignite/pull/3249
IGNITE-6785: Affinity key field ignore case.
Fix for an affinity field name upper-case issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6785
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3249.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3249
----
commit acf0e7dada672e6cd0027d46977279a7c0ab9f91
Author: rkondakov <[email protected]>
Date: 2017-12-18T20:29:32Z
IGNITE-6785: Changed affinity key fields names comparison from the equals()
to equalsIgnoreCase().
----
> Affinity field name forced to be upper-case
> -------------------------------------------
>
> Key: IGNITE-6785
> URL: https://issues.apache.org/jira/browse/IGNITE-6785
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.1
> Reporter: Denis Magda
> Assignee: Roman Kondakov
> Labels: important, usability
> Fix For: 2.4
>
> Attachments: sql_bug.zip
>
>
> If an SQL schema and cache is created with CREATE TABLE command and a user
> wants to use key-value APIs creating its own custom key class, then (at
> least) the key class's affinity field forced to be written in upper-case.
> Steps to reproduce using the project attached:
> * start a node with {{./ignite.sh ../examples/config/example-ignite.xml}}.
> * create {{City}} table using {{ignite_world.sql}}. SQLline is one of the
> quickest ways: https://apacheignite-sql.readme.io/docs/sqlline
> * Run {{KeyValueDataProcessing}} to catch the exception below
> {noformat}
> Exception in thread "main" class
> org.apache.ignite.binary.BinaryObjectException: Binary type has different
> affinity key fields [typeName=demo.model.CityKey,
> affKeyFieldName1=COUNTRYCODE, affKeyFieldName2=countryCode]
> at
> org.apache.ignite.internal.binary.BinaryUtils.mergeMetadata(BinaryUtils.java:987)
> {noformat}
> If fact {{CityKey}} names the affinity field in the same way as in CREATE
> TABLE - {{countryCode}}.
> Next, run {{KeyValueBinaryDataProcessing}} to spot another weird thing:
> * BinaryObject key accepts `countryCode` as the affinity field name.
> * If to print our a binary object value then all the fields are in the
> upper-case (they were not defined this way in CREATE TABLE):
> {noformat}
> demo.model.City [idHash=1613627715, hash=-1386587499, DISTRICT=Noord-Holland,
> POPULATION=711200, NAME=Amsterdam]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
