Discriminator column not supported with JOINED strategy

I did eventually add this support : https://hibernate.atlassian.net/browse/HHH-6911#icft=HHH-6911

But really its more intended for compatibility with inferior providers that need the discriminator with joined inheritance...

Using discriminator column with "joined" strategy used to work when we were using .hbm.xml files to describe ORM. Moreover it's clearly documentated:
http://docs.jboss.org/hibernate/stable/core/reference/fr/html/inheritance.html#inheritance-tablepersubclass-discriminator

SInce we moved to annotations instead of XML files, we can't do that anymore except using secondary tables but it's painful.

4 years passed since this issue was opened.
Any changes?

"Status: Resolved Resolved
Resolution: Rejected "

Rejected? Why? This is very important functionality. Can anyone tell why this issue was skipped, please.

I've the same problem with strategy=JOINED and Discriminator Values.
It's very important to me to have not null value of discriminator field, I use it in group queries.

Now I have to do in base classes something like:

public MyBase () {
// set the value of discriminator's field
kind = this.getClass().getSimpleName();
}

I think it is really ugly

It would be nice to see how the problem with the multiple joins is faced when the underlying DB has restriction on the number of joins one can execute in a single SQL? For instance MySQL seems to allow only 31 joins. What happens if the class hierarchy has more than 31 sub-classes?