Which parts of the entity can be updated?

That can be found here.

Does it make more sense to expose only EntitySpecV2 instead to users, as the other (meta) fields are set by Feast?

agreed, EntitySpecV2 should be here instead

Updated.

Do we have a strong use for this wildcard filters or can we remove it?

I guess it'll be easier to locate a set of entities that are registered with a certain pattern within a project.

Yes, but is there a need for it?

Not a strong need, have removed it.

Hmmm, what have you removed? I still see name.replace('*', '%'), project.replace('*', '%'))

If its easier to keep in then we can keep it in, but this seems like a lot of complexity to keep if we dont actually need it.

Oh, I disallowed searching for wildcard names in a specific project. So if we're removing wildcard filters, should we update the proto to only consider project and labels in the Filter then?

Doesn't seem very useful to have entity name in the filter since it'll just return that entity in a list. The user might be better off using getEntity in this case.

Do we really need to expose the V2 to users? I think we can replace the existing Entity with this new one. Any concerns with that @mrzzy ?

I think that's okay, but we'll need to update (perhaps use another name?) the previous Entity implementation used in tests and feature set. However, this would introduce breaking change to existing users who are still using the featureset-entity concept.

eg. if they do something like

fs = FeatureSet(
        "featureset",
        features=[
            Feature("feat1", ValueType.STRING)
        ],
        entities=[Entity("entity_id", ValueType.INT64)],
        max_age=Duration(seconds=100),
    )

Will be updating SDK in separate PR, along with replacing existing e2e tests.