chroma-core/chroma · error · PydanticCustomError

invalid_field

invalid_field

Error message

'{invalid_fields[0]}' is not a valid field for {class_name}. 

What it means

Error "'{invalid_fields[0]}' is not a valid field for {class_name}. " thrown in chroma-core/chroma.

Source

Thrown at chromadb/api/types.py:1605

def _create_extra_fields_validator(valid_fields: list[str]) -> Any:
    """Create a model validator that provides helpful error messages for invalid fields."""

    @model_validator(mode="before")
    def validate_extra_fields(cls: Type[BaseModel], data: Any) -> Any:
        if isinstance(data, dict):
            invalid_fields = [k for k in data.keys() if k not in valid_fields]
            if invalid_fields:
                invalid_fields_str = ", ".join(f"'{f}'" for f in invalid_fields)
                class_name = cls.__name__
                # Create a clear, actionable error message
                if len(invalid_fields) == 1:
                    msg = (
                        f"'{invalid_fields[0]}' is not a valid field for {class_name}. "
                    )
                else:
                    msg = f"Invalid fields for {class_name}: {invalid_fields_str}. "

                raise PydanticCustomError(
                    "invalid_field",
                    msg,
                    {"invalid_fields": invalid_fields},
                )
        return data

    return validate_extra_fields


class FtsIndexConfig(BaseModel):
    """Configuration for Full-Text Search index. No parameters required."""

    _validate_extra_fields = _create_extra_fields_validator(
        [
            "algorithm",
        ]
    )

View on GitHub (pinned to aecdd12c8a)

When it happens

Trigger: Thrown at chromadb/api/types.py:1605 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of chroma-core/chroma@aecdd12c8a (2026-08-16). Data as JSON: /api/errors/f9bb58d92ff6d769. Report an issue: GitHub.