JsonModel: find not working with enum int not string

[gam-phon]

Hello,

enum with str works but enum with int does not work

[EinderJam]

It looks like performing find() on a model which has an Enum as attribute returns an empty array if the Enum values type is anything other than str: int, as @gam-phon said, but also tuple exhibit this behaviour

[abrookins]

Confirmed bug: This is a valid issue with Enum handling in queries.

Root cause: When building RediSearch queries, the code uses f-strings like f"@{field_name}:[{value} {value}]" where value could be an Enum. For IntEnum this works because it's a subclass of int, but for regular Enum with int values, it produces MyEnum.A instead of 1.

Fix needed: In FindQuery.resolve_value(), we need to extract .value from Enum objects:

# At the start of resolve_value:
if isinstance(value, Enum):
    value = value.value

Workaround: Use IntEnum instead of Enum for integer enum fields, or use StrEnum for string enum fields:

from enum import IntEnum

class Status(IntEnum):  # Instead of Enum
    ACTIVE = 1
    INACTIVE = 2

[abrookins]

Fixed in commit 6428db8 on the feature/redisvl-integration branch (PR #791).

The fix: Added Enum value extraction in resolve_value() for NUMERIC fields. When querying with a regular Enum (not IntEnum) that has int values, we now extract .value from the Enum before using it in the query.

Before this fix, querying with Model.field == Status.ACTIVE where Status.ACTIVE = 2 would produce incorrect query syntax like @status:[Status.ACTIVE Status.ACTIVE] instead of @status:[2 2].