tft.scale_to_z_score_per_key should support non-string keys like tft.vocabulary does
@zoyahav is already working on this.
Since Nov 8, 2021.
Assessment
This issue has not been assessed yet.
Description
As it says in the title, tft.vocabulary allows you to pass in a feature of type tf.int[8|16|32|64] in addition to tf.string. It would be good if tft.scale_to_z_score_per_key could support this as well. Of course, I know I can just convert my int-valued keys to strings before calling tft.scale_to_z_score_per_key, but it would be easier if I didn't have to.
- Dominant language
- Python
- Stars
- 989
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tensorflow/transform
-
stat:contributions welcome type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
tensorflow/transform#347 ·
-
bug stat:awaiting response
Difficulty 3/5 1-2 days Newbie friendliness 35/100
tensorflow/transform#339 · 2 comments ·
-
stat:contributions welcome type:bug
tensorflow/transform#273 · 1 assignee ·
-
stat:contributions welcome type:support
tensorflow/transform#272 · 4 comments · 1 assignee ·
-
stat:contributions welcome type:bug
tensorflow/transform#265 · 3 comments · 2 assignees ·
All issues in tensorflow/transform
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100