-
Notifications
You must be signed in to change notification settings - Fork 93
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
Closes #1792 - GroupBy
Symbol Table Entry
#1805
Closes #1792 - GroupBy
Symbol Table Entry
#1805
Conversation
Converting to draft until I resolve the bug in gasnet. Also, realized I forgot to merge in updates to master and will do that as well. |
40424c8
to
7579cbc
Compare
Adding a note that #1807 is needed before merging this. |
c29dec9
to
9d2bcc2
Compare
9d2bcc2
to
3d09d05
Compare
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.
Only one thing really stood out to me, but not a blocker. The rest looked good.
…will be updated in the future to remove the dtype storage requirement. Currently only configured to build the GroupBy object from keys. Providing all elements is still fully client side, but will be moved in the future.
…ul on the CI. Correcting and repushing.
fd779bc
to
ef7915e
Compare
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.
Looks good! The only thing that might need changed is the getSizeEstimate
Closes #1792
GroupBy
objects. These are only created currently in the case whenkeys
is provided. If all elements are provided, the object remains client side. IssueGroupBy
Creationfrom_parts
#1803 addresses adding support creation from all components.GroupBySymEntry
inherits fromGenSymEntry
in preparation for removingCompositeSymEntry
.CompositeSymEntry
currently does not add any information that is not found inGenSymEntry
and does not appear necessary.GroupBy
object.createGroupBy
message.unique_keys
property is not stored on the server. IssueGroupBy.unique_keys
Server Side Computation #1804 will address computing Unique Keys on the server.This code utilizes components of
Unique
, but does not require the full workflow at this time.