Follow-up to #10. --columns meta.user.id (globs and nested dot-paths) now works for row-producing commands and schema, but stats and freq do their own per-column resolution and reject nested paths with a clean error (no panic — verified during the #10 merge). For consistency, both should accept a dotted path to a primitive leaf: arrs stats --columns meta.user.id ds.lance and arrs freq --column meta.user.name ds.lance. Implementation likely means routing their column validation through projection::resolve/projected_field and scanning the projected leaf as a flat column (the scan path already returns flat dotted columns).
🤖 Generated with Claude Code
Follow-up to #10.
--columns meta.user.id(globs and nested dot-paths) now works for row-producing commands andschema, butstatsandfreqdo their own per-column resolution and reject nested paths with a clean error (no panic — verified during the #10 merge). For consistency, both should accept a dotted path to a primitive leaf:arrs stats --columns meta.user.id ds.lanceandarrs freq --column meta.user.name ds.lance. Implementation likely means routing their column validation throughprojection::resolve/projected_fieldand scanning the projected leaf as a flat column (the scan path already returns flat dotted columns).🤖 Generated with Claude Code