[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-6785: - Fix Version/s: (was: 2.14) > 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, 2.8 >Reporter: Denis A. Magda >Assignee: Maxim Muzafarov >Priority: Major > Labels: newbie, usability > Attachments: SqlAffinityKeyTest.java, sql_bug.zip > > Time Spent: 20m > Remaining Estimate: 0h > > 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 (v8.20.10#820010)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-6785: Fix Version/s: 2.14 (was: 2.10) > 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, 2.8 >Reporter: Denis A. Magda >Priority: Major > Labels: newbie, usability > Fix For: 2.14 > > Attachments: SqlAffinityKeyTest.java, sql_bug.zip > > Time Spent: 20m > Remaining Estimate: 0h > > 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 (v8.20.7#820007)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-6785: -- Fix Version/s: (was: 2.9) 2.10 > 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, 2.8 >Reporter: Denis A. Magda >Priority: Major > Labels: newbie, usability > Fix For: 2.10 > > Attachments: SqlAffinityKeyTest.java, sql_bug.zip > > Time Spent: 20m > Remaining Estimate: 0h > > 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 (v8.3.4#803005)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-6785: --- Attachment: SqlAffinityKeyTest.java > 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, 2.8 >Reporter: Denis A. Magda >Priority: Major > Labels: newbie, usability > Fix For: 2.9 > > Attachments: SqlAffinityKeyTest.java, sql_bug.zip > > Time Spent: 20m > Remaining Estimate: 0h > > 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 (v8.3.4#803005)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-6785: --- Labels: newbie usability (was: important newbie usability) > 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, 2.8 >Reporter: Denis A. Magda >Priority: Major > Labels: newbie, usability > Fix For: 2.9 > > Attachments: sql_bug.zip > > Time Spent: 20m > Remaining Estimate: 0h > > 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 (v8.3.4#803005)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-6785: --- Fix Version/s: 2.9 > 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, 2.8 >Reporter: Denis A. Magda >Priority: Major > Labels: important, newbie, usability > Fix For: 2.9 > > Attachments: sql_bug.zip > > Time Spent: 20m > Remaining Estimate: 0h > > 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 (v8.3.4#803005)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-6785: --- Labels: important newbie usability (was: important usability) > 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, 2.8 >Reporter: Denis A. Magda >Priority: Major > Labels: important, newbie, usability > Attachments: sql_bug.zip > > Time Spent: 20m > Remaining Estimate: 0h > > 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 (v8.3.4#803005)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-6785: --- Affects Version/s: 2.8 > 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, 2.8 >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Major > Labels: important, usability > Attachments: sql_bug.zip > > Time Spent: 20m > Remaining Estimate: 0h > > 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 (v8.3.4#803005)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6785: Fix Version/s: (was: 2.4) > 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: Denis Magda > Labels: important, usability > 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6785: Attachment: (was: sql_bug.zip) > 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: Denis Magda > 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6785: Attachment: sql_bug.zip > 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: Denis Magda > 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6785: Labels: important usability (was: usability) > 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: Vladimir Ozerov > 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6785: Issue Type: Bug (was: Task) > 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 > Security Level: Public(Viewable by anyone) > Components: sql >Affects Versions: 2.1 >Reporter: Denis Magda >Assignee: Vladimir Ozerov > 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: 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6785: Priority: Major (was: Critical) > 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 > 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: 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6785: Attachment: sql_bug.zip > 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: 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6785: Attachment: (was: sql_bug.zip) > 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: 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6785: Attachment: sql_bug.zip > 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 > 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: 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6785: Priority: Critical (was: Major) > 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: 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)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[ https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6785: Labels: usability (was: ) > 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 > Labels: usability > Fix For: 2.4 > > > 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)