Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
As part of the shadow entities mapping agreed design, we'll need this method. This method will prevent name collisions when the same FeatureView is joined more than once onto to the entity data. Here's the RFC - https://docs.google.com/document/d/1TsCwKf3nVXTAfL0f8i26jnCgHA3bRd4dKQ8QdM87vIA/edit#
Describe the solution you'd like
A clear and concise description of what you want to happen.
Add a ".with_name" method to FeatureView class that'll return a copy of the FeatureView with the passed name instead.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
We considered having a name be automatically produced in the shadow entities that has the shadow entity join_keys included in the name. The issue with this is that the name may become too long in the case of composite entities. We also considered just having a numerical counter in the name like fv_name_0_feature_name, fv_name_1_feature_name.
Additional context
Add any other context or screenshots about the feature request here.
Visitar URL original
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
As part of the shadow entities mapping agreed design, we'll need this method. This method will prevent name collisions when the same FeatureView is joined more than once onto to the entity data. Here's the RFC - https://docs.google.com/document/d/1TsCwKf3nVXTAfL0f8i26jnCgHA3bRd4dKQ8QdM87vIA/edit#
Describe the solution you'd like
A clear and concise description of what you want to happen.
Add a ".with_name" method to FeatureView class that'll return a copy of the FeatureView with the passed name instead.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
We considered having a name be automatically produced in the shadow entities that has the shadow entity join_keys included in the name. The issue with this is that the name may become too long in the case of composite entities. We also considered just having a numerical counter in the name like fv_name_0_feature_name, fv_name_1_feature_name.
Additional context
Add any other context or screenshots about the feature request here.