Hi, Well one (weak) reason is that somebody else could already have put data to a cache using the "dash" convention, and in that case we are unable to retrieve this data (eg. how can we (automatically) deserialize the "user-name" field?)
also, allowing this mapping would be in line with hibernate/jpa (java.persistence.Column annotation); where you can have whatever naming convention for database tables, and can then freely map to client pojos (DB data comes first, client pojo-s come later). anyway; what you say makes perfectly sense so, thanks for clarifying this! (and we'll go with the single name convention). -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
