apache/superset · error · ValueError
created_by_fk_or_editor only supports 'eq'; got '{c.opr}'
Error message
created_by_fk_or_editor only supports 'eq'; got '{c.opr}' What it means
ValueError raised in ChartDAO's filter extension (superset/daos/chart.py): the synthetic filter column 'created_by_fk_or_editor' (charts created by a user OR edited by that user's subject) is implemented only as an equality membership test, so any operator other than 'eq' is rejected.
Source
Thrown at superset/daos/chart.py:83
operator_enum = ColumnOperatorEnum(c.opr)
subq = (
select(chart_editors.c.chart_id)
.join(
Subject.__table__,
Subject.__table__.c.id == chart_editors.c.subject_id,
)
.where(
Subject.__table__.c.type == 1,
operator_enum.apply(Subject.__table__.c.user_id, c.value),
)
)
query = query.filter(
Slice.id.in_(subq) # type: ignore[attr-defined,unused-ignore]
)
elif c.col == "created_by_fk_or_editor":
if c.opr != "eq":
raise ValueError(
f"created_by_fk_or_editor only supports 'eq'; got '{c.opr}'"
)
from superset.subjects.models import chart_editors, Subject
editor_subq = (
select(chart_editors.c.chart_id)
.join(
Subject.__table__,
Subject.__table__.c.id == chart_editors.c.subject_id,
)
.where(
Subject.__table__.c.type == 1,
Subject.__table__.c.user_id == c.value,
)
)
query = query.filter(
or_(
Slice.created_by_fk == c.value, # type: ignore[attr-defined,unused-ignore]View on GitHub (pinned to f4587218dd)
Solutions
- Use "opr": "eq" with a scalar user id for created_by_fk_or_editor.
- For 'not created by', invert client-side: fetch with eq and exclude, or use a different filter column.
- Treat created_by_fk_or_editor as a virtual field: check CHART_CUSTOM_FIELDS / the resource's filters endpoint for its advertised operators.
Example fix
# before
filters=[{"col": "created_by_fk_or_editor", "opr": "in", "value": [1]}]
# after
filters=[{"col": "created_by_fk_or_editor", "opr": "eq", "value": 1}] Defensive patterns
Strategy: validation
Validate before calling
def chart_filters_valid(filters) -> bool:
return all(
not (f.get("col") == "created_by_fk_or_editor" and f.get("opr") != "eq")
for f in filters or []
) Type guard
def is_eq_filter(f: dict) -> bool:
return f.get("opr") == "eq" Try / catch
try:
ChartDAO.find(query=", filters=filters)
except ValueError as ex:
if "created_by_fk_or_editor" in str(ex):
filters = [f for f in filters if f["col"] != "created_by_fk_or_editor"] or \
[{**f, "opr": "eq"} for f in filters if f["col"] == "created_by_fk_or_editor"]
results = ChartDAO.find(query=", filters=filters) Prevention
- Treat created_by_fk_or_editor as eq-only virtual field in shared client code.
- Use created_by_fk when you need operators other than eq.
- Cache the resource's /filters metadata and validate before every request.
When it happens
Trigger: Calling the chart REST API (/api/v1/chart/) or ChartDAO.find with filters=[{"col": "created_by_fk_or_editor", "opr": "ne"|"in"|"like"|..., ...}].
Common situations: Clients that enumerate filter columns and assume every column supports every operator; porting a dashboard's filter payload to charts without adjusting the operator.
Related errors
- Invalid filter: column '%s' does not exist on %s
- Operator '{operator_enum.value}' on relationship column '{co
- created_by_fk_or_editor only supports 'eq'; got '{c.opr}'
- created_by_fk_or_editor only supports 'eq'; got '{c.opr}'
- This version does not record a visualization type and datase
AI-assisted analysis of apache/superset@f4587218dd (2026-08-14).
Data as JSON: /api/errors/4f3f194e5288d0a1.
Report an issue: GitHub.