Will AGE be backwards compatible for future releases? #74
Replies: 5 comments 4 replies
-
|
The underlying storage is through PostgreSQL, which is why agtype was based
off of jsonb. So, that shouldn't change much. If anything, we would add to
it.
Our plan is to adhere to the openCypher specification as closely as
possible, so there shouldn't be anything that works in earlier versions
that is left out in later versions.
Hopefully that answers your questions.
John
…On Wed, May 19, 2021 at 8:00 AM Richard L. Burton III < ***@***.***> wrote:
I know this is a tough one to answer, but I'm wondering what will the
upgrade path be for this project and if there any breaking changes in how
the data is stored, will there be a migration path?
I know it's still early stages, but I am interested in using this
extension for a project and I'm just curious about how things will progress
over time and if there will be breaking changes that might prevent a
project using an older version from upgrading.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#74>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALPO4HVMHBRUV4ZUZTQKCLTOPHBRANCNFSM45E3WRQQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you! This is what I assumed as well and in terms of queries, the abstraction is the cypher specification. I was also trying to find a feature compatibility for Cypher. Does one exist? In the past, I was using the Roadmap to get a sense of compatibility, but there wasn't a good definitive list. Keep up the amazing work! |
Beta Was this translation helpful? Give feedback.
-
|
I am in the same situation. As for being able to know the working queries, the tests in the regress folder of the repo are a great help, but they are not really sufficient to know exactly in an "easy manner" what is not yet possible to do. Probably a good solution would be to create some tests for all the openCypher features and generate a table with all the results after any commit? It would be easy to know at a glance the compatibility with AGE? |
Beta Was this translation helpful? Give feedback.
-
|
We try to follow -
https://www.opencypher.org/resources
https://s3.amazonaws.com/artifacts.opencypher.org/openCypher9.pdf
However, it can leave a lot to be desired at times. We also try to
reconcile against Neo4j.
John
…On Wed, May 19, 2021 at 9:53 AM Richard L. Burton III < ***@***.***> wrote:
Thank you! This is what I assumed as well and in terms of queries, the
abstraction is the cypher specification.
I was also trying to find a feature compatibility for Cypher. Does one
exist? In the past, I was using the Roadmap to get a sense of
compatibility, but there wasn't a good definitive list.
Keep up the amazing work!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#74 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALPO4D5PM3BKS4RJ4RTR5DTOPUKJANCNFSM45E3WRQQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Point taken, I will mention that [a table of done and to do] to the team.
John
On Wed, May 19, 2021 at 10:14 AM John Gemignani ***@***.***>
wrote:
… We try to follow -
https://www.opencypher.org/resources
https://s3.amazonaws.com/artifacts.opencypher.org/openCypher9.pdf
However, it can leave a lot to be desired at times. We also try to
reconcile against Neo4j.
John
On Wed, May 19, 2021 at 9:53 AM Richard L. Burton III <
***@***.***> wrote:
> Thank you! This is what I assumed as well and in terms of queries, the
> abstraction is the cypher specification.
>
> I was also trying to find a feature compatibility for Cypher. Does one
> exist? In the past, I was using the Roadmap to get a sense of
> compatibility, but there wasn't a good definitive list.
>
> Keep up the amazing work!
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#74 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AALPO4D5PM3BKS4RJ4RTR5DTOPUKJANCNFSM45E3WRQQ>
> .
>
|
Beta Was this translation helpful? Give feedback.
-
|
I also noticed that |
Beta Was this translation helpful? Give feedback.
-
|
We have releases roughly every 2 months. Those releases contain everything
up to that point in time, packed up (Docker for example) for more general
usage.
If you want the latest - and potentially bleeding edge - you can just clone
the current master and build the extension.
John
…On Wed, May 19, 2021 at 10:23 AM Richard L. Burton III < ***@***.***> wrote:
I also noticed that MERGE was in v0.3.0 and I'm guessing that
https://hub.docker.com/r/sorrell/agensgraph-extension is outdated because
it doesn't accept the MERGE command. I'm only using the docker container
for testing out designs.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#74 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALPO4CSE3G5C22KJW67ZZTTOPXYRANCNFSM45E3WRQQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Okay, I did that a few minutes ago and received the same error. I searched the code base and looks like The git history doesn't show it ever existed in this file, so I suspect it wasn't implemented? |
Beta Was this translation helpful? Give feedback.
-
|
MERGE is still being worked on - it is one of the more difficult operations.
john
…On Wed, May 19, 2021 at 10:36 AM Richard L. Burton III < ***@***.***> wrote:
Okay, I did that a few minutes ago and received the same error. I searched
the code base and looks like MERGE isn't anywhere to be found. I don't
see it listed in the cypher_keywords.c
https://github.com/apache/incubator-age/blob/83426d3a92bd5fee06376a38542d35efb1e6397b/src/backend/parser/cypher_keywords.c
although the roadmap says it was in version 0.3.0.
The git history doesn't show it ever existed in this file, so I suspect it
wasn't implemented?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#74 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALPO4BKF5JYWQPOYCHQATDTOPZLNANCNFSM45E3WRQQ>
.
|
Beta Was this translation helpful? Give feedback.
-
I know this is a tough one to answer, but I'm wondering what will the upgrade path be for this project and if there any breaking changes in how the data is stored, will there be a migration path?
I know it's still early stages, but I am interested in using this extension for a project and I'm just curious about how things will progress over time and if there will be breaking changes that might prevent a project using an older version from upgrading.
Beta Was this translation helpful? Give feedback.
All reactions