Registry get_feature_view should read stream and on-demand feature views about feast HOT 10 OPEN

Probably. I'm thinking of marking it as deprecated right from the get go and we can eventually make a breaking change.

from feast.

I can probably take this one if you're not in a rush for this.

from feast.

Sure, there are already workarounds for it, so we should get by in the meantime. I'll assign you, let us know if you won't be able to find time for it.

from feast.

cc @dmartinol

from feast.

can we keep backward compatibility by adding an optional includes_subclasses that default to False?

from feast.

Going to take care of this over the next couple of days.

Two steps:

1. Create FeatureViewType in the BaseFeatureView
2. Add it to the 3 as metadata and use that to return the list of feature views broken down by type

I'm working on (1) right now and will update when done (it should be quick).

from feast.

Didn't really get the need for the first one, can't you just check the type of an object?

from feast.

Yeah, definitely could but I'd rather have more explicit metadata surrounding it.

That said, I really don't see any other data types outside of On Demand, Batch, and Stream.

from feast.

after looking into this, it's a pretty big change actually. I think it's worth doing but just want to state it explicitly.

from feast.

So first unblock is list_feature_views which is a clunky wrapper but at least gives some small support. I'll change the return object next but I thought I'd at least return the quick one.

#4256

from feast.