René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Materialize via feature server for on-demand feature views crashes","articleBody":"## Expected Behavior \nI propose we expose an optional parameter to `/materialize`, to specify whether full_feature_names are passed-in. This way, for projects that really use full_feature_names, the materialize flow won't break.\n\n## Current Behavior\nWe stumbled upon a peculiar issue while working on materializing some ODFVs. It appears deep within the flow, ODFV materialization calls get_historical_features. Why it is done, not sure. In any case, for projects where feature names collide and feature_views act as namespaces, this causes the following issue:\n\n`/materialize`\n\n```\n    raise FeatureNameCollisionError(collided_feature_refs, full_feature_names)\nfeast.errors.FeatureNameCollisionError: Duplicate features named \u003cmy_feature_1\u003e\nTo resolve this collision, either use the full feature name by setting 'full_feature_names=True', or ensure that the features in question have different names.\n```\n\n## Steps to reproduce\n\nCall `/materialize` for any arbritrary ODFV.\n\n### Specifications\n\n- Version:\n- Platform:\n- Subsystem:\n\n## Possible Solution\n[PR.](https://github.com/feast-dev/feast/pull/5728)","author":{"url":"https://github.com/astronautas","@type":"Person","name":"astronautas"},"datePublished":"2025-11-18T11:24:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/5727/feast/issues/5727"}