[timeseries] Fix inconsistent item_id handling by GluonTS #2605
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Job PR-2605-add1592 is done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
AbstractGluonTSModelintroduced by [timeseries] Speed up prediction for GluonTS models #2593 that caused, e.g.,TemporalFusionTransformerMXNetmodel to fail.Background: Some GluonTS models always convert
item_idto a string, while others keep the original dtype (e.g., int). With this PR, we ensure that we always convertitem_idto a string internally, but return the correct dtype to the user.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.