You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, these files are created from the dataset passed into the NVTabular workflow, typically a transactions or interactions dataset, which only includes items that were sold or clicked.
However, I would like to generate these category metadata files from a full product dataset, which includes all possible item_id and category values, not just those that appear in transactions. Then I want to reuse the same categories/ folder when processing the transactions dataset, to ensure consistent and complete category encoding.
My question is:
Can I safely use the categories/ metadata generated from the full product dataset when applying the workflow to a smaller dataset like transactions?
Will NVTabular handle this correctly, without errors or inconsistencies during transformation?
The goal is to define a fixed category mapping based on the full catalog so it remains stable across training, inference, and future data, even if some category values are not present in the current dataset.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using NVTabular and applying Categorify to categorical features like this:
categ_feats = ['column1', 'column2'] >> nvt.ops.Categorify()
This generates metadata files such as:
By default, these files are created from the dataset passed into the NVTabular workflow, typically a transactions or interactions dataset, which only includes items that were sold or clicked.
However, I would like to generate these category metadata files from a full product dataset, which includes all possible item_id and category values, not just those that appear in transactions. Then I want to reuse the same categories/ folder when processing the transactions dataset, to ensure consistent and complete category encoding.
My question is:
Can I safely use the categories/ metadata generated from the full product dataset when applying the workflow to a smaller dataset like transactions?
Will NVTabular handle this correctly, without errors or inconsistencies during transformation?
The goal is to define a fixed category mapping based on the full catalog so it remains stable across training, inference, and future data, even if some category values are not present in the current dataset.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions