When problems come up with subscriptions, it would be attractive if we could submit a "CANCEL SUBSCRIPTION" and/or "CANCEL TABLE" request that would be of higher priority (as an event) and which could quickly cause the cluster to reject a subscription or table that has somehow proven troublesome. Issues are severalfold: 1. Need to have a way of treating some events with higher priority so that they take place earlier than their injected event number indicates. 2. New SLONIK commands such as CANCEL SUBSCRIPTION, CANCEL TABLE.
*** This bug has been marked as a duplicate of bug 10 ***