[FR] Expand feature search functionality in UI

[aabbasi-hbo]

Willingness to contribute

No. I cannot contribute a bug fix at this time.

Feature Request Proposal

Currently the search functionality in the UI does search by matching keyword to feature name. Would like to expand this functionality by enabling users to filter and search for features based on entity_key, metadata tags (keys and values), and feature type (whether anchor_feature or derived_feature).

Proposal 1:
Have additional field which allows user to specify which column/field (ex. entity_key) they want to match their keyword against. Inputted keyword will only be matched against the specified field.

Proposal 2:
Automatically search keyword against all fields.

Motivation

What is the use case for this feature?

For projects with 100+ features, it is difficult to find features of interest as the only way to find feature information is by scrolling through the list. This filtering functionality will enable quicker feature retrieval.

Details

No response

What component(s) does this feature request affect?

• Python Client: This is the client users use to interact with most of our API. Mostly written in Python.
• Computation Engine: The computation engine that execute the actual feature join and generation work. Mostly in Scala and Spark.
• Feature Registry API: The frontend API layer supports SQL, Purview(Atlas) as storage. The API layer is in Python(FAST API)
• Feature Registry Web UI: The Web UI for feature registry. Written in React

[xiaoyongzhu]

Instead of the name, we should add tags, window duration, IDs, etc. basically all the columns in the entity table
500 features are hard to find

[windoze]

I've another prototyping Feathr Registry implementation at https://github.com/windoze/feathr-registry with clustering support, it also supports real FTS across names and descriptions (but not tags) atm, more fields can be added later.
You may want to take a look and put your comments.