Hi Andrey
thanks for answer.
It seems that is not possible to handle case class evolution in version
which I currently use (1.5.3).
Do you have any recommendation how to avoid such problem in future? Adding a
new field with default value to an existing class seems to me as a common
use case. Can
Hi,
I run simple streaming job where I compute hourly impressions for campaigns:
.keyBy(imp => imp.campaign_id)
.window(TumblingEventTimeWindows.of(...))
.aggregate(new BudgetSpendingByImpsAggregateFunction(), new
BudgetSpendingByImpsWindowFunction())
Where aggregate function just sums impressio
