Re: [I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2024-05-18 Thread via GitHub
github-actions[bot] commented on issue #1284: URL: https://github.com/apache/age/issues/1284#issuecomment-2119036182 This issue was closed because it has been stalled for further 7 days with no activity. -- This is an automated message from the Apache Git Service. To respond to the

Re: [I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2024-05-18 Thread via GitHub
github-actions[bot] closed issue #1284: Efficient Techniques for Tracking Graph Changes in Apache AGE URL: https://github.com/apache/age/issues/1284 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2024-05-10 Thread via GitHub
github-actions[bot] commented on issue #1284: URL: https://github.com/apache/age/issues/1284#issuecomment-2105397149 This issue is stale because it has been open 45 days with no activity. Remove "Abondoned" label or comment or this will be closed in 7 days. -- This is an automated

Re: [I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2023-10-28 Thread via GitHub
danielwambo commented on issue #1284: URL: https://github.com/apache/age/issues/1284#issuecomment-1783915761 @MatheusFarias03 A good way to do this is by creating a separate table then store the log details in it i.e in any modification addition or deletion of vertices and edges.

Re: [I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2023-10-24 Thread via GitHub
jrgemignani commented on issue #1284: URL: https://github.com/apache/age/issues/1284#issuecomment-1778114979 @MatheusFarias03 One would need to research the mechanism that PG uses to log this data and then apply it to AGE. It "could", emphasis on "could", be a relatively easy thing to add.

Re: [I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2023-10-23 Thread via GitHub
MatheusFarias03 commented on issue #1284: URL: https://github.com/apache/age/issues/1284#issuecomment-1776008383 Thank you for the awesome detailed answers @danielwambo and @namsi-lia ! Based on your comments, I believe you guys definitely have a deeper knowledge about this. As

Re: [I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2023-10-23 Thread via GitHub
namsi-lia commented on issue #1284: URL: https://github.com/apache/age/issues/1284#issuecomment-1775993444 Storing metadata alongside graph elements might be beneficial in that this will store information about when the node and edges were created and when last they were modified.

Re: [I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2023-10-22 Thread via GitHub
danielwambo commented on issue #1284: URL: https://github.com/apache/age/issues/1284#issuecomment-1774447247 Maintaining a time-stamped audit log is a common and effective way to track changes. Whenever a vertex or edge is added, modified, or deleted, record the change with a

Re: [I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2023-10-20 Thread via GitHub
jrgemignani commented on issue #1284: URL: https://github.com/apache/age/issues/1284#issuecomment-1773145000 @MatheusFarias03 This is a topic that we've been discussing internally - Audit logs should already exist for any database action that can be logged, provided the DBA or admin

[I] Efficient Techniques for Tracking Graph Changes in Apache AGE [age]

2023-10-18 Thread via GitHub
MatheusFarias03 opened a new issue, #1284: URL: https://github.com/apache/age/issues/1284 Hello! There's a question on AGE's discord server related to graph changes and how to track them. I wanted you guys opinion first so that I can give the right answer there. --- **Question