Vedran Pavic

> That would be useful if you have time, but we're not likely to get to this until after 3.0 has been released so no rush on our side. Got...

> Flagging for team attention to see how we should proceed. Seems like `for: team-meeting` label is missing here.

Thanks for the quick feedback Mark. > The issue here is that each subscription creates a Redis subscription that is unsubscribed when cancelling the stream: Hmm, but doesn't that mean...

Is there anything preventing this from making it into today's `3.0.0-M5` release?

Got it. I updated the PR to pick up the current `main`. Update: I just spotted a couple of new usages of old authorization DSL that have emerged since this...

Release `1.0.0` of `software.amazon.jdbc:aws-advanced-jdbc-wrapper` (hosted on https://github.com/awslabs/aws-advanced-jdbc-wrapper) has apparently been published in early October. With that in mind, maybe this could be revisited?

Since the last update here, AWS Advanced JDBC Driver project published a few [releases](https://github.com/awslabs/aws-advanced-jdbc-wrapper/releases) (including the recent `v2.0.0`) and has generally been adding features valuable for users of Aurora-flavored DBs...

Any updates on this? Status quo means that the default session repository for the most popular session data store (Redis) does not have actuator endpoint capability.

@chong-shao, sorry to tag you directly, but are there updates here? Now that Batch send API is getting decommissioned, using topics (if I'm not mistaken) is the only way to...

> Current optimizations on JDBC Session is good but still have large rooms for optimizations. I'm not sure this is the case - we've done what we can at `SessionRepositoryFilter`...