Re: Additional field problems occurred in ignite2.6

2018-08-03 Thread dkarachentsev
Hi, Rules of field naming defined in BinaryIdMapper interface. By default used BinaryBasicIdMapper implementation that is by default converts all field names to lower case. So Ignite doesn't support the same field names in different cases as it will treat them as same field. But you can configure

Additional field problems occurred in ignite2.6

2018-08-02 Thread hulitao198758
Ignite2.6 configured POJO field mapping, in the case of Ignite2.3 field is uppercase or lowercase, only will be mapped to Ignite the memory among the field names, but in the ignite2.6 if the field names in the JAVA entity class and Ignite the Config fields in the configuration file name case is inc