acoustic-van-30942
11/01/2023, 6:07 PMcrooked-jordan-29960
11/02/2023, 8:32 PMcrooked-jordan-29960
11/02/2023, 8:35 PMacoustic-van-30942
11/02/2023, 8:36 PMcrooked-jordan-29960
11/02/2023, 8:36 PMacoustic-van-30942
11/02/2023, 8:38 PMacoustic-van-30942
11/02/2023, 8:41 PMFor feature engineering (ml use cases), sometimes the user may fetch different data resources (s3, kafka or snowflake), and do the transformation individually and merge together to transform a new feature set.
Of course, they can create a one gigantic processing code to handle all the logics from source to sink (e.g. offline feature store).
So usually we will encourage users to divide transformations logic into multiple smaller steps and construct as a DAG and using orchestration tool like Airflow.
Okay, then there is another issue, for ML use case, they may change their feature transformation logic very quickly, like branching out the same column and applying another transformation or creating another feature based on the same column, and also it’s really hard for users to figure out what the DAGs looks like in the beginning, so that they cannot even construct theirfiledag.py
acoustic-van-30942
11/02/2023, 8:42 PMcrooked-jordan-29960
11/02/2023, 8:45 PMacoustic-van-30942
11/02/2023, 8:58 PMflaky-plumber-70709
11/02/2023, 8:58 PMflaky-plumber-70709
11/02/2023, 9:01 PMflaky-plumber-70709
11/02/2023, 9:03 PMcrooked-jordan-29960
11/02/2023, 9:08 PMacoustic-van-30942
11/02/2023, 9:16 PMambitious-bird-15073
11/04/2023, 1:57 PMacoustic-van-30942
11/05/2023, 6:07 AM