Additional field problems occurred in ignite2.6

classic Classic list List threaded Threaded
2 messages Options
hulitao198758 hulitao198758
Reply | Threaded
Open this post in threaded view
|

Additional field problems occurred in ignite2.6

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
inconsistent, will Ignite the memory mapping out the two fields, in the end
will be one more with JAVA entity class variables the same fields, why?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
dkarachentsev dkarachentsev
Reply | Threaded
Open this post in threaded view
|

Re: Additional field problems occurred in ignite2.6

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 BinaryBasicIdMapper to be case-sensitive. Just set it
to BinaryConfiguration:
config.setBinaryConfiguration(new BinaryConfiguration().setIdMapper(new
BinaryBasicIdMapper(false))).

Thanks!
-Dmitry



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/