-
Notifications
You must be signed in to change notification settings - Fork 13.8k
[FLINK-6536] [cep] Improve error message in SharedBuffer::put(). #3872
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
Conversation
aljoscha
left a comment
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.
LGTM once Travis says it's green! 👍
| previousTimestamp + ". This can indicate that the element belonging to the previous " + | ||
| "relation has been already pruned, even though you expect it to be still there."); | ||
| previousTimestamp + ". This can indicate that either you did not implement " + | ||
| "the equals() and hashCode() methods, of your input elements properly or that " + |
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.
I think the comma is superfluous.
| "relation has been already pruned, even though you expect it to be still there."); | ||
| previousTimestamp + ". This can indicate that either you did not implement " + | ||
| "the equals() and hashCode() methods of your input elements properly or that " + | ||
| "the element belonging to that entry has been already pruned."); |
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.
Been thinking about this exception message and those two reasons for the exception come from "two different worlds".
- if element has been pruned - from user perspective this means some error in CEP library occured and the user can not do much about it.
- the equals() and hashCode() are obvious user mistakes.
Not sure if we should do sth with it, but just wanted to express my thoughts on 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.
You are right @dawidwys but I think that now the message makes clear that you should always implement equals() and hashCode(). So far it was only in the docs.
|
Merged. |
There are two commits that address both FLINK-6536 and FLINK-6255.
R @aljoscha