Re: Controlling the Materialization of JOIN updates

2020-01-05 Thread Kurt Young
Good to hear that the patch resolved your issue, looking forward to hearing more feedback from you! Best, Kurt On Mon, Jan 6, 2020 at 5:56 AM Benoît Paris < benoit.pa...@centraliens-lille.org> wrote: > Hi Kurt, > > Thank you for your answer. > > Yes both fact tables and dimension tables are

Re: Controlling the Materialization of JOIN updates

2020-01-05 Thread Benoît Paris
Hi Kurt, Thank you for your answer. Yes both fact tables and dimension tables are changing over time; it was to illustrate that they could change at the same time but that we could still make a JOIN basically ignore updates from one specified side. The SQL is not the actual one I'm using, and as

Re: Controlling the Materialization of JOIN updates

2020-01-03 Thread Kurt Young
Hi Benoît, Before discussing all the options you listed, I'd like understand more about your requirements. The part I don't fully understand is, both your fact (Event) and dimension (DimensionAtJoinTimeX) tables are coming from the same table, Event or EventRawInput in your case. So it will

Controlling the Materialization of JOIN updates

2020-01-02 Thread Benoît Paris
Hello all! I'm trying to design a stream pipeline, and have trouble controlling when a JOIN is triggering an update: Setup: - The Event table; "probe side", "query side", the result of earlier stream processing - The DimensionAtJoinTimeX tables; of updating nature, "build side", the