feathr-ai/feathr

[BUG] "csv" output format get_offline_features doesn't include the header (feature names).

Open

#811 opened on Nov 1, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Scala (1,929 stars) (244 forks)batch import
buggood first issue

Description

Willingness to contribute

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

Feathr version

0.8.0

System information

  • OS Platform and Distribution (e.g., Linux Ubuntu 20.0): Ubuntu 20
  • Python version: 3.10

Describe the problem

get_offline_features with the output format to be csv returns csv files without headers so that all the column names get lost including the feature names.

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

Contributor guide

Tech stack
pythonscala
Domain
data
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of FeathrPythonScala/Spark
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The bug is that CSV output from get offline features lacks headers. Look in the computation engine (Scala/Spark) for code that writes CSV files, likely in the Spark job logic. Also check the Python client that triggers the job to see if headers are expected. Since no reproduction steps are provided, you may need to set up a minimal Feathr example to replicate the issue. Examine the output path and the method that serializes features to CSV.
[BUG] "csv" output format get_offline_features doesn't include the header (feature names). · feathr-ai/feathr#811 | Good First Issue