You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When defining a specific behavior for a StreamsProvider, the StreamsContainer in output currently cannot be used to instantiate a Model.
The enhancement would be to accept a StreamsContainer when creating a Model.
I know that other improvements to better handle the behavior of the readers is necessary, maybe at the DataSources level. We can discuss this in other issues.
Steps for implementing the feature
Change the Model.__init__ method to accept a StreamsContainer as data_sources. The parameter already accepts an str or a os.PathLike so we might as well accept a StreamsContainer.
Useful links and references
No response
The text was updated successfully, but these errors were encountered:
The remark was made that the reading settings could be something we set at the DataSources level, which then would be used to set the reading options of a StreamsProvider.
Description of the feature
When defining a specific behavior for a
StreamsProvider
, theStreamsContainer
in output currently cannot be used to instantiate aModel
.The enhancement would be to accept a
StreamsContainer
when creating aModel
.@MeenaBytes @ahernsean
I know that other improvements to better handle the behavior of the readers is necessary, maybe at the DataSources level. We can discuss this in other issues.
Steps for implementing the feature
Change the
Model.__init__
method to accept aStreamsContainer
asdata_sources
. The parameter already accepts anstr
or aos.PathLike
so we might as well accept aStreamsContainer
.Useful links and references
No response
The text was updated successfully, but these errors were encountered: