Related information: This issue also affects em.getReference(). Please see te updated github pull request. The problem may not exist in the find code as the unit test exposes the persist of the entity with the table component of the tuple set to the super class. Pasted below for reference:
00:11:28,243 INFO hibernate.dialect.Dialect:122 - HHH000400: Using dialect: org.hibernate.ogm.dialect.NoopDialect
00:11:28,244 INFO jdbc.internal.LobCreatorBuilder:85 - HHH000422: Disabling contextual LOB creation as connection was null
00:11:28,244 INFO transaction.internal.TransactionFactoryInitiator:73 - HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
00:11:28,245 INFO internal.ast.ASTQueryTranslatorFactory:48 - HHH000397: Using ASTQueryTranslatorFactory
00:11:28,250 INFO datastore.impl.DatastoreProviderInitiator:89 - OGM000016: NoSQL Datastore provider: org.hibernate.ogm.datastore.mapbased.impl.MapBasedDatastoreProvider
00:11:28,251 INFO dialect.impl.GridDialectFactoryImpl:81 - OGM000017: Grid Dialect: org.hibernate.ogm.datastore.mapbased.impl.HashMapDialect
00:11:28,251 INFO dialect.impl.GridDialectFactoryImpl:84 - Grid dialect logs are active
00:11:28,255 TRACE ogm.datastore.access:78 - Reading Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Spartacus]} and context Tuple Context {}
00:11:28,256 TRACE ogm.datastore.access:84 - Build Tuple object with key EntityKey{table='Hero', columnNames=[name], columnValues=[Spartacus]} (does not trigger access to the datastore)
00:11:28,256 TRACE ogm.datastore.access:91 - Creating Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Spartacus]} in datastore
00:11:28,256 TRACE ogm.datastore.access:78 - Reading Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Batman]} and context Tuple Context {specialPower}
00:11:28,256 TRACE ogm.datastore.access:84 - Build Tuple object with key EntityKey{table='Hero', columnNames=[name], columnValues=[Batman]} (does not trigger access to the datastore)
00:11:28,257 TRACE ogm.datastore.access:91 - Creating Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Batman]} in datastore
00:11:28,257 TRACE ogm.datastore.access:78 - Reading Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Spartacus]} and context Tuple Context {}
00:11:28,258 TRACE ogm.datastore.access:78 - Reading Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Batman]} and context Tuple Context {}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Related information: This issue also affects em.getReference(). Please see te updated github pull request. The problem may not exist in the find code as the unit test exposes the persist of the entity with the table component of the tuple set to the super class. Pasted below for reference:
00:11:28,243 INFO hibernate.dialect.Dialect:122 - HHH000400: Using dialect: org.hibernate.ogm.dialect.NoopDialect
00:11:28,244 INFO jdbc.internal.LobCreatorBuilder:85 - HHH000422: Disabling contextual LOB creation as connection was null
00:11:28,244 INFO transaction.internal.TransactionFactoryInitiator:73 - HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
00:11:28,245 INFO internal.ast.ASTQueryTranslatorFactory:48 - HHH000397: Using ASTQueryTranslatorFactory
00:11:28,250 INFO datastore.impl.DatastoreProviderInitiator:89 - OGM000016: NoSQL Datastore provider: org.hibernate.ogm.datastore.mapbased.impl.MapBasedDatastoreProvider
00:11:28,251 INFO dialect.impl.GridDialectFactoryImpl:81 - OGM000017: Grid Dialect: org.hibernate.ogm.datastore.mapbased.impl.HashMapDialect
00:11:28,251 INFO dialect.impl.GridDialectFactoryImpl:84 - Grid dialect logs are active
00:11:28,255 TRACE ogm.datastore.access:78 - Reading Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Spartacus]} and context Tuple Context {}
00:11:28,256 TRACE ogm.datastore.access:84 - Build Tuple object with key EntityKey{table='Hero', columnNames=[name], columnValues=[Spartacus]} (does not trigger access to the datastore)
00:11:28,256 TRACE ogm.datastore.access:91 - Creating Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Spartacus]} in datastore
00:11:28,256 TRACE ogm.datastore.access:78 - Reading Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Batman]} and context Tuple Context {specialPower}
00:11:28,256 TRACE ogm.datastore.access:84 - Build Tuple object with key EntityKey{table='Hero', columnNames=[name], columnValues=[Batman]} (does not trigger access to the datastore)
00:11:28,257 TRACE ogm.datastore.access:91 - Creating Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Batman]} in datastore
00:11:28,257 TRACE ogm.datastore.access:78 - Reading Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Spartacus]} and context Tuple Context {}
00:11:28,258 TRACE ogm.datastore.access:78 - Reading Tuple with key EntityKey{table='Hero', columnNames=[name], columnValues=[Batman]} and context Tuple Context {}