[IGNITE-21797] Column's type mismatch during marshalling of pojo (embedded API)

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 3.0.0-beta2
• Labels: ignite-3
• Assignee: Maksim Zhuravkov
• Reporter: Konstantin Orlov
• Created: 19/Mar/24 10:00
• Updated: 27/Mar/24 12:35
• Resolved: 27/Mar/24 12:35

Description

Take a look at the scenario below:

    static class Key {
        int int_col;
        String str_col;
    }

    static class Val {
        boolean bool_col;
        LocalDate date_col;
    }

    sql("CREATE TABLE test (int_col INT, bool_col BOOLEAN, date_col DATE, str_col VARCHAR, PRIMARY KEY (int_col, str_col))");

    KeyValueView<Key, Val> kvView = CLUSTER.aliveNode().tables()
            .table("test")
            .keyValueView(Key.class, Val.class);

    var key = new Key();
    key.int_col = 1;
    key.str_col = "1";

    var val = new Val();
    val.bool_col = true;
    val.date_col = LocalDate.now();

    kvView.put(null, key, val);

Mind the order of primary key fields: the first and the last columns in table declaration. In that case, InvalidTypeException is thrown, because after IGNITE-19744 key columns are not grouped in the very beginning of the row anymore, but marshaller of embedded client still appends key columns first (see org.apache.ignite.internal.schema.marshaller.reflection.KvMarshallerImpl#marshal(K, V)).

Issue Links

• blocks: IGNITE-21768 Wrong key column serialization in ClientKeyValueView
• is caused by: IGNITE-19744 Clean up IEP-54 leftovers
• links to: GitHub Pull Request #3466