@Christian Beikov , thanks a lot. Now that, Hibernate has provided the solution for it already. It might not be considerd as a bug. And that, the content of the report has been understood correctly . Therefore, I will not attach a test case. This operation seems to be not necessary.

However, I think that

 @DiscriminatorOptions.force = true 

should be considerd as the default behaviour. Because the restriction of @DiscriminatorColumn should not be optional, it is not correspond with the proper expectations.

Is there any additional consideration?
Any idea about this?