-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set the right output column type for forecast functions #1108
Set the right output column type for forecast functions #1108
Conversation
@hershd23 I have moved the |
if frequency is None: | ||
raise RuntimeError( | ||
f"Can not infer the frequency for {self.node.name}. Please explictly set it." | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thanks for adding this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks taking care of this @xzdandy!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
from evadb.utils.generic_utils import string_comparison_case_insensitive | ||
|
||
|
||
class GenericUtilsTests(unittest.TestCase): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I was wondering whether to create a new test file add in a new file or not. Thanks for this, makes it clear
Current forecast functions only output the y value. This PR fixes the binded output column, so forecasting functions also return unqiue_id and datastamp column.