This is going to require some internal discussion on the best way to handle addressing this and therefore I am going to unschedule this for 5.4 for the time being. We may be able to get something in place for this for 5.4.x but in the meantime specifying the values on the @Table annotation explicitly solves the problem.