Re: [I] vertex assigned to variable o1 was deleted - large create statements [age]
jrgemignani commented on issue #1627: URL: https://github.com/apache/age/issues/1627#issuecomment-2130534053 @MuhammadTahaNaveed I have not had an opportunity to look into this yet, sorry. -- 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 the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Unexpected Error: argument 1 must not be null [age]
jrgemignani commented on issue #882: URL: https://github.com/apache/age/issues/882#issuecomment-2130532359 Issue was resolved -- 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 the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Unexpected Error: function `ag_catalog.age_startnode` does not exist [age]
jrgemignani commented on issue #874: URL: https://github.com/apache/age/issues/874#issuecomment-2130531970 Issue was resolved. -- 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 the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Unexpected Error: function `ag_catalog.age_startnode` does not exist [age]
jrgemignani closed issue #874: Unexpected Error: function `ag_catalog.age_startnode` does not exist URL: https://github.com/apache/age/issues/874 -- 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 the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Unexpected Error: argument 1 must not be null [age]
jrgemignani closed issue #882: Unexpected Error: argument 1 must not be null URL: https://github.com/apache/age/issues/882 -- 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 the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [DISCUSS] Apache AGE - fully Graph DBMS PR
So long as it stays in its own branch, it shouldn't have any conflicts with AGE's source code. As it stands now, the PR was merged into the branch PROPOSAL_PG_Graph, by me. Again, this needs to go through the proper procedures. Otherwise, I'm fine with the addition. john On Fri, May 24, 2024 at 2:54 PM Rafsun Masud wrote: > Hi Everyone, > > To add one top of what has already been mentioned, > > AGE as an independent graph DBMS sounds interesting. It seems the file and > folder structure of such a project will be very different from the AGE as > an extension. In my opinion, there may be some challenges to maintain them > in the same repository. > > -- > *Rafsun Masud* > > > On Fri, May 24, 2024 at 8:32 AM John Gemignani > wrote: > > > If I am understanding this correctly, this is a PR for a new project > along > > side of the Apache AGE extension. It does not modify nor extend the > actual > > extension itself, which is Apache AGE. It merely adds an alternative, > > rooted in PostgreSQL version 13, to the extension. > > > > I am not opposed to thinking of Apache AGE as a suite of openCypher > > implementations and adding this as a fully integrated openCypher > > implementation option; this could give more options to users. > > > > However, as this PR is donated code, I believe it will need to go through > > the whole donation process. > > > > Additional questions to think about - > > > > How fully does it implement the openCypher specification compared to the > > extension? > > How does it perform relative to the extension? > > Will we have the resources to bring them into line and across all > > supported versions? > > Does the community want or need this? > > > > john > > > > On 2024/05/06 21:52:08 Eya Badal wrote: > > > Dear Everyone, > > > > > > I hope you are doing great. > > > > > > We would like to have a conversation about a recent Pull Request [1] > > that we received for Apache AGE. This Pull Request seems to introduce new > > extension features for AGE within the DBMS core engine. Currently, it > > utilizes PostgreSQL13 and aims to transform AGE from its existing > extension > > format into a fully Graph DBMS built on top of PostgreSQL[2]. > > > > > > Please let us know what you think. > > > > > > [1] https://github.com/apache/age/pull/1801 > > > [2] https://github.com/apache/age/issues/1802 > > > > > > > > > Thank you very much, > > > Eya Badal > > > > > >
Re: [DISCUSS] Apache AGE - fully Graph DBMS PR
Hi Everyone, To add one top of what has already been mentioned, AGE as an independent graph DBMS sounds interesting. It seems the file and folder structure of such a project will be very different from the AGE as an extension. In my opinion, there may be some challenges to maintain them in the same repository. -- *Rafsun Masud* On Fri, May 24, 2024 at 8:32 AM John Gemignani wrote: > If I am understanding this correctly, this is a PR for a new project along > side of the Apache AGE extension. It does not modify nor extend the actual > extension itself, which is Apache AGE. It merely adds an alternative, > rooted in PostgreSQL version 13, to the extension. > > I am not opposed to thinking of Apache AGE as a suite of openCypher > implementations and adding this as a fully integrated openCypher > implementation option; this could give more options to users. > > However, as this PR is donated code, I believe it will need to go through > the whole donation process. > > Additional questions to think about - > > How fully does it implement the openCypher specification compared to the > extension? > How does it perform relative to the extension? > Will we have the resources to bring them into line and across all > supported versions? > Does the community want or need this? > > john > > On 2024/05/06 21:52:08 Eya Badal wrote: > > Dear Everyone, > > > > I hope you are doing great. > > > > We would like to have a conversation about a recent Pull Request [1] > that we received for Apache AGE. This Pull Request seems to introduce new > extension features for AGE within the DBMS core engine. Currently, it > utilizes PostgreSQL13 and aims to transform AGE from its existing extension > format into a fully Graph DBMS built on top of PostgreSQL[2]. > > > > Please let us know what you think. > > > > [1] https://github.com/apache/age/pull/1801 > > [2] https://github.com/apache/age/issues/1802 > > > > > > Thank you very much, > > Eya Badal > > >
Re: [I] DAG support [age]
jrgemignani commented on issue #1821: URL: https://github.com/apache/age/issues/1821#issuecomment-2130342234 @spbnick The graph is stored in tables. However, for some queries [VLE specifically] there is an in-memory data structure that represents the graph allowing graph algorithms easier transversal. -- 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 the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [DISCUSS] Apache AGE - fully Graph DBMS PR
If I am understanding this correctly, this is a PR for a new project along side of the Apache AGE extension. It does not modify nor extend the actual extension itself, which is Apache AGE. It merely adds an alternative, rooted in PostgreSQL version 13, to the extension. I am not opposed to thinking of Apache AGE as a suite of openCypher implementations and adding this as a fully integrated openCypher implementation option; this could give more options to users. However, as this PR is donated code, I believe it will need to go through the whole donation process. Additional questions to think about - How fully does it implement the openCypher specification compared to the extension? How does it perform relative to the extension? Will we have the resources to bring them into line and across all supported versions? Does the community want or need this? john On 2024/05/06 21:52:08 Eya Badal wrote: > Dear Everyone, > > I hope you are doing great. > > We would like to have a conversation about a recent Pull Request [1] that we > received for Apache AGE. This Pull Request seems to introduce new extension > features for AGE within the DBMS core engine. Currently, it utilizes > PostgreSQL13 and aims to transform AGE from its existing extension format > into a fully Graph DBMS built on top of PostgreSQL[2]. > > Please let us know what you think. > > [1] https://github.com/apache/age/pull/1801 > [2] https://github.com/apache/age/issues/1802 > > > Thank you very much, > Eya Badal >
