hibernate/hibernate-orm · error · UnsupportedOperationException
Ordering for {referenceModelPart} not supported
Error message
Ordering for {referenceModelPart} not supported What it means
Error "Ordering for {referenceModelPart} not supported" thrown in hibernate/hibernate-orm.
Source
Thrown at hibernate-core/src/main/java/org/hibernate/metamodel/mapping/internal/AbstractDomainPath.java:105
if ( embeddableValuedModelPart.getFetchableName()
.equals( modelPartName ) || ELEMENT_TOKEN.equals( modelPartName ) ) {
final int size = embeddableValuedModelPart.getNumberOfFetchables();
final List<Expression> expressions = new ArrayList<>( size );
for ( int i = 0; i < size; i++ ) {
final var fetchable = embeddableValuedModelPart.getFetchable( i );
expressions.add( resolve( fetchable, ast, tableGroup, modelPartName, creationState ) );
}
return new SqlTuple( expressions, embeddableValuedModelPart );
}
else {
final var subPart = embeddableValuedModelPart.findSubPart( modelPartName, null );
assert subPart.asBasicValuedModelPart() != null;
return resolve( subPart, ast, tableGroup, modelPartName, creationState );
}
}
else {
// sure it can happen
throw new UnsupportedOperationException( "Ordering for " + referenceModelPart + " not supported" );
}
}
@Override
public void apply(
QuerySpec ast,
TableGroup tableGroup,
String collation,
String modelPartName,
SortDirection sortOrder,
Nulls nullPrecedence,
SqlAstCreationState creationState) {
apply(
getReferenceModelPart(),
ast,
tableGroup,
collation,
modelPartName,View on GitHub (pinned to fad1729dce)
Solutions
- Only apply ordering to orderable model parts (basic attributes); remove ORDER BY on the unsupported part or order by a basic attribute instead.
When it happens
Trigger: Thrown when an order-by fragment references a model part for which ordering is not supported.
Common situations: See trigger scenarios.
AI-assisted analysis of hibernate/hibernate-orm@fad1729dce (2026-08-22).
Data as JSON: /api/errors/95f4bb236dbda149.
Report an issue: GitHub.