I have been discussing this last week with Sanne and Hardy.
There are three cases

1. Inheritance.SINGLE_TABLE

This is the only supported strategy really AFAIR. But it seems that for some reason, I have disabled discriminator support.
Adding a discriminator column would I think solve your problem entirely without the need to find different table name.
A discriminator might not be super elegant though and something akeen to the discriminator formula would be nice. Unfortunately that "formula" would be specific to each NoSQL. The good thing though is that the discriminator value could be inferred from the presence of some properties and avoid the pollution of the data model.

1. Inheritance JOINED

I don't think this model makes much sense in a NoSQL solution. At least not for Document and Map based

1. Inheritance TABLE_PER_CLASS

This approach might be useful, I'm undecided. Today we don't have an entity persister implementing it though and that would need to be done probably by subclassing OgmEntityPersister.
I think the hack you have done is close to doing just that.

1. Conclusion

I'd start with supporting the single table and discriminator approach. I'm pretty sure I disabled discriminator support when I ported OGM from ORM in the OgmEntityPersister and that needs to be rewired.
Then we can explore the table per class approach as an alternative

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