noklam
06/27/2022, 5:35 PMsjster
06/27/2022, 5:51 PMdatajoely
06/27/2022, 5:53 PMdatajoely
06/27/2022, 5:53 PMsjster
06/27/2022, 6:14 PMdatajoely
06/27/2022, 6:17 PMdatajoely
06/27/2022, 6:23 PMsjster
06/27/2022, 6:43 PMsjster
06/28/2022, 6:17 PM2022-06-28 13:56:27,146 - kedro.pipeline.node - INFO - Running node: evaluate_mapping_in_embeddings_faiss: run_faiss([es_df,tu_df]) -> [res_faiss]
zsh: segmentation fault kedro run --tag run_faiss
datajoely
06/28/2022, 6:18 PMnoklam
06/29/2022, 11:42 AMsjster
06/29/2022, 2:51 PMsjster
06/29/2022, 2:51 PMs.hedayati
06/30/2022, 11:15 AMdatajoely
06/30/2022, 11:16 AMkedro run --env=prod
?s.hedayati
06/30/2022, 11:18 AMdatajoely
06/30/2022, 11:19 AMTemplatedConfigLoader
?s.hedayati
06/30/2022, 11:20 AMuser
07/01/2022, 3:42 PMantony.milne
07/01/2022, 5:03 PMgui42
07/01/2022, 6:21 PMdo_step_a=True
in the yaml add the step_a
node to a pipeline object? My intuition says that this is a counter pattern.antony.milne
07/01/2022, 9:26 PMafter_context_created
hook like this: https://github.com/kedro-org/kedro/discussions/1436#discussioncomment-2789761
If it suits your use case, better would be to register two pipelines in `pipeline_registry.py`:
pipeline_1 = pipeline(...)
pipeline_2 = pipeline_1 + [node_a]
and then run the pipeline you want through kedro run -p
Another alternative is to keep the node in the pipeline but just change the logic inside the node function itself to skip using something like on if not do_step_a: return
youmaaz
07/04/2022, 8:23 PMdatajoely
07/04/2022, 8:32 PMyoumaaz
07/04/2022, 8:35 PMdatajoely
07/04/2022, 8:35 PMyoumaaz
07/05/2022, 11:43 AMyoumaaz
07/06/2022, 7:35 AMdatajoely
07/06/2022, 7:43 AMdatajoely
07/06/2022, 7:43 AM