-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
GraphStore
definition + Data
and HeteroData
integration
#4816
Conversation
…into feature_store_pt1
Codecov Report
@@ Coverage Diff @@
## master #4816 +/- ##
==========================================
- Coverage 84.53% 82.70% -1.83%
==========================================
Files 325 326 +1
Lines 17430 17518 +88
==========================================
- Hits 14735 14489 -246
- Misses 2695 3029 +334
Continue to review full report at Codecov.
|
"An edge layout is required to store an edge index, but one " | ||
"was not provided.") | ||
|
||
# NOTE implementations should take care to ensure that `SparseTensor` |
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.
What does that mean in this case?
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've updated this to work with Tuple[Tensor, Tensor]
directly; lmkwyt!
|
||
|
||
@dataclass | ||
class EdgeAttr(CastMixin): |
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.
This term is now a bit overloaded.
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.
In what manner? I think it aligns well with TensorAttr
in FeatureStore
(they are both attributes of objects we are trying to add to the respective stores).
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.
We usually refer to data.edge_attr
for edge attributes/features.
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.
Ah, right. I think it's probably okay to leave this overloaded term for now (mostly since I can't think of a better one), and if you have any ideas we can do a quick refactor.
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
@rusty1s @Padarn @wsad1: thank you for the feedback! This PR has been updated accordingly. A few notable changes:
Let me know what you think. |
MaterializedGraph
definition + Data
and HeteroData
integrationGraphStore
definition + Data
and HeteroData
integration
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 am super impressed. This is clean.
|
||
|
||
@dataclass | ||
class EdgeAttr(CastMixin): |
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.
We usually refer to data.edge_attr
for edge attributes/features.
Sorry I was really busy and didn't read your updates earlier @mananshah99 - looks awesome and thanks for your responses. |
This PR defines a very lightweight
MaterializedGraph
that supports basic put and get operations of edge indices. It additionally letsData
andHeteroData
inherit from and implement this abstraction.