Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] non-feature columns get converted into string columns when get result dataframe #942

Open
1 of 4 tasks
loomlike opened this issue Jan 5, 2023 · 0 comments
Open
1 of 4 tasks
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@loomlike
Copy link
Collaborator

loomlike commented Jan 5, 2023

Willingness to contribute

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

Feathr version

0.9.0

System information

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

Describe the problem

non-feature columns of the original source data get converted into string column, e.g. 0 (int) -> "0", True (bool) -> "True" string values when getting the feature result.

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
@loomlike loomlike added the bug Something isn't working label Jan 5, 2023
@loomlike loomlike changed the title [BUG] boolean values get converted into string when get result dataframe [BUG] non-feature columns get converted into string columns when get result dataframe Jan 5, 2023
@blrchen blrchen added the good first issue Good for newcomers label Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants