Last updated on MARCH 08, 2017
Applies to:MySQL Cluster - Version 7.2 and later
Information in this document applies to any platform.
There are actually two versions of event handling currently in ndbapi - v1 and v2.
The v2 methods will be labeled as such e.g. pollEvent2(), nextEvent2() etc.
When adding specific filtering event types e.g. TE_INSERT, TE_DELETE and TE_UPDATE to the addTableEvent() method, why does the application get flooded with TE_EMPTY event types instead of getting filtered, and how do I handle it?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms