LAG e LEAD

Funções de janela no Snowflake

Jake Roach

Field Data Engineer

LAG

LAG permite comparar um valor com um valor em um registro anterior

SELECT
    <fields>,


    LAG(<1>, <2>, <3>) OVER(
        PARTITION BY <4>
        ORDER BY <5>
    )


...;

<1>: campo no registro anterior para recuperar

<2>: número de registros para "olhar para trás"

<3>: valor padrão se o registro não existir, 0

<4>: campo para particionar

<5>: campo para ordenar os registros

LAG

Um exemplo de conjunto de dados gerado usando LAG

LAG

SELECT
    member_id AS m_id, 
    workout_date AS wd,
    calories_burned AS cb,

    -- Recupere as calorias queimadas 
    -- do último treino

    LAG(calories_burned, 1) OVER(
        PARTITION BY member_id
        ORDER BY workout_date
    ) AS past_cb,


FROM fitness.workouts;

  m_id  |       wd     |   cb  |  past_cb 
 ------ | ------------ | ----- | ---------
 m_192  |  2024-01-01  |  105  |   null
 m_192  |  2024-01-03  |  156  |   105
 m_192  |  2024-01-04  |   69  |   156
 m_192  |  2024-01-10  |  102  |    69

 m_74   |  2024-02-10  |  374  |   null
 m_74   |  2024-02-13  |  396  |   374
 m_74   |  2024-02-14  |  504  |   396

 m_233  |  2024-03-05  |  51   |   null 
 m_233  |  2024-03-12  |  81   |    51

LAG

SELECT
    ...
    LAG(calories_burned, 1) OVER(
        PARTITION BY member_id
        ORDER BY workout_date
    ) AS past_cb,

    -- Encontre a diferença no número de calorias queimadas
``` {sql}
    calories_burned - LAG(calories_burned, 1, calories_burned) OVER(
        PARTITION BY member_id
        ORDER BY workout_date
    ) AS more_cb,


FROM fitness.workouts;

LAG

                  m_id  |       wd     |   cb  |  past_cb  |  more_cb
                ------- | ------------ | ----- | --------- | ---------
                 m_192  |  2024-01-01  |  105  |    null   |      0
                 m_192  |  2024-01-03  |  156  |    105    |     51
                 m_192  |  2024-01-04  |   69  |    156    |    -87
                 m_192  |  2024-01-10  |  102  |     69    |     33

                 m_74   |  2024-02-10  |  374  |    null   |      0
                 m_74   |  2024-02-13  |  396  |    374    |     22
                 m_74   |  2024-02-14  |  504  |    396    |    108

                 m_233  |  2024-03-05  |  51   |    null   |      0
                 m_233  |  2024-03-12  |  81   |     51    |     30

LEAD

LEAD permite comparar um valor com um valor em um registro "futuro"

<1>: campo no registro anterior para recuperar

<2>: número de registros para "olhar à frente"

<3>: valor padrão se o registro não existir

<4>: campo para particionar

<5>: campo para ordenar os registros

SELECT
    <fields>,


    LEAD(<1>, <2>, <3>) OVER(
        PARTITION BY <4>
        ORDER BY <5>
    )


...;

Comumente usado para tarefas preditivas

LEAD

SELECT
    member_id, 
    workout_date
    calories_burned,

    -- Após este treino, encontre a próxima data de treino
    LEAD(workout_date, 1) OVER(
        PARTITION BY member_id
        ORDER BY workout_date
    ) AS next_workout_date

FROM fitness.workouts;

LEAD

            m_id  |  workout_date  |  calories_bured  |  next_workout_date
          ------- | -------------- | ---------------- | -------------------
           m_192  |   2024-01-01   |        105       |     2024-01-03
           m_192  |   2024-01-03   |        156       |     2024-01-04
           m_192  |   2024-01-04   |         69       |     2024-01-10
           m_192  |   2024-01-10   |        102       |         null

           m_74   |   2024-02-10   |        374       |     2024-02-13
           m_74   |   2024-02-13   |        396       |     2024-02-14
           m_74   |   2024-02-14   |        504       |         null

           m_233  |   2024-03-05   |         51       |     2024-03-12 
           m_233  |   2024-03-12   |         81       |         null

Vamos praticar!

Funções de janela no Snowflake