Open fschueler opened 8 years ago
I see a lot of times Spark instructions are manually optimized to use a broadcast/ map-side join. I think this optimization is not needed for Flink. I think we should always use the Flink operator with the best semantics and give the Flink optimizer the enough meta information to find the perfect plan. For instance the matrix multiplication (Mapmm and MapmmChain) could be extended to use Flink's JoinHint
s.
This issue tracks the status of instructions. Please insert the instruction that you're working on and your name into the table and don't forget to mark it as finished once you're done.
MLContext
is missing