Gunnar Liljas
Gunnar Liljas
The settable properties on KafkaEventData are important for the flow of events, especially the offset. They should not be subject to tampering. IMO, different types should be used for sending...
Allows injecting custom scaling logic. Now, in fairness, the factory could have been an IScaleMonitorFactory. Use case: Custom handling of scaling, based on metrics, such as ensuring (at least trying)...
Just a POC. Kafka and the Confluent client has support for listening to multiple topics with only one consumer. It would be quite useful to use that functionality with KafkaTrigger,...
It's useful e.g in a scenario where multiple functions are in the same function app, and there's something (like in our case, a retry handler) that should be able to...
This is more a POC than a PR. It gives a somewhat weird but also convenient way to handle the issue mentioned in #161. I've experimented with a few ways,...
Adds a ClientId parameter to the KafkaTrigger. This is good thing to have, e.g for collecting metrics. In our Confluent dashboard we get this warning: "Unable to compute throughput. There...
Maybe a minor thing, but I think all (?) modern libraries should move to DateTimeOffset, instead of DateTime. It's a much better datatype and it's what's recommended by the Framework...
Guid values were basically dropped before.
A query like this: ``` var result = db.OrderLines .GroupBy(x => new {x.Order.OrderId,x.Order.OrderDate}) .Select(x => new { OrderIdString = x.Key.OrderId.ToString(), x.Key.OrderDate, Count=x.Count() }) .ToArray(); ``` where the grouping is done...