This is not a bug, but a feature request. We simply don't support all types which are not covered by JDBC. I created HHH-15504 Open for adding the type mapping. In the meantime, you can create a custom UserType that binds values in the correct byte order.