feathr-ai / feathr-ai/feathr

[BUG] get_offline_feature ignores `parquet` output file option

未关闭
#716 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
bug good first issue
主要语言
Scala
星标
1.9k
派生
247
PR 合并指标
30 天内没有已合并 PR

描述

### 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)**: both on Linux Ubuntu 20 and Databricks
- **Python version**: 3.10
- **Spark version, if reporting runtime issue**:

### Describe the problem

get_offline_feature always write into avro regardless of the execution config.

### Tracking information

_No response_

### Code to reproduce bug

Run:
```
get_offline_feature(
execution_configurations=SparkExecutionConfiguration({
"spark.feathr.inputFormat": "parquet",
"spark.feathr.outputFormat": "parquet",
}),
....
)
```
still write file as avro

### 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

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。