hibernate/hibernate-orm · error · IllegalStateException

Could not find table group for: %s

Error message

Could not find table group for: %s

What it means

PluralTableGroup only carries table groups for the ELEMENT and INDEX parts of a collection mapping. Its getTableGroup(CollectionPart.Nature) switch handles those two constants; every other Nature value falls through to an IllegalStateException. In Hibernate's enum that other value is ID (the idbag collection-id part), so the plural table group structurally has nothing to return for it.

Source

Thrown at hibernate-core/src/main/java/org/hibernate/sql/ast/tree/from/PluralTableGroup.java:29

 * @author Christian Beikov
 */
public interface PluralTableGroup extends TableGroup {

	PluralAttributeMapping getModelPart();

	TableGroup getElementTableGroup();

	TableGroup getIndexTableGroup();

	default TableGroup getTableGroup(CollectionPart.Nature nature) {
		switch ( nature ) {
			case ELEMENT:
				return getElementTableGroup();
			case INDEX:
				return getIndexTableGroup();
		}

		throw new IllegalStateException( "Could not find table group for: " + nature );
	}
}

View on GitHub (pinned to fad1729dce)

Solutions

1. Do not resolve Nature.ID through PluralTableGroup.getTableGroup - resolve the collection-id part via the PluralAttributeMapping instead
2. Switch on nature at the call site and handle/skip ID before calling getTableGroup
3. If you control the caller, use getElementTableGroup()/getIndexTableGroup() directly
4. Verify any idbag NavigablePath handling: the {collection-id} path must not be resolved against a plain plural table group

Example fix

// before
TableGroup group = pluralTableGroup.getTableGroup( nature ); // throws for Nature.ID

// after
TableGroup group = switch ( nature ) {
    case ELEMENT -> pluralTableGroup.getElementTableGroup();
    case INDEX -> pluralTableGroup.getIndexTableGroup();
    case ID -> null; // resolve collection-id via PluralAttributeMapping, not the table group
};

TableGroup resolveTableGroup(PluralTableGroup group, CollectionPart.Nature nature) {
    return switch ( nature ) {
        case ELEMENT -> group.getElementTableGroup();
        case INDEX -> group.getIndexTableGroup();
        default -> null;
    };
}

boolean isResolvableNature(CollectionPart.Nature nature) {
    return nature == CollectionPart.Nature.ELEMENT || nature == CollectionPart.Nature.INDEX;
}

try { ... } catch ( IllegalStateException e ) { if ( e.getMessage() != null && e.getMessage().startsWith( "Could not find table group for" ) ) { /* resolve via PluralAttributeMapping instead */ } else throw e; }

When it happens

Trigger: Calling pluralTableGroup.getTableGroup(CollectionPart.Nature.ID), e.g. while resolving a NavigablePath that addresses the '{collection-id}' part of an idbag mapping; generic code that iterates CollectionPart.Nature.values() and resolves each nature against a PluralTableGroup; custom SQM path resolution or result builders that look up collection parts by nature.

Common situations: Custom dialect functions, SQM extensions, or tooling that walks collection parts generically; idbag mappings whose collection-id path gets resolved against a standard plural table group; Hibernate upgrades where the Nature enum gains a constant the switch does not handle.

Related errors

• removeTableGroupJoin not supported by %s
• Mutating table reference should be handled by the statement
• Property not among declared properties: " + property.getName
• Could not resolve ServiceRegistry
• Same column is added more than once with different values fo

AI-assisted analysis of hibernate/hibernate-orm@fad1729dce (2026-08-22). Data as JSON: /api/errors/3966c721cf88d14f. Report an issue: GitHub.