Mike Lissner

This sounds good. As a next step, can you chat with Bill and think through any problems the new approach might cause, like duplicate alerts, missed ones, or something else?

I'm not sure I see it being necessary, but I could be convinced. Most of the case law team's work on historical content adds or cleans up fields, but I...

> Since that's the only place currently creating RealTimeQueue instances, which are required for triggering real-time Opinion alerts under the current Opinion Alerts approach. I think that means it's safe...

This sounds great, Alberto! Let's get a review from somebody on case law and from Eduardo. @flooie, can you or somebody on your team please look at this to make...

Sorry this one seems to have gotten stuck on my desk. The last comment was that we need a sign off from the case law folks. That still the case,...

@flooie, can you please take a look at this and give it your OK so we can move to using percolators for case law alerts (making them faster and infinitely...

@flooie I added a P1 priority on this because we just need your thoughts or review and it's been stuck awhile.

The countdown was meant to create jitter to spread big data loads around. I think we're past having to worry about this. Glad you guys came to the same conclusion....

Hm, if we wait until the end of the week and the end of the month, could we just do the swap over at a convenient time and avoid the...

Sounds great. > The only thing to consider is timing, these settings should be enabled right after the command for the corresponding rate (DLY, WLY, or MLY) completes, so we...