input
stringlengths
1
12.6k
output
stringlengths
1
12k
so it should be possible to pickle and run tasks directly from notebook onto a flyte-server
that's epic I'm imagining map tasks from within notebook would be incredible
that's epic I'm imagining map tasks from within notebook would be incredible
yup exactly also distributed training and others so i think we should just rewrite this resolverrr <https://github.com/flyteorg/flytekit/blob/master/flytekit/extras/cloud_pickle_resolver.py> or use this resolver to use in fast-execute and update pyflyte-fast-execute to use cloudpickle as an option and then it should just work IMO? Also <@U019PBV483E> have you seen the new map-tasks support for multiple-lists etc and partials?
yup exactly also distributed training and others so i think we should just rewrite this resolverrr <https://github.com/flyteorg/flytekit/blob/master/flytekit/extras/cloud_pickle_resolver.py> or use this resolver to use in fast-execute and update pyflyte-fast-execute to use cloudpickle as an option and then it should just work IMO? Also <@U019PBV483E> have you seen the new map-tasks support for multiple-lists etc and partials?
I haven't yet
I haven't yet
this is in beta, some small bugs being fixed, but keep an eye <https://github.com/flyteorg/flytekit/pull/1556>
<@U03BT8P2XGA> training operator is already integrated
Ah nice - I thought that was only the TF/torch operator, but saw that this includes xgboost (which I guess in turn can support lightgbm, which is what we care about) We're currently in the process of figuring out if it's easier to distribute lgbm w/ dask or the KF operator, jury's still out
Ah nice - I thought that was only the TF/torch operator, but saw that this includes xgboost (which I guess in turn can support lightgbm, which is what we care about) We're currently in the process of figuring out if it's easier to distribute lgbm w/ dask or the KF operator, jury's still out
Ohh interesting it uses training operator But you are right others are not there yet
Thanks for setting this up <@U04H6UUE78B>, I think creating an initial issue or discussion might be a good place to have the conversation in the open.
there you go: <https://github.com/flyteorg/flyte/discussions/3593>
Hey everyone!
welcome Dominik!