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

Stream engine fingerprinting needs improvement #922

Closed
bernd opened this Issue Jan 26, 2015 · 0 comments

Comments

Projects
None yet
2 participants
@bernd
Member

bernd commented Jan 26, 2015

The current stream and stream rule fingerprinting takes only the stream id, stream rules ids and the output ids into account. This is not enough to detect all changes to streams and stream rules.

Example: If the field of a stream rule is changed, the stream engine does not reload because the fingerprint does not change.

Maybe we can just use the hashCode() of the stream, stream rule and output objects to build the fingerprint.

@bernd bernd added the bug label Jan 26, 2015

@bernd bernd added this to the 1.0.0 milestone Jan 26, 2015

@kroepke kroepke self-assigned this Jan 27, 2015

@kroepke kroepke closed this in 47cf5af Jan 27, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment