Skip to content

[EN] Add checking and error message if users want to materialize features that's defined on INPUT_CONTEXT. #767

@xiaoyongzhu

Description

@xiaoyongzhu

Willingness to contribute

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

Feathr version

0.8

System information

  • OS Platform and Distribution (e.g., Linux Ubuntu 20.0):
  • Python version:
  • Spark version, if reporting runtime issue:

Describe the problem

We should check if the materialized features are defined on INPUT_CONTEXT, and if it's not, we should give out warning and advise users use the right way to materialize features (maybe link to the corresponding docs)

Tracking information

No response

Code to reproduce bug

No response

What component(s) does this bug 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementFurther enhancement to improve usability

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions