ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6785) Affinity field name forced to be upper-case
Date Wed, 01 Nov 2017 08:36:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233775#comment-16233775

Vladimir Ozerov commented on IGNITE-6785:

[~dmagda], the script is wrong in several places:
1) Single quote is illegal way to force case-sensitivitiy. H2 engine simple ignores it. Use
double quote instead.
2) Make sure that field name cases matches everywhere. E.g. in some places "ID" is used, in
others - "id". FIeld name is "countryCode", but affinityKey is "CountryCode". Etc.

When I fixed these errors everything worked fine for me. The only problem I found is how we
manage cases for "affinityKey" property, but it should not affect your case provided that
case-sensitivity is fixed.

> Affinity field name forced to be upper-case
> -------------------------------------------
>                 Key: IGNITE-6785
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6785
>             Project: Ignite
>          Issue Type: Task
>      Security Level: Public(Viewable by anyone) 
>          Components: sql
>    Affects Versions: 2.1
>            Reporter: Denis Magda
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>              Labels: 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:
> * 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,
> 	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,
> {noformat}

This message was sent by Atlassian JIRA

View raw message