-
Notifications
You must be signed in to change notification settings - Fork 652
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
FEAT: Properly implement map
operator
#4909
Labels
Epic
Internals
Internal modin functionality
new feature/request 💬
Requests and pull requests for new features
P2
Minor bugs or low-priority feature requests
Comments
noloerino
added
new feature/request 💬
Requests and pull requests for new features
P2
Minor bugs or low-priority feature requests
Internals
Internal modin functionality
labels
Aug 31, 2022
3 tasks
7 tasks
noloerino
added a commit
to noloerino/modin
that referenced
this issue
Nov 1, 2022
Signed-off-by: Jonathan Shi <jhshi@ponder.io>
noloerino
added a commit
to noloerino/modin
that referenced
this issue
Dec 6, 2022
Signed-off-by: Jonathan Shi <jhshi@ponder.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Epic
Internals
Internal modin functionality
new feature/request 💬
Requests and pull requests for new features
P2
Minor bugs or low-priority feature requests
Most of the behavior for the
map
operator proposed in the Modin research papers is actually covered by the broadcast_* methods on dataframe/partition manager classes. We should refactor the codebase to use the logic forbroadcast
withinmap
instead, which hopefully enables performance improvements.map
should also have an optionaldtypes
argument to hint the type of the resulting dataframe.See also: stale algebra tracking issue #2924.
The text was updated successfully, but these errors were encountered: