René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"dbt integration: Make TTL default configurable and increase default value","articleBody":"## Context\nPR #5827 added dbt integration with TTL (time-to-live) for feature views.\n\n## Problem\nThe default TTL is hardcoded to 1 day, which is very aggressive and may not be suitable for most production use cases. Many feature pipelines run weekly or have longer retention requirements.\n\n## Current Behavior\n```python\n# In dbt_import.py:64-68\n@click.option(\n    \"--ttl-days\",\n    type=int,\n    default=1,  # Very short!\n    show_default=True,\n    help=\"TTL (time-to-live) in days for feature views\",\n)\n```\n\n## Proposed Changes\n\n1. **Increase default to 7 days** - More reasonable for production use cases\n2. **Make default configurable** - Allow users to set default in config file\n3. **Add validation** - Warn if TTL is unusually short (\u003c 1 day) or long (\u003e 365 days)\n\n## Example\n```python\ndefault=7,  # More reasonable default\n```\n\nOr support config override:\n```yaml\n# feature_store.yaml\ndbt:\n  default_ttl_days: 30\n```\n\n## Migration Note\nThis is a breaking change for users who relied on the 1-day default. Consider:\n- Documenting the change in release notes\n- Providing migration guide\n- Adding deprecation warning in interim release\n\n## Related\n- PR #5827","author":{"url":"https://github.com/YassinNouh21","@type":"Person","name":"YassinNouh21"},"datePublished":"2026-01-16T20:12:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/5873/feast/issues/5873"}