René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"dbt integration: FileSource generates invalid hardcoded paths","articleBody":"## Context\nPR #5827 added support for FileSource data sources in dbt integration.\n\n## Problem\nThe FileSource implementation generates hardcoded paths that likely don't exist:\n\n```python\n# In mapper.py:240-242\nreturn FileSource(\n    name=f\"{model.name}_source\",\n    path=f\"/data/{model.name}.parquet\",  # Hardcoded, likely invalid\n    # ...\n)\n```\n\nThis path `/data/{model.name}.parquet` is unlikely to match actual file locations.\n\n## Impact\n- Generated FileSource objects won't work without manual editing\n- Confusing user experience\n- No clear documentation on how to fix the paths\n\n## Proposed Solutions\n\n### Option 1: Make path configurable\n```bash\nfeast dbt import -m manifest.json -e driver_id --data-source-type file --file-path-template \"/my/data/{model}.parquet\"\n```\n\n### Option 2: Read from dbt meta\nSupport custom path in dbt model meta:\n```yaml\n# dbt model\nmodels:\n  - name: driver_stats\n    meta:\n      feast:\n        file_path: \"/data/warehouse/driver_stats.parquet\"\n```\n\n### Option 3: Require explicit path mapping file\n```bash\nfeast dbt import -m manifest.json -e driver_id --file-path-config paths.yaml\n```\n\n## Recommendation\nImplement Option 1 (path template) as it's simplest and covers most use cases. Consider Option 2 for advanced scenarios.\n\n## Related\n- PR #5827","author":{"url":"https://github.com/YassinNouh21","@type":"Person","name":"YassinNouh21"},"datePublished":"2026-01-16T20:12:19.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/5874/feast/issues/5874"}