You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The failure occurs because the avro adapter in the flow-record library (.venv/lib/python3.12/site-packages/flow/record/adapter/avro.py) lacks a mapping for the path field type to an Avro primitive type. When rdump tries to serialize the output of the users query, it encounters the home field, which is explicitly typed as a path, and throws an error.
Unlike SQLite and DuckDB adapters that default unknown types to TEXT, the Avro adapter performs a strict lookup. We can fix this by adding "path": "string" (and its system-specific variants) to the AVRO_TYPE_MAP dictionary directly within the virtual environment's package.
Key Changes
.venv/lib/python3.12/site-packages/flow/record/adapter/avro.py: Update the AVRO_TYPE_MAP dictionary to map path, posix_path, and windows_path to Avro's "string" type.
Not sure this would work though, appears that it would happen with any unknown field type encountered?
Activity
jeffbryner commentedon May 13, 2026
FWIW: Analysis by cline,
Overview
The failure occurs because the
avroadapter in theflow-recordlibrary (.venv/lib/python3.12/site-packages/flow/record/adapter/avro.py) lacks a mapping for thepathfield type to an Avro primitive type. Whenrdumptries to serialize the output of theusersquery, it encounters thehomefield, which is explicitly typed as apath, and throws an error.Unlike SQLite and DuckDB adapters that default unknown types to
TEXT, the Avro adapter performs a strict lookup. We can fix this by adding"path": "string"(and its system-specific variants) to theAVRO_TYPE_MAPdictionary directly within the virtual environment's package.Key Changes
.venv/lib/python3.12/site-packages/flow/record/adapter/avro.py: Update theAVRO_TYPE_MAPdictionary to mappath,posix_path, andwindows_pathto Avro's"string"type.Not sure this would work though, appears that it would happen with any unknown field type encountered?
yunzheng commentedon May 17, 2026
This is indeed due to a missed mapping in the AVRO adapter. Is this something you want to try and fix yourself? I'll be happy to review it.