You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
[3.3.0] - October 28th, 2019
New Features:
Added support for event batching via the event processor.
Events generated by methods like activate, track, and is_feature_enabled will be held in a queue until the configured batch size is reached, or the configured flush interval has elapsed. Then, they will be batched into a single payload and sent to the event dispatcher.
To configure event batching, set the batch_size and flush_interval properties when initializing instance of BatchEventProcessor.
Event batching is disabled by default. You can pass in instance of BatchEventProcessor when creating Optimizely instance to enable event batching.
Users can subscribe to LogEvent notification to be notified of whenever a payload consisting of a batch of user events is handed off to the event dispatcher to send to Optimizely's backend.
Introduced blocking timeout in PollingConfigManager. By default, calls to get_config will block for maximum of 10 seconds until config is available.
Bug Fixes:
Fixed incorrect log message when numeric metric is not used. (#217)