Swapping the generics order in TSets
Previously TSets functions had generics as <O, I>. It is changed to <I, O>. (I= input type, O=output type). This is more in-line with other frameworks like Spark.
Removed Input type generic from ComputeTsets. Previously the signature was ComputeTSet<O, I>. But input types do not serve any purpose for a TSet, because no subsequent communication operations, do not care how that TSet was created. So, the new signature was changed to ComputeTSet<O> that only follows output type. Same logic follows for SComputeTSet<O>, KeyedTSet<K, V> and SKeyedTSet<K, V>.
Since this is a major API change,
@pulasthi could you please double-check the beam examples?
@vibhatha could you please double-check windowing examples?
Swapping the generics order in TSets Previously TSets functions had generics as <O, I>. It is changed to <I, O>. (I= input type, O=output type). This is more in-line with other frameworks like Spark.
Removed Input type generic from ComputeTsets. Previously the signature was
ComputeTSet<O, I>
. But input types do not serve any purpose for a TSet, because no subsequent communication operations, do not care how that TSet was created. So, the new signature was changed toComputeTSet<O>
that only follows output type. Same logic follows forSComputeTSet<O>
,KeyedTSet<K, V>
andSKeyedTSet<K, V>
.