-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
14 add dataprovider support #138
Conversation
Kudos, SonarCloud Quality Gate passed! |
private List<T> extractItemsFromDataProvider(final DataProvider<T, ?> dataProvider) | ||
{ | ||
return dataProvider.fetch(new Query<>()).collect(Collectors.toList()); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should do this like this. Here we're reading all the data from the Dataprovider.
A dataprovider can contain huge amounts of data and was likely designed with the thought that not all that data should be in memory at once.
Is there a different solution for handling the problem? Because this solution yields no improvements in my eyes.
Closed as PR is stale. |
No description provided.