Gunnar Liljas
Gunnar Liljas
How would you like "binding properties" to work?
https://github.com/confluentinc/confluent-kafka-dotnet/pull/1408
@shrohilla I would really appreciate a bit of feedback on a bunch of PR:s. This one is a very clear bug that was reported more than 2 years ago.
The PR doesn't update to 1.9.0, but to 1.8.2. Also, I think the references are only needed in the "Core" project.
Apparently, Confluent also wants it to be unique per consumergroup+client. Back to the code.
Got hit by this today. Not only did build.ps1 delete all my existing tools, it also failed to bootstrap itself.
Hi! Maybe I'm missing something here, and is just focusing on the title, but query space invalidation / time stamp updating is orthogonal to the cachability of entities.
Exactly. A cached query stores identifiers (or value projections) and should be invalidated whenever one of the included queryspaces is invalidated. It's not particularly efficient, especially with distributed caches, but...
A working feature might be to only allow queries to be cached if all included queryspaces/persisters have caching enabled.
Thanks! Please add tests too.