-
Notifications
You must be signed in to change notification settings - Fork 19
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
Data Builder Record Abstraction #5
Data Builder Record Abstraction #5
Conversation
Signed-off-by: Andrew <andrjc4@vt.edu>
612ef6c
to
b5e1c5c
Compare
will take a look, thanks for the RFC |
Co-authored-by: Marcos Iglesias <190833+Golodhros@users.noreply.github.com>
Signed-off-by: Andrew <andrjc4@vt.edu>
8e76c0c
to
30461fe
Compare
Co-authored-by: Marcos Iglesias <190833+Golodhros@users.noreply.github.com> Signed-off-by: Andrew <andrjc4@vt.edu>
30461fe
to
61eab0c
Compare
Signed-off-by: Andrew <andrjc4@vt.edu>
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.
do you see any backward compatibility issue?
also the DCO fails as well |
|
||
## Reference-level Explanation (aka Technical Details) | ||
|
||
Each of the models in the databuilder are built off of the `GraphSerializable` class. The `GraphSerializable` class is an abstract class that is responsible for validating and returning the nodes and relationships of its subclasses. The interface on the `GraphSerializable` is `next_node` with a return type of `Union[GraphNode, None]` and `next_relation` with a return type of `Union[GraphRelationship, None]`. |
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.
make sense
|
||
## Drawbacks | ||
|
||
This adds a level of complexity because it adds an additional layer to the databuilder. Instead of having the neo4j serialization built into the models it becomes a separate process. This also would add a small performance degradation because the models are producing named tuples and then they are being convered into another format. |
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.
could you elaborate a bit or maybe you could create the pr and point me to the place of this?
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.
yeah what I was trying to get at here is that there is a slight performance degradation because you are now converting from a named tuple to a dictionary.
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 I see, it should be fine.
also could you create the pr with your branch? thanks a lot |
I am not sure if its a bug or a typo but some of the timestamps were not unquoted. I currently have it so it is unquoted let me know if that is unwanted. |
@AndrewCiambrone I just merged the change. Could you update this rfc and move it under rfcs folder and name it 002-xxx.md? thanks. |
…record-abstraction-rfc
…record-abstraction-rfc
Signed-off-by: Andrew <andrjc4@vt.edu>
Signed-off-by: Andrew <andrjc4@vt.edu>
* RFC for introducing an abstraction layer to the databuilder records Signed-off-by: Andrew <andrjc4@vt.edu> * Update templates/000-databuilder-record-abstraction.md Co-authored-by: Marcos Iglesias <190833+Golodhros@users.noreply.github.com> * RFC for introducing an abstraction layer to the databuilder records Signed-off-by: Andrew <andrjc4@vt.edu> * remove merge tags Signed-off-by: Andrew <andrjc4@vt.edu> * move the rfc to the rfc folder Signed-off-by: Andrew <andrjc4@vt.edu> * delete old rfc in template folder Signed-off-by: Andrew <andrjc4@vt.edu> Co-authored-by: Marcos Iglesias <190833+Golodhros@users.noreply.github.com> Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>
* RFC for introducing an abstraction layer to the databuilder records Signed-off-by: Andrew <andrjc4@vt.edu> * Update templates/000-databuilder-record-abstraction.md Co-authored-by: Marcos Iglesias <190833+Golodhros@users.noreply.github.com> * RFC for introducing an abstraction layer to the databuilder records Signed-off-by: Andrew <andrjc4@vt.edu> * remove merge tags Signed-off-by: Andrew <andrjc4@vt.edu> * move the rfc to the rfc folder Signed-off-by: Andrew <andrjc4@vt.edu> * delete old rfc in template folder Signed-off-by: Andrew <andrjc4@vt.edu> Co-authored-by: Marcos Iglesias <190833+Golodhros@users.noreply.github.com> Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>
No description provided.