pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] revans2 commented on issue #881: updating Storm version in Pulsar
Date Thu, 01 Jan 1970 00:00:00 GMT
revans2 commented on issue #881: updating Storm version in Pulsar
URL: https://github.com/apache/incubator-pulsar/pull/881#issuecomment-342173192
   @jerrypeng is right that tick tuples are generally configured on a per component basis.
 It is possible for someone to set it for the entire topology, but most components will not
know how to handle it and will likely end up with exceptions.
   If you are scared about breaking compatibility, because a user could set it before without
issues, it should not be that big of a deal to leave the tick tuple checks in place.  But
if you do `org.apache.storm.utils.TupleUtils.isTickTuple` is the new preferred way to do it.
 It will be a very small performance cost if you do leave it in place though.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message