[DISCUSS] Apache AGE First Release

[John Gemignani]

Dear all,
 
We would like to discuss the Apache AGE release 0.3.0. that we have been 
working toward it. This release is the first release of Apache AGE.
 
Functionalities included and addressed in this release:
·   Standard functions
·   User defined functions
·   Aggregate functions (partial)
·   Property constraints
·   SET clause (Simple scenario where one property is updated)
·   REMOVE clause
·   Define extension’s behavior when dropped
 
 
1- The git tag to be voted upon:
https://github.com/apache/incubator-age/releases/tag/v0.3.0.rc0-incubating
 
2- The git commit hash:
commit 549ac9ff63337f64a9c19d8b9950b89ae412edee

 
3- THE SOURCE TARBALL CAN BE FOUND 
https://dist.apache.org/repos/dist/dev/incubator/age/0.3.0.rc0/
 
4- The fingerprint of key to sign release artifacts:
 FD8B 268F 784A CE10 F201  E63B C063 8775 6375 38D2
 
5- Release artifacts are signed with one of the keys available at:
https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
 
6- The release notes:
 https://github.com/apache/incubator-age/releases/tag/v0.3.0.rc0-incubating
 
Please share your thoughts and feedback and let us know if we can call for a 
vote. 

John

Re: [DISCUSS] Apache AGE First Release

[John Gemignani]

Hi all,

Could we get an update on this please?

Thank you!

john

On Fri, Jan 22, 2021 at 4:01 PM John Gemignani 
wrote:

> Dear all,
>
> We would like to discuss the Apache AGE release 0.3.0. that we have been
> working toward it. This release is the first release of Apache AGE.
>
> Functionalities included and addressed in this release:
> ·   Standard functions
> ·   User defined functions
> ·   Aggregate functions (partial)
> ·   Property constraints
> ·   SET clause (Simple scenario where one property is updated)
> ·   REMOVE clause
> ·   Define extension’s behavior when dropped
>
>
> 1- The git tag to be voted upon:
> https://github.com/apache/incubator-age/releases/tag/v0.3.0.rc0-incubating
>
> 2- The git commit hash:
> commit 549ac9ff63337f64a9c19d8b9950b89ae412edee
>
>
> 3- THE SOURCE TARBALL CAN BE FOUND
> https://dist.apache.org/repos/dist/dev/incubator/age/0.3.0.rc0/
>
> 4- The fingerprint of key to sign release artifacts:
>  FD8B 268F 784A CE10 F201  E63B C063 8775 6375 38D2
>
> 5- Release artifacts are signed with one of the keys available at:
> https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
>
> 6- The release notes:
>
> https://github.com/apache/incubator-age/releases/tag/v0.3.0.rc0-incubating
>
> Please share your thoughts and feedback and let us know if we can call for
> a vote.
>
> John
>

Re: Request for First AGE Apache Release Review - VOTE

[John Gemignani]

Hi all,

@vongosling  "I'm more concerned about the activities
of our community than that. Our mailing list doesn't seem to see the voice
of discussion."

My concerns about the community discussions, and partly why I don't use
this to communicate with Josh (besides what Josh has stated above), are the
expectations that I don't know. Please, if there is a document that covers
this, point me to it.

   - What is expected that we discuss here? What level of granularity? What
   details?

There can be a lot of noise generated with constant emails that will
completely obscure important discussions.


   - Are we expected to wait for others to give their input for all of our
   discussions?  How long are we expected to wait for a response before going
   ahead?

There can be decisions that need to be communicated promptly. Waiting for a
comment could be pointless and not waiting might give the appearance of not
caring about others input.

I do understand that most may be volunteers and I mean no disrespect.
However, I do feel that it is necessary to point out that our team members
aren't volunteers - this is actually our job. So, while it might not be
important to others to give, or have, a prompt response, for us it can be
vital.

I hope this conveys my questions and concerns.

Thank you for your input in advance,

John

On Thu, Jan 21, 2021 at 7:33 PM Josh Innis  wrote:

> Hi Felix,
>
> John and I were friends before working together, so we are used to
> discussing things privately; also we have a Google Hangouts forum we use
> when we wanna talk to each other. When our project was donated to Apache we
> decided to move all necessary communication to the Slack channel you are
> included in. In retrospect, all we post there are patches that John and I
> have already deemed necessary to the project. John and I have discussed
> this and will endeavour to move our discussion to the Apache AGE mailing
> lists. Thank you for understanding and sorry for the trouble.
>
> On Thu, Jan 21, 2021 at 5:13 PM Eya Badal  wrote:
>
> > Please disregard the previous message. I just replaced it with "the
> Apache
> > Incubator PMC."
> >
> > On 2021/01/21 23:29:50, Eya Badal  wrote:
> > > Hello @ Felix Cheung   and all,
> > >
> > > Regarding the WIP-Disclaimer, could you please advise what to include
> > when it mentioned "the name of Apache TLP sponsor". I am not sure about
> > this part.
> > >
> > > Thank you very much.
> > >
> > > "Apache AGE is an effort undergoing incubation at The Apache Software
> > Foundation (ASF), sponsored by the name of Apache TLP sponsor. "
> > >
> > >
> > > On 2021/01/19 05:58:03, Felix Cheung 
> wrote:
> > > > Thanks for the updates.
> > > >
> > > > For disclaimer: it is your first release, so it is likely something
> is
> > off (for example, you have a dependency that is not compatible with
> Apache
> > license and normally will not be possible to release with) it is just
> > easier to get through the process. The community can decide if you want
> to
> > go this route or not.
> > > >
> > > > For OpenCypher - if it is a public spec from OpenCypher, it will be
> > best not to include a file but link to it. Even if license compatible it
> is
> > best not to include files, source code etc from another project because
> > then proper attribution should be there (typically in the LICENSE or
> NOTICE
> > file)
> > > >
> > > > See bundled dependencies here
> > https://infra.apache.org/licensing-howto.html
> > > >
> > > >
> > > > 
> > > > From: Eya Badal 
> > > > Sent: Monday, January 18, 2021 7:32 AM
> > > > To: dev@age.apache.org
> > > > Subject: Re: Request for First AGE Apache Release Review - VOTE
> > > >
> > > > Hi Felix,
> > > >
> > > > I just want to mention some points.
> > > >
> > > > 1-I did update the svn with new files. The unzipping to different
> > names is fixed now.
> > > > 2-I also removed the md5 file and KEYS file from the svn and source
> > distribution.
> > > > 3-As I mentioned before the OpenCypher is based on Apache License and
> > it is included.
> > > > 4-Regarding the DISCLAIMER-WIP:
> > > > We do not have any tasks to do or tasks pending and not sure if we
> > have to go by DISCLAIMER-WIP. What is your advice?
> > > >
> > > > All the licenses are there and I do not have anything for pending
> > tasks so I am not sure if we should use Standard or Work in Progress
> > disclaimer. Please advise.
> > > >
> > > > We will wait for your advice and then call for a VOTE.
> > > >
> > > > Best regards,
> > > >
> > > > On 2021/01/18 02:59:15, Felix Cheung 
> > wrote:
> > > > > Yes. See the link I included in my reply for subject, format and
> > content.
> > > > >
> > > > >
> > > > > 
> > > > > From: Eya Badal 
> > > > > Sent: Sunday, January 17, 2021 6:30:04 PM
> > > > > To: dev@age.apache.org 
> > > > > Subject: Re: Request for First AGE Apache Release Review - VOTE
> > > > >
> > > > > Thank you very much, Flex. I appreciate t

Re: [apache/incubator-age] return value out of range (#15)

[John Gemignani]

Hi Martin,

I'm assuming this generated an error for you on compile? Which os/compiler
did you use? On our various compiles this does not show up.

As for the issue, in PostgreSQL the *ereport *function causes an exit, so
execution will never reach the return that follows. Some compilers complain
if there isn't a final return in a function, so that is why there is one.
Although, it will never reach it.

I will correct it with a patch, though, so that it won't cause any other
issues.

John


On Wed, Jan 27, 2021 at 1:17 AM Martin Strunz 
wrote:

> /src/backend/utils/adt/agtype_util.c line 1536 Non-boolean value returned
> from function returning bool
> static bool equals_agtype_scalar_value(agtype_value *a, agtype_value *b)
> {
> if (a->type == b->type)
> {
> switch (a->type)
> {
> case AGTV_NULL:
> return true;
> case AGTV_STRING:
> return length_compare_agtype_string_value(a, b) == 0;
> case AGTV_NUMERIC:
> return DatumGetBool(DirectFunctionCall2(
> numeric_eq, PointerGetDatum(a->val.numeric),
> PointerGetDatum(b->val.numeric)));
> case AGTV_BOOL:
> return a->val.boolean == b->val.boolean;
> case AGTV_INTEGER:
> return a->val.int_value == b->val.int_value;
> case AGTV_FLOAT:
> return a->val.float_value == b->val.float_value;
> case AGTV_VERTEX:
> {
> graphid a_graphid, b_graphid;
> a_graphid = a->val.object.pairs[0].value.val.int_value;
> b_graphid = b->val.object.pairs[0].value.val.int_value;
>
> return a_graphid == b_graphid;
> }
>
> default:
> ereport(ERROR, (errmsg("invalid agtype scalar type %d for equals",
>a->type)));
> }
> }
> ereport(ERROR, (errmsg("agtype input scalars must be of same type")));
> return -1; // <- should be bool
>
> }
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> , or unsubscribe
> 
> .
>

[DISCUSS] Apache AGE openCypher auto group by

[John Gemignani]

Hi All,

In researching and designing a way to implement the auto group by feature of 
openCypher, I believe that it is necessary to split it into two distinct cases -

1) Explicit group by keys. Fx: RETURN key, aggregate(x);
2) Implicit group by keys: Fx: RETURN aggregate(x)/key;

For now, I believe that we should only implement #1. Per the documentation, 
tests, and other sources (see below), #2 is too ambiguous to implement and will 
only cause confusion. Additionally, not implementing it, would not affect 
feature usability - you can always explicitly state the key.

https://www.opencypher.org/articles/2017/07/27/ocig1-aggregations-article/

So, for now, I am proposing to only implement #1 (explicit group by keys). 
Implicit group by keys should be tabled until a later date.

John

[DISCUSS] Apache AGE Coding standard adjustment

[John Gemignani]

Hi,

The following coding standard adjustments have been suggested by our team in 
our last meeting. It is felt that going forward we need to conform to these.

1) All functions should have top level descriptions (comments) going 
forward. 
2) All functions should contain more comments on functionality. It doesn't 
have to be a book or a tome. 
3) Use #define, for any string or character constants.
4) Use enums whenever possible.
5) Use macros where possible.
6) For the if/else structures, the preference is for braces, even for one 
line of code.
7) If you are working on a function that does not conform, try to bring it 
up to date.

John

Re: [GitHub] [incubator-age] pdpotter opened a new issue #48: Using geographic objects as properties with PostGIS

[John Gemignani]

When a function isn't prefaced with the schema in the cypher function call,
the transform logic will see it as a cypher function and prepend age_ to
the name and then add the schema ag_catalog. This avoids naming clashes and
helps with understanding where the system is looking for something.  So, if
you want to use a specific PG or other user function, you need to specify
the specific schema that it is in. When a schema is provided, the transform
logic no longer looks for it in ag_catalog with a prepended age_. The
function call transforms, inside the cypher function call, recurse through
the arguments. So, nested calls will be processed by AGE in the above
manner.

This logic may, or may not change in the future. The issue here is that the
PG routines that search for the function will exit if one is not found. So
our code - unless we add in more of PG's code and modify it - will never
get a second chance to process it for additional matches. So, we had to
find a happy middle ground. Unfortunately, some of PG's errors are vague.
Was it not found at all? or just not one that matches the arguments? Only
the debugger can tell you.

For this particular issue, this means that any non-AGE function needs its
schema name added if it appears in the cypher function command. As an
example, for PG's sqrt(4), it would be pg_catalog.sqrt(4).

Additionally, any function argument inside the cypher function command will
be transformed through AGE. These are not the same typecasts as PG's
typecasts.  So, typecasts like 4::float, will be translated as some number
into agtype float, not PG's float. We plan on adding ones like ::pg_float
shortly. There is currently an exception to this, and that is due to an
implicit cast that is going to be removed and replaced by an explicit cast.
There is an implicit cast to float, that will be removed shortly, so if
everything is correctly named, what you have above should work - for items
that can be cast to a float.

As an example -

psql-11.5-5432-pgsql=# SELECT * from cypher('test', $$
RETURN pg_catalog.sqrt(pg_catalog.sqrt(pg_catalog.sqrt(256)))
$$) as (result agtype);
 result

 2.0
(1 row)

Hopefully this helps. Unfortunately, I am unable to get Postgis installed
and therefore I can't debug it further at this time.

John

On Mon, Mar 29, 2021 at 6:18 AM GitBox  wrote:

>
> pdpotter opened a new issue #48:
> URL: https://github.com/apache/incubator-age/issues/48
>
>
>Is there a way to add PostGis data as property to a node (e.g., a
> [point geometry](https://postgis.net/docs/ST_MakePoint.html))?
>
>I've tried:
>```
>SELECT * FROM cypher('testgraph', $$
>CREATE (n:Test {id: 1, location: ST_SetSRID(ST_MakePoint(-71.10,
> 42.32),4326)}) return n
>$$) as (a agtype);
>ERROR:  function ag_catalog.age_st_makepoint(agtype, agtype) does not
> exist
>LINE 2: ... (n:Test {id: 1, location: ST_SetSRID(ST_MakePoint(-71.10,
> 4...
> ^
>HINT:  No function matches the given name and argument types. You might
> need to add explicit type casts.
>
>SELECT * FROM cypher('testgraph', $$
>CREATE (n:Test {id: 1, location:
> public.ST_SetSRID(public.ST_MakePoint(-71.10, 42.32),4326)}) return n
>$$) as (a agtype);
>ERROR:  function public.ST_MakePoint(agtype, agtype) does not exist
>LINE 2: ...1, location: public.ST_SetSRID(public.ST_MakePoint(-71.10,
> 4...
> ^
>HINT:  No function matches the given name and argument types. You might
> need to add explicit type casts.
>
>SELECT * FROM cypher('testgraph', $$
>CREATE (n:Test {id: 1, location:
> public.ST_SetSRID(public.ST_MakePoint(-71.10::float, 42.32::float),4326)})
> return n
>$$) as (a agtype);
>ERROR:  ag function does not exist
>LINE 1: SELECT * FROM cypher('testgraph', $$
>   ^
>DETAIL:  agtype_typecast_float(1)
>
>SELECT * FROM cypher('testgraph', $$
>CREATE (n:Test {id: 1, location:
> public.ST_GeomFromText('POINT(-71.10, 42.32)', 4326)}) return n
>$$) as (a agtype);
>ERROR:  function public.ST_GeomFromText(agtype, agtype) does not exist
>LINE 2: ...E (n:Test {id: 1, location:
> public.ST_GeomFromText('POINT(-7...
> ^
>HINT:  No function matches the given name and argument types. You might
> need to add explicit type casts.
>
>SELECT * FROM cypher('testgraph', $$
>CREATE (n:Test {id: 1, location:
> public.ST_GeomFromText('POINT(-71.10, 42.32)'::text, 4326)}) return n
>$$) as (a agtype);
>ERROR:  typecast 'text' not supported
>LINE 1: SELECT * FROM cypher('testgraph', $$
>   ^
>```
>
>Additional information: the indivial extensions (age, postgis) do work:
>```
>SELECT * FROM cypher('testgraph', $$
>CREA

Re: [DISCUSS] Apache AGE Sub Project - Visualization Tool

[John Gemignani]

My opinion,...

A visualization tool would help to open up AGE to more people which would
grow our community and grow our contributors.

John

On Wed, Jun 16, 2021 at 6:36 PM vongosling  wrote:

> Hi Eya，
>
> I haven't seen the specific code for the project yet, but in recent times,
> I suggest not to propose it as a new sub-project, We could focus on
> building the community. I'd like to know how many users are using our
> project now? Is our project open enough? How many contributors do we
> absorb?
>
>
> Eya Badal  于2021年6月16日周三 上午1:53写道：
>
> > Hello Felix,
> > @all mentors
> >
> > Thank you very much for your prompt reply, I greatly appreciate it. We
> are
> > retooling an existing project to work with incubating Apache AGE. The
> > project is not complete yet and we are hoping to have it as a sub-project
> > of AGE and continue the development of it.
> >
> > Could you please advise if we have to go through the proposal process? If
> > yes please also advise if it is the same process that we have been
> through
> > for AGE - creating a proposal and then calling for a vote in the
> incubator.
> >
> > Thank you very much,
> > Eya Badal
> >
> >
> >
> > On 2021/06/10 21:10:37, Eya Badal  wrote:
> > > Dear Everyone,
> > > @All Mentors
> > >
> > > I hope you are doing great.
> > >
> > > We would like to discuss the possibility of having a sub-project for
> > Apache
> > > AGE. This sub-project is a visualization tool that enables Apache AGE
> > users
> > > to visualize their data.
> > >
> > > This tool is a web-based graph visualization tool that allows you to
> > > visualize a graph. It connects to a Postgres server running the AGE
> graph
> > > database extension. AGViewer has a query editor where you can submit
> SQL
> > > and Cypher (or Hybrid) queries, allowing you to build, modify and query
> > > graphs in AGE. The visualization supports many layout formats such as
> > > COSE-Bilkent, Dagre, and Euler. In addition, there is a table output
> for
> > > displaying non-graph results.
> > >
> > >
> > > Please advise and give us your feedback.
> > >
> > > Thank you very much,
> > > Eya Badal
> > >
> >
>
>
> --
> Best Regards :-)
>

Re: [VOTE] Release Apache AGE (incubating) version 0.5.0

[John Gemignani]

+1

On Sat, Jul 24, 2021 at 9:21 PM Felix Cheung 
wrote:

> +1
>
> Though it will be great to fix soon:
>
>
>   *incubating in name
>
> - signature and hash fine
> - DISCLAIMER is fine
> - LICENSE and NOTICE are fine
> - No unexpected binary files
>
> - Check: All source files have ASF headers
> about 20 source files for tests do not have the Apache header.
> /drivers/jdbc/lib/src/test/java/org/apache/age/jdbc/
>
> what is the source of this jar?
> /drivers/jdbc/gradle/wrapper/gradle-wrapper.jar
>
> 
> From: Dehowe Feng 
> Sent: Friday, July 23, 2021 10:41:28 AM
> To: dev@age.apache.org 
> Subject: Re: [VOTE] Release Apache AGE (incubating) version 0.5.0
>
> Hey Eya,
>
> I can vouch for what you wrote to be true, and am looking forward to the
> release.
>
> +1
>
> On 2021/07/10 14:32:05, Eya Badal  wrote:
> > Dear Apache Community,
> >
> > Please vote on releasing the following candidate as Apache AGE version
> 0.5.0
> >
> > The vote is open now and until July 13th at 7:32 AM PST and passes if a
> majority +1 votes are cast, with a minimum of 3 +1 votes.
> >
> > [ ] +1 Release this package as Apache AGE 0.5.0
> > [ ] -1 Do not release this package because ...
> >
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > *
> > The git tag to be discussed and voted upon:
> > https://github.com/apache/incubator-age/releases/tag/v0.5.0
> >
> > The git commit hash:
> > commit e36e6d79c2a65259f4b46cd9a3623d69518605a4
> >
> > The release files for 0.5.0, can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/age/0.5.0.rc0%20/
> >
> > The signatures, files, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/age/
> >
> > Signatures used for AGE RCs can be found in this file:
> > https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> >
> > The fingerprint of key to sign release artifacts:
> > FD8B 268F 784A CE10 F201  E63B C063 8775 6375 38D2
> >
> > For information about the contents of this release, see:
> > https://github.com/apache/incubator-age/releases/tag/v0.5.0
> >
> > Thank you for your time in advance.
> >
> > Best regards,
> > Eya Badal
> >
> >
>

Re: [VOTE] Accepting Code Contribution for Visualization tool

[John Gemignani]

+1

On Fri, Jul 30, 2021 at 12:55 PM Dehowe Feng  wrote:

> +1 I support this motion.
>
> On 2021/07/30 18:46:16, Eya Badal  wrote:
> > Dear AGE Community,
> >
> > This is a call for accepting the Code Contribution for AGE Visualization
> tool. The community already discussed the importance and advantages of
> having this visualization tool.
> >
> > The vote will be open for 72 hours.
> > [ ] +1 Accept this contribution
> > [ ] +0 no opinion
> > [ ] -1 do not this contribution because...
> >
> >
> > Thank you for all your time.
> >
> > Best regards,
> > Eya Badal
> >
>

Re: Benchmarking result

[John Gemignani]

Good job!

On Thu, Sep 9, 2021 at 9:11 PM VUONG QUOC Viet  wrote:

> Hi Joe and Muhammad,
>
> I've finished the benchmarking experiments after listening to Muhammad's
> suggestions to improve the process: 1. to create 2 separate repos for
> original code and optimized code and 2. place the create_graph at the
> beginning and drop_graph at the end of each sql file.
>
> The experiments were conducted basically the same way: I calculated the
> total time for running 100, 1000 and 1 sql queries, repeated 20 times
> consecutively, got the average value, and repeated that process 10 times
> more. So in essence, there are totally 200 measurements conducted for
> original and optimized code, each. And I calculated overall average for
> total 200 measurements to get a final number to compare between the
> original and the optimized: So here's the result:
>
> Original code (ms) Optimized code (ms) Difference(ms)
> 100 queries 29.23397 28.786665 0.447305
> 1000 queries 255.391305 250.43654 4.9547650004
> 1 queries 2558.612315 2517.9374 40.674915001
>
> According to the result, the difference in execution time for 100 queries
> is that the optimized code was about 0.45ms faster than the original code.
> For 1000 queries, the optimized code is 4.95ms faster and for 1
> queries, it's 40.67ms faster. These numbers, I think, are reasonable,
> because as we make the number of queries 10 times larger, the difference in
> time also increases around 10 times.
>
> I've attached the detailed statistics report. Please let me know your
> comments and suggestions.
>
> Best regards,
> Viet.
>
>

Re: [DISCUSS] Apache AGE 0.6.0 Release

[John Gemignani]

Looks good to me.

+1

On Fri, Sep 10, 2021 at 9:52 AM Josh Innis  wrote:

> Dear Apache Community,
>
>
>
> We would like to discuss the Apache AGE release 0.6.0. that we have been
> working toward it.
>
>
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
>
>
> Functionalities included and addressed in this release:
>
>
>- Add VLE SRF (Set Returning Function).
>- Fix Vertex, Edge, and Path serialization bug (AGE2-307)
>- Fix CREATE passback bug (AGE2-337).
>- Fix CREATE transaction block bug (AGE2-345).
>- Fix parallel build errors.
>- Fix Travis CI compiler warnings.
>
>
> *
>
> The git tag to be discussed and voted upon:
>
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
>
>
>
> The git commit hash:
>
> commit 3681c90da68353507001db89eb429755d34857f7
>
>
>
> The release files for 0.6.0, can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
>
>
>
> The signatures, files, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/age/
>
>
>
> Signatures used for AGE RCs can be found in this file:
>
> https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
>
>
>
> The fingerprint of key to sign release artifacts:
>
> 2245 1CFA 0521 1612 A4EA  9F05 6EF7 BD28 B870 8B05
>
>
>
> For information about the contents of this release, see:
>
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
>
>
>
>
>
> Please share your thoughts and feedback and let us know if we can call for
> a vote.
>
>
>
> Thank you for your time.
>
>
>
> Best regards,
>
> Josh Innis
>
> We create value for our clients by connecting the world's data.
> Josh Innis Software Engineer
> Core R&D Team
> *P*: (831)278-0327
> 3945 Freedom Circle #260, Santa Clara, CA 95054
> <
> https://www.google.com/maps/place/3945+Freedom+Cir+%23260,+Santa+Clara,+CA+95054/
> >
> bitnine.net
>

Re: Benchmarking result

[John Gemignani]

est is asking whether the before and after numbers could
>> have come from the same code (ie no changes). The results are saying that
>> yes, they could. Statistically the difference in results could (very)
>> easily have come from the same code. There is no significant difference. In
>> other words, you could have used only the before code, ran the test twice,
>> and the difference in results could easily be greater than the difference
>> you have observed in your test.
>>
>> Thanks
>> Joe
>>
>> On Fri, 10 Sept 2021 at 19:57, Joe Fagan  wrote:
>>
>>> Great Josh.
>>> I learnt loads reading your script
>>>
>>> On Fri, 10 Sep 2021 at 18:14, Josh Innis  wrote:
>>>
>>>> Good Job Viet. I made some modifications to the SQL function that you
>>>> made. This may be a way to analyze how long it takes to run the queries in
>>>> a purely postgres way that only calls explain analyze once.
>>>>
>>>> SET search_path TO ag_catalog;
>>>> LOAD 'age';
>>>> SELECT create_graph('test_graph');
>>>>
>>>> CREATE OR REPLACE FUNCTION f_test(ct int, sql text)
>>>> RETURNS VOID
>>>> LANGUAGE plpgsql AS $func$
>>>>DECLARE   i int;
>>>> BEGIN
>>>> FOR i IN 1 .. $1 LOOP
>>>> EXECUTE sql;
>>>> END LOOP;
>>>> END $func$;
>>>>
>>>> EXPLAIN ANALYZE SELECT *
>>>> FROM f_test( 1, $q$
>>>> SELECT * from ag_catalog.cypher('test_graph', $$
>>>> CREATE (a:Person {id: 129, name: 'Brian', title: 'Researcher',
>>>> city: 'Munich'})
>>>> RETURN a
>>>> $$) as (a agtype)
>>>> $q$);
>>>>
>>>> We create value for our clients by connecting the world's data.
>>>> Josh Innis Software Engineer
>>>> Core R&D Team
>>>> *P*: (831)278-0327
>>>> 3945 Freedom Circle #260, Santa Clara, CA 95054
>>>> <https://www.google.com/maps/place/3945+Freedom+Cir+%23260,+Santa+Clara,+CA+95054/>
>>>> bitnine.net
>>>>
>>>>
>>>> On Fri, Sep 10, 2021 at 9:12 AM John Gemignani <
>>>> john.gemign...@bitnine.net> wrote:
>>>>
>>>>> Good job!
>>>>>
>>>>> On Thu, Sep 9, 2021 at 9:11 PM VUONG QUOC Viet 
>>>>> wrote:
>>>>>
>>>>>> Hi Joe and Muhammad,
>>>>>>
>>>>>> I've finished the benchmarking experiments after listening to
>>>>>> Muhammad's suggestions to improve the process: 1. to create 2 separate
>>>>>> repos for original code and optimized code and 2. place the create_graph 
>>>>>> at
>>>>>> the beginning and drop_graph at the end of each sql file.
>>>>>>
>>>>>> The experiments were conducted basically the same way: I calculated
>>>>>> the total time for running 100, 1000 and 1 sql queries, repeated 20
>>>>>> times consecutively, got the average value, and repeated that process 10
>>>>>> times more. So in essence, there are totally 200 measurements conducted 
>>>>>> for
>>>>>> original and optimized code, each. And I calculated overall average for
>>>>>> total 200 measurements to get a final number to compare between the
>>>>>> original and the optimized: So here's the result:
>>>>>>
>>>>>> Original code (ms) Optimized code (ms) Difference(ms)
>>>>>> 100 queries 29.23397 28.786665 0.447305
>>>>>> 1000 queries 255.391305 250.43654 4.9547650004
>>>>>> 1 queries 2558.612315 2517.9374 40.674915001
>>>>>>
>>>>>> According to the result, the difference in execution time for 100
>>>>>> queries is that the optimized code was about 0.45ms faster than the
>>>>>> original code. For 1000 queries, the optimized code is 4.95ms faster and
>>>>>> for 1 queries, it's 40.67ms faster. These numbers, I think, are
>>>>>> reasonable, because as we make the number of queries 10 times larger, the
>>>>>> difference in time also increases around 10 times.
>>>>>>
>>>>>> I've attached the detailed statistics report. Please let me know your
>>>>>> comments and suggestions.
>>>>>>
>>>>>> Best regards,
>>>>>> Viet.
>>>>>>
>>>>>> --
>>>
>>> <http://bitnine.net>
>>>
>>> Joe Fagan
>>>
>>> Community Advocate Director
>>>
>>>
>>>
>>>  M : +44 7788 148772
>>>
>>>
>>>
>>> <https://www.facebook.com/search/top?q=bitnine%20agens>
>>> <http://linkedin.com/company/bitnineglobal> <http://bitnine.net>
>>> <http://age.apache.org>
>>> A Graph Extension for PostgreSQL <http://age.apache.org>In the news: Bitnine
>>> Promoting a First IPO in the Graph Database <https://bwnews.pr/3ds2mUc>
>>>
>>

Re: [VOTE] Release Apache AGE (incubating) version 0.6.0

[John Gemignani]

+1

On Thu, Sep 16, 2021 at 12:21 AM Joe Fagan  wrote:

> +1
>
> On Wed, 15 Sep 2021 at 17:12, Josh Innis  wrote:
>
> > Dear Apache Community,
> >
> >
> > Please vote on releasing the following candidate as Apache AGE version
> > 0.6.0
> >
> >
> > The vote is open now and until September 18th at 10:30 AM PST and passes
> if
> > a majority +1 votes are cast, with a minimum of 3 +1 votes.
> >
> >
> > [ ] +1 Release this package as Apache AGE 0.6.0
> >
> > [ ] -1 Do not release this package because ...
> >
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> >
> > *Functionalities included and addressed in this release:*
> >
> >- Add VLE SRF (Set Returning Function).
> >
> >- Fix Vertex, Edge, and Path serialization bug (AGE2-307)
> >
> >- Fix CREATE passback bug (AGE2-337).
> >
> >- Fix CREATE transaction block bug (AGE2-345).
> >
> >- Fix parallel build errors.
> >
> >- Fix Travis CI compiler warnings.
> >
> >
> >
> >
> >
> > *
> >
> >
> >
> > *The git tag to be discussed and voted upon:*
> >
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> >
> >
> > *The git commit hash:*
> >
> > commit 3681c90da68353507001db89eb429755d34857f7
> >
> >
> >
> > *The release files for 0.6.0, can be found at:*
> >
> > https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
> >
> >
> >
> > *The signatures, files, etc. can be found at:*
> >
> > https://dist.apache.org/repos/dist/dev/incubator/age/
> >
> >
> >
> > *Signatures used for AGE RCs can be found in this file:*
> >
> > https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> >
> >
> >
> > *The fingerprint of key to sign release artifacts:*
> >
> > 2245 1CFA 0521 1612 A4EA  9F05 6EF7 BD28 B870 8B05
> >
> >
> >
> > *For information about the contents of this release, see:*
> >
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> >
> >
> > Thank you for your time.
> >
> >
> >
> > Best regards,
> >
> > Josh Innis
> > We create value for our clients by connecting the world's data.
> > Josh Innis Software Engineer
> > Core R&D Team
> > *P*: (831)278-0327
> > 3945 Freedom Circle #260, Santa Clara, CA 95054
> > <
> https://www.google.com/maps/search/3945+Freedom+Circle+%23260,+Santa+Clara,+CA+95054?entry=gmail&source=g
> >
> > <
> >
> https://www.google.com/maps/place/3945+Freedom+Cir+%23260,+Santa+Clara,+CA+95054/
> > >
> > bitnine.net
> >
> --
>
> 
>
> Joe Fagan
>
> Community Advocate Director
>
>
>
>  M : +44 7788 148772
>
>
>
> 
>  
> 
> A Graph Extension for PostgreSQL In the news:
> Bitnine
> Promoting a First IPO in the Graph Database 
>

Re: [VOTE] Release Apache AGE (incubating) version 0.6.0

[John Gemignani]

+1

   - Download links are valid.
   - Checksums and PGP signatures are valid.
   - LICENSE, NOTICE and DISCLAIMER files are correct.
   - All files have license headers if necessary.

John

On Sun, Sep 19, 2021 at 4:55 AM Juan Pan  wrote:

> +1, My check list,
>
>
>
> x] Download links are valid.
>
> [x] Checksums and PGP signatures are valid.
>
> [x] LICENSE, NOTICE and DISCLAIMER files are correct.
>
> [x] All files have license headers if necessary.
>
>
>
>
>
>
> Best,
> Trista
>
> --
> Juan Pan(Trista), Apache member, Apache ShardingSphere PMC, Apache brpc
> (Incubator) & Apache AGE (Incubator) mentor
> Twitter, @trista86934690
>
>
>
> On 09/16/2021 00:11，Josh Innis wrote：
> Dear Apache Community,
>
>
> Please vote on releasing the following candidate as Apache AGE version
> 0.6.0
>
>
> The vote is open now and until September 18th at 10:30 AM PST and passes if
> a majority +1 votes are cast, with a minimum of 3 +1 votes.
>
>
> [ ] +1 Release this package as Apache AGE 0.6.0
>
> [ ] -1 Do not release this package because ...
>
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
>
> *Functionalities included and addressed in this release:*
>
> - Add VLE SRF (Set Returning Function).
>
> - Fix Vertex, Edge, and Path serialization bug (AGE2-307)
>
> - Fix CREATE passback bug (AGE2-337).
>
> - Fix CREATE transaction block bug (AGE2-345).
>
> - Fix parallel build errors.
>
> - Fix Travis CI compiler warnings.
>
>
>
>
>
> *
>
>
>
> *The git tag to be discussed and voted upon:*
>
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
>
>
>
> *The git commit hash:*
>
> commit 3681c90da68353507001db89eb429755d34857f7
>
>
>
> *The release files for 0.6.0, can be found at:*
>
> https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
>
>
>
> *The signatures, files, etc. can be found at:*
>
> https://dist.apache.org/repos/dist/dev/incubator/age/
>
>
>
> *Signatures used for AGE RCs can be found in this file:*
>
> https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
>
>
>
> *The fingerprint of key to sign release artifacts:*
>
> 2245 1CFA 0521 1612 A4EA  9F05 6EF7 BD28 B870 8B05
>
>
>
> *For information about the contents of this release, see:*
>
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
>
>
>
> Thank you for your time.
>
>
>
> Best regards,
>
> Josh Innis
> We create value for our clients by connecting the world's data.
> Josh Innis Software Engineer
> Core R&D Team
> *P*: (831)278-0327
> 3945 Freedom Circle #260, Santa Clara, CA 95054
> <
> https://www.google.com/maps/place/3945+Freedom+Cir+%23260,+Santa+Clara,+CA+95054/
> >
> bitnine.net
>

Re: New committer: Andrew Ko

[John Gemignani]

+1

john

On Fri, Oct 8, 2021 at 8:35 AM Josh Innis  wrote:

> +1
> We create value for our clients by connecting the world's data.
> Josh Innis Software Engineer
> Core R&D Team
> *P*: (831)278-0327
> 3945 Freedom Circle #260, Santa Clara, CA 95054
> <
> https://www.google.com/maps/place/3945+Freedom+Cir+%23260,+Santa+Clara,+CA+95054/
> >
> bitnine.net
>
>
> On Thu, Oct 7, 2021 at 5:16 PM Eya Badal  wrote:
>
> > Hello Everyone,
> >
> > The Apache AGE community has invited Andrew Ko(@aysko75) to become a
> > committer and we are pleased to announce that he has accepted.
> >
> >
> > Best regards,
> > Eya Badal Abdisho
> >
> >
> >
>

Re: [GitHub] [incubator-age] deem0n opened a new issue #140: What is the correct way to MATCH vertexes without edges?

[John Gemignani]

It is best not to assume anything about a graph. Did you create a vertex
without an edge to test the command against it?

On Fri, Nov 5, 2021 at 11:15 AM GitBox  wrote:

>
> deem0n opened a new issue #140:
> URL: https://github.com/apache/incubator-age/issues/140
>
>
>I tried
>
>``` sql
>SELECT * FROM cypher('test',
>$$MATCH (f:Engine),(t:Engine)
>WHERE NOT EXISTS((f)-[]->(t))
>RETURN f,t$$) as (f agtype, t agtype);
>```
>
>and it returns nothing. I am sure there are plenty not connected
> vertexes in my DB though.
>
>
> --
> 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 (incubating) Release 0.6.0

[John Gemignani]

+1

On Fri, Nov 12, 2021 at 1:11 PM Nicholas Sorrell  wrote:

> +1
>
> On 2021/11/10 19:58:06 Josh Innis wrote:
> > Dear Apache Community,
> >
> > Please vote on releasing the following candidate as Apache AGE version
> 0.6.0.
> >
> > The vote is open now and until November 13th at 12:00 PM PST and passes
> if
> > a majority +1 votes are cast, with a minimum of 3 +1 votes.
> >
> > [ ] +1 Release this package as Apache AGE 0.6.0
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > *Functionalities included and addressed in this release:*
> > - Add VLE SRF (Set Returning Function).
> > - Fix Vertex, Edge, and Path serialization bug (AGE2-307)
> > - Fix CREATE passback bug (AGE2-337).
> > - Fix CREATE transaction block bug (AGE2-345).
> > - Fix parallel build errors.
> > - Fix Travis CI compiler warnings.
> >
> > *
> > *The git tag to be discussed and voted upon:*
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> > *The git commit hash:*
> > commit 0dfb741276d5177c2f7beb260634bef21e880386
> >
> > *The release files for 0.6.0, can be found at:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
> >
> > *The signatures, files, etc. can be found at:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/
> >
> > *Signatures used for AGE RCs can be found in this file:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> >
> > *The fingerprint of key to sign release artifacts:*
> > 4D57 8595 934A 64F4 8DD9  B39C 7FAD 0CDD C278 09E8
> >
> > *For information about the contents of this release, see:*
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> > Thank you for your time.
> > Josh Innis
> >
> >
>
>

Re: [VOTE] Apache AGE (incubating) Release 0.6.0

[John Gemignani]

+1


 Signature and hash fine
 DISCLAIMER is fine
 LICENSE and NOTICE are fine
 No unexpected binary files
 incubating in name


john

On Thu, Nov 18, 2021 at 3:37 PM Andrew Ko  wrote:

> +1 ... Thank you
>
> 2021년 11월 18일 (목) 오후 3:04, Muhammad Shoaib 님이 작성:
>
> > +1,
> >
> >
> > I confirm that I have checked the following and they look good to the
> best
> > of my knowledge
> >
> >
> >
> >- Signature and hash fine
> >- DISCLAIMER is fine
> >- LICENSE and NOTICE are fine
> >- No unexpected binary files
> >- incubating in name
> >
> >
> > On Thu, Nov 18, 2021, 18:07 Josh Innis  wrote:
> >
> > > Dear Apache Community,
> > >
> > > Please vote on releasing the following candidate as Apache AGE version
> > > 0.6.0.
> > >
> > > The vote is open now and until November 13th at 12:00 PM PST and passes
> > if
> > > a majority +1 votes are cast, with a minimum of 3 +1 votes.
> > >
> > > [ ] +1 Release this package as Apache AGE 0.6.0
> > > [ ] -1 Do not release this package because ...
> > >
> > > To learn more about Apache AGE, please see http://age.apache.org/
> > >
> > > *Functionalities included and addressed in this release:*
> > > - Add VLE SRF (Set Returning Function).
> > > - Fix Vertex, Edge, and Path serialization bug (AGE2-307)
> > > - Fix CREATE passback bug (AGE2-337).
> > > - Fix CREATE transaction block bug (AGE2-345).
> > > - Fix parallel build errors.
> > > - Fix Travis CI compiler warnings.
> > >
> > > *
> > > *The git tag to be discussed and voted upon:*
> > > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> > >
> > > *The git commit hash:*
> > > commit 0dfb741276d5177c2f7beb260634bef21e880386
> > >
> > > *The release files for 0.6.0, can be found at:*
> > > https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
> > >
> > > *The signatures, files, etc. can be found at:*
> > > https://dist.apache.org/repos/dist/dev/incubator/age/
> > >
> > > *Signatures used for AGE RCs can be found in this file:*
> > > https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> > >
> > > *The fingerprint of key to sign release artifacts:*
> > > 4D57 8595 934A 64F4 8DD9  B39C 7FAD 0CDD C278 09E8
> > >
> > > *For information about the contents of this release, see:*
> > > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> > >
> > > Thank you for your time.
> > > Josh Innis
> > >
> >
>

Re: [VOTE] Apache AGE (incubating) Release v0.6.0

[John Gemignani]

+1,

   - Signature and hash - check.
   - DISCLAIMER - check.
   - LICENSE and NOTICE - check.
   - No unexpected binary files - check.
   - incubating in name - check.

John

On Mon, Nov 22, 2021 at 12:51 AM Muhammad Shoaib  wrote:

> +1,
>
>
> I confirm that I have checked the following and they look good to the best
> of my knowledge
>
>
>
>- Signature and hash fine
>- DISCLAIMER is fine
>- LICENSE and NOTICE are fine there is no WIP information there now.
>- No unexpected binary files
>- incubating in name
>
>
> On Sun, Nov 21, 2021 at 10:33 PM Josh Innis  wrote:
>
> > Dear Apache Community,
> >
> > Please vote on releasing the following candidate as Apache AGE version
> > 0.6.0.
> >
> > This release includes the updates to the NOTICE, removing the WIP
> > disclaimer
> > and adding the standard disclaimer, and changing the copyright header in
> > files
> > that are predominately Postgres source code.
> >
> > The vote is open now and until November 24th at 2:30 PM PST and passes if
> > a majority +1 votes are cast, with a minimum of 3 +1 votes.
> >
> > [ ] +1 Release this package as Apache AGE 0.6.0
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > *Functionalities included and addressed in this release:*
> > - Add VLE SRF (Set Returning Function).
> > - Fix Vertex, Edge, and Path serialization bug (AGE2-307)
> > - Fix CREATE passback bug (AGE2-337).
> > - Fix CREATE transaction block bug (AGE2-345).
> > - Fix parallel build errors.
> > - Fix Travis CI compiler warnings.
> >
> > *
> > *The git tag to be discussed and voted upon:*
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> > *The git commit hash:*
> > commit 9786fc32d52c577cf67e9e89409246b9e7a3a063
> >
> > *The release files for 0.6.0, can be found at:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
> >
> > *The signatures, files, etc. can be found at:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/
> >
> > *Signatures used for AGE RCs can be found in this file:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> >
> > *The fingerprint of key to sign release artifacts:*
> > 4D57 8595 934A 64F4 8DD9  B39C 7FAD 0CDD C278 09E8
> >
> > *For information about the contents of this release, see:*
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> > Thank you for your time.
> > Josh Innis
> >
>
>
> --
>
> * Muhammad Shoaib, PhD*
>
> * Senior Research Engineer *
>
> *P* : +82-70-4800-3517   *F* : +82-70-8677-2552
> 401 Yangcheon-ro A/1201, Gangseo-gu, Seoul, 07528, Korea
>

Re: Apache AGE (Incubating) - Community Graduation Vote

[John Gemignani]

I completely agree with all of Eya and Josh's points.

Especially, now that we have v0.6.0 out (which took a lot of extra attention 
and cleaned up a lot of pending issues) and with the upcoming release of 
v0.7.0. The latter release will add a significant amount of new functionality. 
This makes me confident that the project will be able to move forward a lot 
more smoothly.

+1

John

On 2021/12/02 01:39:41 Josh Innis wrote:
> This project has seen incredible growth from when it was originally donated 
> to Apache. The community continues to grow as more people see the 
> opportunities in what the project could be. Now that we are nearly done with 
> our original goal of implementing the openCypher specification in Postgres as 
> an extension, we can now begin to pursue some of these powerful features that 
> the community is requesting in the Github repository. The team is continuing 
> to grow at an accelerated pace, with most of the new committers being 
> accepted in the last six months. I personally think the future of AGE is 
> bright, especially with all the new features that will be coming out in 
> v0.7.0.
> 
> On 2021/12/01 02:42:22 Eya Badal wrote:
> > Thank you mentors for your valuable feedback. The feedback is addressed 
> > below. 
> > 
> > Regarding GitHub issues and pull requests: 
> >   It is true that in the earlier months we were sluggish in responding to 
> > and closing out issues. In 
> >   April we created SLA to categorise (label), assign, and respond to 
> > issues. Since April, 95% are 
> >   responded within 72 hours (80% of issues are responded to within 24 hrs). 
> > In the last month we 
> >   have closed 8 issues across the project. Regarding pull requests we are 
> > behind our internal 
> >   SLA but have addressed that in the last 48 hrs.
> > 
> > Regarding committer and contributor diversity:
> >   The committers and contributors act on their own initiative without 
> > representing a corporation 
> >   or organization. Core contributors are indeed employees of a single 
> > company (Bitnine Global, 
> >   the project donator) who has interest in the success of AGE but there are 
> > many entirely 
> >   independent contributors and committers. Contributions span more than 20 
> > countries across 
> >   the globe including Australia, Belarus, Belgium, China, France, Germany, 
> > Ireland, Israel, Italy, 
> >   Luxembourg, The Netherlands, Nigeria, The Philippines, Russia, South 
> > Korea, Thailand, UK, 
> >   Ukraine, USA and Vietnam.
> > 
> > Regarding the breakdown of the PPMC membership on affiliation (companies) 
> > and PPMC growth:
> > 
> >  The PPMC representation, excluding mentors is as follows:
> > 
> >   Bitnine Global: Eya Badal, Josh Innis, John Gemignani, Dehowe Feng(in 
> > voting process).  
> >   Liberation Data: Jasper Blues 
> >   Immuta: Mason Sharp
> > 
> >  The project has added five new committers taking the total to 10 
> > (excluding mentors).
> > 
> >   Bitnine Global: Dehowe Feng
> >   Kroger: Nick Sorrell
> >   Ghent University: Pieterjan De Potter
> >   Agedb: Andrew Ko, Alex Kwak
> > 
> > RE CS10 “The project maintains a public list of its contributors who have 
> > decision power”:
> > We now have the list of community members (committer and PPMC) at 
> > age.apache.org
> > 
> > Regarding how incubator-age-viewer is released:
> >   Age-viewer has been released 8 times. The age-viewer developers are 
> > looking to release in the 
> >   Apache way soon. The age team is coaching the age-viewer developers to 
> > encourage future 
> >   releases to comply with Apache guiding principles.
> > 
> > The documentation link at incubator.apache.org/projects/age.html is 
> > corrected.
> > 
> > Regarding project name search and approval:
> >   We have completed name search and approval. PPMC is actively checking 
> > Apache AGE brand 
> >   use.
> > 
> > The licensing issue regarding 0.6.0 has been resolved. We’re happy to 
> > announce Apache AGE 0.6.0 is officially out today. 
> > 
> > Thank you for your feedback and recognition that after 6 releases including 
> > 4 Apache releases, we have demonstrated that this community is able to run 
> > independently outside incubation.
> > 
> > We look forward to a positive vote on graduation to a Top Level Project.
> > 
> > Thank you
> > Eya
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >

Re: [VOTE] Release Apache AGE Viewer (incubating) 1.0.0-rc0

[John Gemignani]

+1

john

On Wed, Dec 22, 2021 at 4:58 PM Alex Kwak  wrote:

> Dear Apache AGE Community,
>
> This is an official vote for the Apache AGE Viewer release v1.0.0-rc0 that
> we have been working toward it.
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
> Functionalities included and addressed in this release:
> - Graph visualization for AGE.
> - Extends edge and vertex point by point.
>
>
> The vote is open now and until December 25th at 5:00 PM PST and passes if
> a majority +1 votes are cast, with a minimum of 3 +1 votes.
>
> [ ] +1 Release this package as Apache AGE 0.6.0
> [ ] 0 I won't get in the way
> [ ] -1 Do not release this package because ...
>
>
> The git tag to be discussed and voted upon
> https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0
>
> The git commit hash:
> commit 2c55b2302875449565674aa039517734cf338031
>
> The release files, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/age/viewer/apache-age-viewer-1.0.0-incubating-rc0/
>
> The SHA512 Checksum for these artifacts is:
>
> 8fa45254bba973678243a78321869aaf88c746b55168d4401931c5d6e87192c80d581d97e927c8b87098aaacba8d6f77bf1ca225e864c49117f5cb1887c699d0
>
> Release artifacts are signed with the following key:
> https://downloads.apache.org/incubator/age/KEYS
>
> The fingerprint of key to sign release artifacts:
> 0E7F 408D 8C6A 1952 329C B379 D471 FDCE 5F5C 5B82
>
> For more information about the contents of this release, see:
> https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0
>
>
>
> Best regards,
> Alex Kwak
>

Re: [DISCUSS] Release Apache AGE Viewer (incubating) 1.0.0-rc0

[John Gemignani]

+1

john

On Mon, Dec 20, 2021 at 2:33 AM Muhammad Shoaib 
wrote:

> +1
>
> It seems that Apache AGE is now in shape to go into major release. It has
> implemented near to complete cypher implementation, have removed most of
> the bugs identified by the customers, and performed the scalability
> testing. Currently the team is working on exploring the options to add more
> functionality.
>
> Software development is a continuous process and I believe that we will see
> more good experiences in the future as well.
>
> On Mon, Dec 20, 2021 at 3:37 AM Alex Kwak  wrote:
>
> > We now close this thread as there has been no objections and move will
> > forward to the
> > [VOTE] thread.
> > Thank you,
> >
> > Alex Kwak
> >
> > On 2021/12/17 02:30:47 Alex Kwak wrote:
> > > Dear Apache AGE Community,
> > > We would like to discuss the Apache AGE Viewer release v1.0.0-rc0 that
> > we have been working toward it.
> > > To learn more about Apache AGE, please see http://age.apache.org/
> > >
> > > Functionalities included and addressed in this release:
> > > - Graph visualization for AGE.
> > > - Extends edge and vertex point by point.
> > >
> > > The git tag to be discussed and voted upon
> > > https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0
> > >
> > > The git commit hash:
> > > commit 2c55b2302875449565674aa039517734cf338031
> > >
> > > The release files, including signatures, digests, etc. can be found at:
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/age/viewer/apache-age-viewer-1.0.0-incubating-rc0/
> > >
> > > The SHA512 Checksum for these artifacts is:
> > >
> >
> 8fa45254bba973678243a78321869aaf88c746b55168d4401931c5d6e87192c80d581d97e927c8b87098aaacba8d6f77bf1ca225e864c49117f5cb1887c699d0
> > >
> > > Release artifacts are signed with the following key:
> > > https://downloads.apache.org/incubator/age/KEYS
> > >
> > > The fingerprint of key to sign release artifacts:
> > > 0E7F 408D 8C6A 1952 329C  B379 D471 FDCE 5F5C 5B82
> > >
> > > For more information about the contents of this release, see:
> > > https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0
> > >
> > > The thread is open for 72 hours and please let us know if you have any
> > questions.
> > >
> > > Best regards,
> > > Alex Kwak
> > >
> >
>
>
> --
> Muhammad *Shoaib, PhD*
> Data Scientist, Bioinformatician and AI Engineer
> PhD (Biomedical Engineering)
> Email: muhemmed.sho...@gmail.com
>

Re: [DISCUSS] Committer Requirements

[John Gemignani]

How about -

There should be a minimum of 1 month since the start of activity from said 
commiter.
There should be a minimum of 5 commits.

John

On 2022/01/06 20:14:31 Eya Badal wrote:
> Hello everyone, 
> 
> As recommended by our mentors I would like to get community feedback and 
> thoughts on committer requirements. I think we should discuss this and 
> document the requirements.
> 
> Best regards, 
> Eya 
> 

Re: [DISCUSS] Apache AGE 0.7.0 Release

[John Gemignani]

+1

John

On Tue, Jan 18, 2022 at 8:57 AM Joe Fagan  wrote:

> +1
>
> On 2022/01/14 02:18:03 Dehowe F wrote:
> > Dear Apache Community,
> >
> > We would like to discuss the Apache AGE release 0.7.0. that we have been
> > working toward it.
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > Functionalities included and addressed in this release:
> >
> > *Add VLE core to the MATCH clause.
> > *Added support for various list functions
> > *range()
> > *relationships()
> > *keys()
> > *label()
> > *nodes()
> > *reverse()
> > *Various bug fixes
> >
> > *
> >
> > The git tag to be discussed and voted upon:
> > https://github.com/apache/incubator-age/releases/tag/v.0.7.0-rc0
> >
> >
> > The git commit hash: commit d0175f4a2fb03f28c356ea43da3bd48a47f5ef42
> >
> >
> >  The release files for 0.7.0, can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/age/0.7.0.rc0/
> >
> >
> >  Signatures used for AGE RCs can be found in this file:
> > https://downloads.apache.org/incubator/age/KEYS
> >
> >
> >
> > The fingerprint of key to sign release artifacts:
> >
> > 847F A9F0 CB17 2A51 DEC9  D0F3 8285 D595 875F 13B1
> >
> >
> >
> > For information about the contents of this release, see:
> > https://github.com/apache/incubator-age/releases/tag/v.0.7.0-rc0
> >
> >
> > Please share your thoughts and feedback and let us know if we can call
> for
> > a vote.
> >
> > Thank you for your time.
> >
> > Best,
> >
> > Dehowe Feng
> >
>

Re: [VOTE] Apache AGE 0.7.0 Release

[John Gemignani]

+1

John

On Tue, Jan 18, 2022 at 3:42 PM Young Seung Andrew Ko <
youngseung.and...@gmail.com> wrote:

> +1
> Finally VLE :)
> Nice work guys !
>
> On Wed, Jan 19, 2022 at 8:38 AM Dehowe Feng 
> wrote:
>
> > Dear Apache Community,
> >
> > This is an official vote for the Apache AGE release 0.7.0. that we have
> > been
> > working toward it.
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > Functionalities included and addressed in this release:
> >
> > *Add VLE core to the MATCH clause.
> > *Added support for various list functions
> > *range()
> > *relationships()
> > *keys()
> > *label()
> > *nodes()
> > *reverse()
> > *Various bug fixes
> >
> > *
> >
> > The git tag to be discussed and voted upon:
> > https://github.com/apache/incubator-age/releases/tag/v.0.7.0-rc0
> >
> > The git commit hash: commit d0175f4a2fb03f28c356ea43da3bd48a47f5ef42
> >
> > The release files for 0.7.0, can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/age/0.7.0.rc0/
> >
> > Signatures used for AGE RCs can be found in this file:
> > https://downloads.apache.org/incubator/age/KEYS
> >
> > The fingerprint of key to sign release artifacts:
> > 847F A9F0 CB17 2A51 DEC9 D0F3 8285 D595 875F 13B1
> >
> > For information about the contents of this release, see:
> > https://github.com/apache/incubator-age/releases/tag/v.0.7.0-rc0
> >
> >
> >
> > Please vote:
> >
> >
> > [ ] +1 Release this package as Apache AGE 0.7.0
> > [ ] 0 I won't get in the way
> > [ ] -1 Do not release this package because ...
> >
> >
> > This vote will be open for 72 hours.
> >
> > Thank you for your time.
> >
> >
> > Best,
> > Dehowe Feng
> >
>

Re: [VOTE] Apache AGE 0.7.0 Release

[John Gemignani]

Hi Juan,

Not necessarily the file names but the contents of those files.


John

On Sun, Jan 23, 2022, 3:31 AM Juan Pan  wrote:

> Hi Josh,
>
>
> I see. I just want to double check the following files all comes from
> PostgreSQL, not from others, right?
>
>
>
>
>
>
> --
> Juan Pan(Trista), Twitter: @tristaZero
>
>
> On 01/23/2022 11:43，Josh Innis wrote：
> Hi Trista,
>
> From the discussion from the last release the team reviewed the project and
> determined that there was a large enough amount of the Postgres code base
> in those files to warrant  the Postgres header instead of the Apache
> header.
>
> On Sat, Jan 22, 2022 at 6:35 AM Juan Pan  wrote:
>
> Hello,
>
>
>
> [x] Download links are valid.
>
> [x] Checksums and PGP signatures are valid.
>
> [x] LICENSE, NOTICE and DISCLAIMER files exist.
>
> [ ] All files have license headers if necessary.
>
>
>
>
> The following files with source coding are all from Postgres project?
> 
> apache-age-0.7.0-incubating/.gitignore
> apache-age-0.7.0-incubating/.travis.yml
> apache-age-0.7.0-incubating/CONTRIBUTING.md
> apache-age-0.7.0-incubating/README.md
> apache-age-0.7.0-incubating/doc/.gitignore
> apache-age-0.7.0-incubating/drivers/golang/README.md
> apache-age-0.7.0-incubating/drivers/golang/TYPES.md
> apache-age-0.7.0-incubating/drivers/golang/parser/README.md
> apache-age-0.7.0-incubating/drivers/nodejs/README.md
> apache-age-0.7.0-incubating/drivers/python/README.md
> apache-age-0.7.0-incubating/drivers/python/antlr/README.md
>
> apache-age-0.7.0-incubating/drivers/python/samples/apache-age-agtypes.ipynb
> apache-age-0.7.0-incubating/drivers/python/samples/apache-age-basic.ipynb
> apache-age-0.7.0-incubating/drivers/python/samples/apache-age-note.ipynb
> apache-age-0.7.0-incubating/regress/.gitignore
> apache-age-0.7.0-incubating/src/backend/executor/cypher_utils.c
> apache-age-0.7.0-incubating/src/backend/parser/.gitignore
> apache-age-0.7.0-incubating/src/backend/parser/cypher_clause.c
> apache-age-0.7.0-incubating/src/backend/parser/cypher_expr.c
> apache-age-0.7.0-incubating/src/backend/parser/cypher_item.c
> apache-age-0.7.0-incubating/src/backend/parser/cypher_keywords.c
> apache-age-0.7.0-incubating/src/backend/parser/cypher_parse_agg.c
> apache-age-0.7.0-incubating/src/backend/parser/cypher_parse_node.c
> apache-age-0.7.0-incubating/src/backend/utils/ag_func.c
> apache-age-0.7.0-incubating/src/backend/utils/adt/ag_float8_supp.c
> apache-age-0.7.0-incubating/src/backend/utils/adt/agtype.c
> apache-age-0.7.0-incubating/src/backend/utils/adt/agtype_parser.c
> apache-age-0.7.0-incubating/src/backend/utils/adt/agtype_util.c
> apache-age-0.7.0-incubating/src/include/parser/.gitignore
> apache-age-0.7.0-incubating/src/include/parser/ag_scanner.h
> apache-age-0.7.0-incubating/src/include/parser/cypher_expr.h
> apache-age-0.7.0-incubating/src/include/parser/cypher_parse_agg.h
> apache-age-0.7.0-incubating/src/include/utils/ag_float8_supp.h
> apache-age-0.7.0-incubating/src/include/utils/ag_func.h
> apache-age-0.7.0-incubating/src/include/utils/agtype.h
> apache-age-0.7.0-incubating/src/include/utils/agtype_parser.h
>
>
>
>
>
> --
> Juan Pan(Trista), Twitter: @tristaZero
>
>
> On 01/19/2022 07:37，Dehowe Feng wrote：
> Dear Apache Community,
>
> This is an official vote for the Apache AGE release 0.7.0. that we have
> been
> working toward it.
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
> Functionalities included and addressed in this release:
>
> *Add VLE core to the MATCH clause.
> *Added support for various list functions
> *range()
> *relationships()
> *keys()
> *label()
> *nodes()
> *reverse()
> *Various bug fixes
>
> *
>
> The git tag to be discussed and voted upon:
> https://github.com/apache/incubator-age/releases/tag/v.0.7.0-rc0
>
> The git commit hash: commit d0175f4a2fb03f28c356ea43da3bd48a47f5ef42
>
> The release files for 0.7.0, can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/age/0.7.0.rc0/
>
> Signatures used for AGE RCs can be found in this file:
> https://downloads.apache.org/incubator/age/KEYS
>
> The fingerprint of key to sign release artifacts:
> 847F A9F0 CB17 2A51 DEC9 D0F3 8285 D595 875F 13B1
>
> For information about the contents of this release, see:
> https://github.com/apache/incubator-age/releases/tag/v.0.7.0-rc0
>
>
>
> Please vote:
>
>
> [ ] +1 Release this package as Apache AGE 0.7.0
> [ ] 0 I won't get in the way
> [ ] -1 Do not release this package because ...
>
>
> This vote will be open for 72 hours.
>
> Thank you for your time.
>
>
> Best,
> Dehowe Feng
>
>

Re: [VOTE] Apache AGE 0.7.0 Release

[John Gemignani]

vongosling -

"Do we have a plan to transfer all pg files to an external directory?"

Could you please clarify what *you *mean by an external directory? Is it
another directory in our repository or not in our repository at all?

Additionally, is this a requirement? Per Justin, or at least from my
understanding of what Justin stated and please correct me if I am wrong, it
is desirable to keep the code in another directory in the repository but,
it is not necessary.

What we have been working on is slowly migrating code out of these files
and trying to segregate our new code. However, this is a slow process as
there are a lot of interdependencies. Additionally, as the core code for
AGE is heavily based off of JSONB, some of our code cannot be fully
separated or segregated.

So, to answer your question, yes, we have been working on a plan to
separate and segregate our code. But, to an external directory, that
depends on what you mean. There will always be files with a mix of our code
and PG code due to the nature of this extension - which has been stated
before.

John

On Sun, Jan 23, 2022 at 7:14 PM vongosling  wrote:

> Do we have a plan to transfer all pg files to an external directory? I have
> seen we have many files like we have pointed.
>
> Josh Innis  于2022年1月24日周一 02:03写道：
>
> > There is some code that the AGE team wrote that is in those files, but no
> > third party code is in those files.
> >
> > On Sun, Jan 23, 2022 at 8:46 AM John Gemignani 
> > wrote:
> >
> > > Hi Juan,
> > >
> > > Not necessarily the file names but the contents of those files.
> > >
> > >
> > > John
> > >
> > > On Sun, Jan 23, 2022, 3:31 AM Juan Pan  wrote:
> > >
> > > > Hi Josh,
> > > >
> > > >
> > > > I see. I just want to double check the following files all comes from
> > > > PostgreSQL, not from others, right?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
> --
> > > > Juan Pan(Trista), Twitter: @tristaZero
> > > >
> > > >
> > > > On 01/23/2022 11:43，Josh Innis wrote：
> > > > Hi Trista,
> > > >
> > > > From the discussion from the last release the team reviewed the
> project
> > > and
> > > > determined that there was a large enough amount of the Postgres code
> > base
> > > > in those files to warrant  the Postgres header instead of the Apache
> > > > header.
> > > >
> > > > On Sat, Jan 22, 2022 at 6:35 AM Juan Pan  wrote:
> > > >
> > > > Hello,
> > > >
> > > >
> > > >
> > > > [x] Download links are valid.
> > > >
> > > > [x] Checksums and PGP signatures are valid.
> > > >
> > > > [x] LICENSE, NOTICE and DISCLAIMER files exist.
> > > >
> > > > [ ] All files have license headers if necessary.
> > > >
> > > >
> > > >
> > > >
> > > > The following files with source coding are all from Postgres project?
> > > > 
> > > > apache-age-0.7.0-incubating/.gitignore
> > > > apache-age-0.7.0-incubating/.travis.yml
> > > > apache-age-0.7.0-incubating/CONTRIBUTING.md
> > > > apache-age-0.7.0-incubating/README.md
> > > > apache-age-0.7.0-incubating/doc/.gitignore
> > > > apache-age-0.7.0-incubating/drivers/golang/README.md
> > > > apache-age-0.7.0-incubating/drivers/golang/TYPES.md
> > > > apache-age-0.7.0-incubating/drivers/golang/parser/README.md
> > > > apache-age-0.7.0-incubating/drivers/nodejs/README.md
> > > > apache-age-0.7.0-incubating/drivers/python/README.md
> > > > apache-age-0.7.0-incubating/drivers/python/antlr/README.md
> > > >
> > > >
> > >
> >
> apache-age-0.7.0-incubating/drivers/python/samples/apache-age-agtypes.ipynb
> > > >
> > apache-age-0.7.0-incubating/drivers/python/samples/apache-age-basic.ipynb
> > > >
> > apache-age-0.7.0-incubating/drivers/python/samples/apache-age-note.ipynb
> > > > apache-age-0.7.0-incubating/regress/.gitignore
> > > > apache-age-0.7.0-incubating/src/backend/executor/cypher_utils.c
> > > > apache-age-0.7.0-incubating/src/backend/parser/.gitignore
> > > > apache-age-0.7.0-incubating/src/backend/parser/cypher_clause.c
> > > > apache-age-0.7.0-incubating/

Re: [DISCUSS] Ambiguity in the MERGE Specification

[John Gemignani]

I don't think having a default direction applied for a non-directed edge is
a good idea; there wouldn't be a way to tell these edges apart later on.

I think it might be a better idea to just support non-directed edges.

John

On Mon, Jan 24, 2022 at 3:35 PM Jasper Blues 
wrote:

> Hi All,
>
> The quirk behind that CYPHER comes from Neo4j’s property graph model:
>
> All edges have a direction
> When direction is not relevant it can be ignored.
>
> This works will for read queries, for merge it is slightly quirky, however
> I believe the specification is reasonable:
>
> If we MERGE with an edge that does not specify a direction, it is because
> direction is irrelevant, just as in the read scenario
> Given this, the result is to intentionally assign a random direction
>
> I think the above behavior is OK. It would also be reasonable to pick a
> consistent direction, however this leads to potential compatibility issues:
>
> Users might start depending on an ‘implied’ direction
> When porting to/from Neo4j (interoperability is a strength - being able to
> attract users to the platform and have the users be confident they can
> migrate if ever they want aids adoption).
>
> So my 2c: Do what Neo4j does, and make it random, because the intention is
> “direction doesn’t matter”. However choosing a direction would also be ok.
> I don’t think rejecting the MERGE is great, because it differs from how
> other CYPHER graph DBs behave.
>
>
>
> > On Jan 25, 2022, at 7:06 AM, Josh Innis  wrote:
> >
> > Hi All,
> >
> > The openCypher specification for MERGE has an ambiguous specification on
> > the subject of undirected relationships.
> >
> > Per the document on page 119 in the section titled "Merge on an
> undirected
> > relationship":
> >
> > MERGE can also be used with an undirected relationship. When it needs to
> > create a new one, it will pick a direction.
> >
> > Query:
> > MATCH (charlie:Person {name: 'Charlie Sheen'}), (oliver:Person {name:
> > 'Oliver Stone'})
> > MERGE (charlie)-[r:KNOWS]-(oliver)
> > RETURN r
> >
> > As 'Charlie Sheen' and 'Oliver Stone' do not know each other, this MERGE
> > query will create a KNOWS relationship between them. The direction of the
> > created relationship is arbitrary.
> >
> > We should probably clarify that. Having MERGE use undirected edges to
> find
> > paths is a potentially useful feature, but "The direction of the created
> > relationship is arbitrary" is unclear and should be clarified.
> >
> > I believe there are two potential ways to solve this issue:
> > Option 1: Do not let MERGE use undirected edges.
> > Option 2: Have a default direction that AGE will use every time MERGE
> > creates an edge where direction is not specified.
> >
> > Personally, I lean towards proposal 2 with the default direction being a
> > right directed edge. The other way limits functionality, and as long as
> the
> > decision we make is expressed well in the documentation, I don't believe
> it
> > is too confusing.
> >
> > Please let us know what you think.
>
>

Re: [DISCUSS] Ambiguity in the MERGE Specification

[John Gemignani]

I'm not sure of the consequences of storing both directions (like multiple
edges returned from a match when there is really only one) for just one
non-directional edge. Although, a non-directional edge is technically,
bidirectional.

The ideal way would be to support a non-directional edge alongside the
other directions.

Picking a default direction could have side-effects elsewhere that we may
not be aware of, or aware of yet. So, we should thoroughly flesh those out.

Additionally, I don't think that we should just support anything, that may
be ill advised, just because Neo4j does. I think that if we vear off too
far, it will complicate using well defined algorithms for graphs.

My thoughts.

John


On Mon, Jan 24, 2022 at 5:37 PM Josh Innis  wrote:

> Support in what way, have two edges, one for each direction or what Jasper
> and Nick are suggesting?
>
> On Mon, Jan 24, 2022 at 5:35 PM John Gemignani  >
> wrote:
>
> > I don't think having a default direction applied for a non-directed edge
> is
> > a good idea; there wouldn't be a way to tell these edges apart later on.
> >
> > I think it might be a better idea to just support non-directed edges.
> >
> > John
> >
> > On Mon, Jan 24, 2022 at 3:35 PM Jasper Blues  >
> > wrote:
> >
> > > Hi All,
> > >
> > > The quirk behind that CYPHER comes from Neo4j’s property graph model:
> > >
> > > All edges have a direction
> > > When direction is not relevant it can be ignored.
> > >
> > > This works will for read queries, for merge it is slightly quirky,
> > however
> > > I believe the specification is reasonable:
> > >
> > > If we MERGE with an edge that does not specify a direction, it is
> because
> > > direction is irrelevant, just as in the read scenario
> > > Given this, the result is to intentionally assign a random direction
> > >
> > > I think the above behavior is OK. It would also be reasonable to pick a
> > > consistent direction, however this leads to potential compatibility
> > issues:
> > >
> > > Users might start depending on an ‘implied’ direction
> > > When porting to/from Neo4j (interoperability is a strength - being able
> > to
> > > attract users to the platform and have the users be confident they can
> > > migrate if ever they want aids adoption).
> > >
> > > So my 2c: Do what Neo4j does, and make it random, because the intention
> > is
> > > “direction doesn’t matter”. However choosing a direction would also be
> > ok.
> > > I don’t think rejecting the MERGE is great, because it differs from how
> > > other CYPHER graph DBs behave.
> > >
> > >
> > >
> > > > On Jan 25, 2022, at 7:06 AM, Josh Innis 
> > wrote:
> > > >
> > > > Hi All,
> > > >
> > > > The openCypher specification for MERGE has an ambiguous specification
> > on
> > > > the subject of undirected relationships.
> > > >
> > > > Per the document on page 119 in the section titled "Merge on an
> > > undirected
> > > > relationship":
> > > >
> > > > MERGE can also be used with an undirected relationship. When it needs
> > to
> > > > create a new one, it will pick a direction.
> > > >
> > > > Query:
> > > > MATCH (charlie:Person {name: 'Charlie Sheen'}), (oliver:Person {name:
> > > > 'Oliver Stone'})
> > > > MERGE (charlie)-[r:KNOWS]-(oliver)
> > > > RETURN r
> > > >
> > > > As 'Charlie Sheen' and 'Oliver Stone' do not know each other, this
> > MERGE
> > > > query will create a KNOWS relationship between them. The direction of
> > the
> > > > created relationship is arbitrary.
> > > >
> > > > We should probably clarify that. Having MERGE use undirected edges to
> > > find
> > > > paths is a potentially useful feature, but "The direction of the
> > created
> > > > relationship is arbitrary" is unclear and should be clarified.
> > > >
> > > > I believe there are two potential ways to solve this issue:
> > > > Option 1: Do not let MERGE use undirected edges.
> > > > Option 2: Have a default direction that AGE will use every time MERGE
> > > > creates an edge where direction is not specified.
> > > >
> > > > Personally, I lean towards proposal 2 with the default direction
> being
> > a
> > > > right directed edge. The other way limits functionality, and as long
> as
> > > the
> > > > decision we make is expressed well in the documentation, I don't
> > believe
> > > it
> > > > is too confusing.
> > > >
> > > > Please let us know what you think.
> > >
> > >
> >
>

Re: [VOTE] Release Apache AGE Viewer (incubating) 1.0.0-rc1

[John Gemignani]

I will give this a +1.

However, I haven't seen any traction on this thread for a while. Should this be 
closed and then reopened? Or, should we continue to try to get enough votes? Or?

Mentors, could you please give your input?

Thanks!

John

On 2022/01/10 04:38:32 Alex Kwak wrote:
> Sorry, All.
> 
> It was a mistake to close it. We will continue voting.
> 
> On 2022/01/10 02:37:21 Alex Kwak wrote:
> > Hello Community,
> > 
> > We are closing the vote. Results will be sent shortly.
> > 
> > On 2022/01/06 02:20:46 Alex Kwak wrote:
> > > Dear Apache AGE Community,
> > > 
> > > This is an official vote for the Apache AGE Viewer release v1.0.0-rc1 
> > > that we have been working toward it.
> > > 
> > > To learn more about Apache AGE, please see http://age.apache.org/
> > > 
> > > Functionalities included and addressed in this release:
> > > - Graph visualization for AGE.
> > > - Extends edge and vertex point by point.
> > > 
> > > 
> > > The vote is open now and until January 8th at 6:00 PM PST and passes if a 
> > > majority +1 votes are cast, with a minimum of 3 +1 votes.
> > > 
> > > [ ] +1 Release this package as Apache AGE Viewer v1.0.0
> > > [ ] 0 I won't get in the way
> > > [ ] -1 Do not release this package because ...
> > > 
> > > 
> > > The git tag to be discussed and voted upon
> > > https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0-rc1
> > > 
> > > The git commit hash:
> > > commit 2b7fe6018d9da5ce10cf206cc6e879577a3d8051
> > > 
> > > The release files, including signatures, digests, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/age/viewer/apache-age-viewer-1.0.0-incubating-rc1/
> > > 
> > > The SHA512 Checksum for these artifacts is:
> > > dce65e48c222d4bd0b1be8f571495b50217fcf60d82599702f3e42b36cc5afb0045b798099f981c0db13ed76a94157f9f6dadeb5940a20756bb5c2f6fb6b8009
> > > 
> > > Release artifacts are signed with the following key:
> > > https://downloads.apache.org/incubator/age/KEYS
> > > 
> > > The fingerprint of key to sign release artifacts:
> > > 0E7F 408D 8C6A 1952 329C B379 D471 FDCE 5F5C 5B82
> > > 
> > > For more information about the contents of this release, see:
> > > https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0-rc1
> > > 
> > > 
> > > 
> > > Best regards,
> > > Alex Kwak
> > > 
> > 
> 

Re: [VOTE] Apache AGE Viewer 1.0.0 (rc2) Release

[John Gemignani]

+1

On Mon, Feb 28, 2022 at 8:35 AM Josh Innis  wrote:

> +1
>
> On Sat, Feb 26, 2022 at 9:20 AM Eya Badal  wrote:
>
> > Looks good to me.
> > +1
> >
> > Checked the following:
> > *Download links valid.
> > *Checksums, PGP signatures valid.
> > *LICENSE, NOTICE, and DISCLAIMER files exist.
> > *All files have license headers if necessary.
> >
> > Best regards,
> > Eya
> >
> > On 2022/02/26 03:57:26 Alex Kwak wrote:
> > > Dear Apache AGE Community,
> > >
> > > This is an official vote for the Apache AGE Viewer v1.0.0-rc2 that we
> > have been working toward.
> > >
> > > To learn more about Apache AGE, please see http://age.apache.org/
> > >
> > > Functionalities included and addressed in this release:
> > > - Graph visualization for AGE.
> > > - Extends edge and vertex point by point.
> > > - Removed AgensGraph trademarks (as discussed in the previous vote
> email
> > thread)
> > >
> > > The vote will be open for 72 hours and pass if a majority +1 votes are
> > cast, with a minimum of 3 +1 votes.
> > >
> > > Please vote
> > >
> > > [ ] +1 Release this package as Apache AGE Viewer v1.0.0
> > > [ ] 0 I won't get in the way
> > > [ ] -1 Do not release this package because ...
> > >
> > >
> > > The git tag to be discussed and voted upon
> > > https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0-rc2
> > >
> > > The git commit hash:
> > > commit 63ed1882e372ef8cdf6677e9850237650e586848
> > >
> > > The release files, including signatures, digests, etc. can be found at:
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/age/viewer/apache-age-viewer-1.0.0-incubating-rc2/
> > >
> > > The SHA512 Checksum for these artifacts is:
> > >
> >
> 683f17b6bfc84d9fd8c88f0856b4dd18fdb24ab429517134880594243601f6810fefe9f7d9da7d5a802e2236622974c4297cee874e0f06685e85a40d5ac90d3d
> > >
> > > Release artifacts are signed with the following key:
> > > https://downloads.apache.org/incubator/age/KEYS
> > >
> > > The fingerprint of key to sign release artifacts:
> > > 0E7F 408D 8C6A 1952 329C B379 D471 FDCE 5F5C 5B82
> > >
> > > For more information about the contents of this release, see:
> > > https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0-rc2
> > >
> > >
> > >
> > > Best regards,
> > > Alex Kwak
> > >
> >
>

Re: [DISCUSS] Committer Requirements

[John Gemignani]

I'm thinking that 4 months may be too long or restrictive. Maybe it should
be based on the level of contribution activity, something like -

   - +3 months with light activity and engagement.
   - +2 months of medium activity and engagement.
   - +1 month with solid activity and engagement.

john

On Mon, Feb 28, 2022 at 3:14 PM Eya Badal  wrote:

> Thank you to anyone who contributed to this discussion. I would like to
> finalize the committer requirements guideline based on the discussions from
> this thread.
>
> Please following find the requirements:
>
> 1-Continuous contributions to AGE:
> Committers should have a decent amount, at least 4 continuous monthly
> engagement and contributions (fixing bugs, writing documentation, answering
> community questions) to AGE either by contributing on GitHub Repos,
> documentation and mailing list, etc
>
> 2-Quality of contributions:
> Well tested, well-designed, following Apache AGE coding standards, and
> simple patches.
>
> 3-Community involvement:
> Committers should support the development and advancement of AGE in
> different areas. They should also be active on the dev and user list and
> help mentor newer contributors and users. They should also be involved in
> the design road map discussions with a professional and diplomatic approach
> even if there is a disagreement.
>
> I will keep this discussion open for couple more days, and if no
> objections, I will close and publish the requirement on the AGE website.
>
> Best regards,
> Eya
>
> On 2022/01/06 20:14:31 Eya Badal wrote:
> > Hello everyone,
> >
> > As recommended by our mentors I would like to get community feedback and
> thoughts on committer requirements. I think we should discuss this and
> document the requirements.
> >
> > Best regards,
> > Eya
> >
>

Re: [DISCUSS] AGE Versioning in Master

[John Gemignani]

I agree as well.

John

On Wed, Mar 2, 2022 at 7:07 PM VUONG QUOC Viet  wrote:

> Hi Josh,
> I agree with your idea.
> Best regards,
> Viet.
>
> On Thu, Mar 3, 2022, 3:58 AM Josh Innis  wrote:
>
> > Hi All,
> >
> > For every release of AGE we update the version number. The team is
> > currently researching how to support upgrading between versions and an
> > issue about the order of updating the version in Master came to our
> > attention.
> >
> > Currently, before we create a release we update the version number.
> However
> > we do this at the end of a development of a release cycle rather than at
> > the beginning. This will become an issue with maintaining our upgrade
> > scripts going forward.
> >
> > So we propose this change to our release cycle: update the version of AGE
> > in Master at the beginning of a development cycle rather than at the end.
> > This will allow us to construct the upgrade scripts through the whole
> > process of the release rather than having to do it all at once in the
> end.
> >
> > For the current release, we just make the change now and follow this
> > process going forward.
> >
> > Thoughts?/Concerns?/Questions?
> >
>

Re: [VOTE] Apache AGE 1.0.0 Release

[John Gemignani]

+1

On Thu, Mar 17, 2022 at 5:28 PM Josh Innis  wrote:

> +1
>
> On Thu, Mar 17, 2022 at 3:25 PM Nicholas Sorrell  wrote:
>
> > Reminder, the vote is scheduled to close in less than 24 hours.
> >
> > Please vote:
> >
> > [ ] +1 Release this package as Apache AGE 1.0.0
> > [ ] 0  I won't get in the way
> > [ ] -1 Do not release this package because ...
> > 
> > From: Nicholas Sorrell 
> > Sent: Tuesday, March 15, 2022 3:03:00 PM
> > To: dev@age.apache.org 
> > Subject: [VOTE] Apache AGE 1.0.0 Release
> >
> > Dear Apache Community,
> >
> > This is an official vote for the Apache AGE release 1.0.0 that we have
> > been working towards.
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > Functionality included and addressed in this release:
> >
> >   - Add an upgrading SQL script file from 0.5.0 to 0.6.0
> >   - Add upgrading file age--0.6.0--0.7.0.sql
> >   - Refactor function get_agtype_value_object_value
> >   - Age load issue (#188)
> >   - Refactor agtype_access_operator
> >   - Bugfix - Remove INLINE from function declaration
> >   - Rebase VLE code
> >   - Implement Merge Clause
> >   - Bugfix: chained union logic
> >   - Allow a path of one vertex
> >   - Created functions for load graph from CSV files
> >   - Add UNION into EXPLAIN grammar rule
> >   - Implement `UNWIND` clause(#173)
> >   - Bugfix:(nodejs) Corrects parsing for independence value(#177)
> >   - Feat: Implement `OPTIONAL MATCH` (#175)
> >
> > *
> >
> > The git tag to be discussed and voted upon:
> > https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc0
> >
> > The git commit hash:
> >   commit 6660aa419f967118cfba20f554b0db1549bb15f7
> >
> > The release files for 1.0.0, can be found at:
> >  https://dist.apache.org/repos/dist/dev/incubator/age/1.0.0.rc0/
> >
> > Signatures used for AGE RCs can be found in this file:
> > https://downloads.apache.org/incubator/age/KEYS
> >
> > The fingerprint of key to sign release artifacts:
> >   C3F1 A95F 43D0 CCF6 A5EF  92C5 4E03 406A 5227 E499
> >
> > For information about the contents of this release, see:
> > https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc0
> >
> > *
> >
> > Please vote:
> >
> > [ ] +1 Release this package as Apache AGE 1.0.0
> > [ ] 0  I won't get in the way
> > [ ] -1 Do not release this package because ...
> >
> >
> > This vote will be open for 72 hours.
> >
> > Thank you for your time.
> >
> >
> > Best Regards,
> > Nick Sorrell
> >
>

Re: [VOTE] Apache AGE 1.0.0 Release

[John Gemignani]

Hi Dmitry,

We do very much appreciate your activity however,...

This is a thread for voting on a specific release and whether all the files
meet Apache's criteria. Please do not reply to it with anything unrelated
to the specific release. Releases are generally frozen, meaning nothing new
will get added.

For future reference, questions like this should be posted on github or in
a different email thread.

Thanks,

john

On Wed, Mar 30, 2022 at 8:06 AM Dmitry Dorofeev  wrote:

> Hi all,
>
> If we are not releasing 1.0.0 right now, can anyone check typo issue
> https://github.com/apache/incubator-age/pull/203
>
> It would be nice if it is fixed in release 1.0
>
> Thanks,
>
> -D.
>
> On 30.03.2022 15:37 PM, Nicholas Sorrell wrote:
> >
> > I am closing this vote to address the issues noted by Trista. I will
> open a new vote thread for the new release candidate after the issues are
> resolved.
> >
> > Thanks,
> > Nick
> >
> > 
> > From: hannk...@163.com  on behalf of Juan Pan <
> panj...@apache.org>
> > Sent: Tuesday, March 29, 2022 3:41 AM
> > To: dev@age.apache.org 
> > Cc: dev@age.apache.org 
> > Subject: Re:[VOTE] Apache AGE 1.0.0 Release
> >
> > Hello,
> >
> >
> > There are some issues from my side, could anyone give it a look?
> > 1. Copyright 2021-> Copyright 2022 on NOTICE
> > 2. The unzipped directory of `apache-age-1.0.0-incubating-src.tar.gz` is
> `git_apache-age-1.0.0-incubating`?
> >
> >
> > Thanks,
> > Trista
> >
> --
> > Trista Pan
> > Twitter & Github: tristaZero
> >
> >
> >
> >
> > On 03/16/2022 03:03，Nicholas Sorrell wrote：
> > Dear Apache Community,
> >
> > This is an official vote for the Apache AGE release 1.0.0 that we have
> been working towards.
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > Functionality included and addressed in this release:
> >
> > - Add an upgrading SQL script file from 0.5.0 to 0.6.0
> > - Add upgrading file age--0.6.0--0.7.0.sql
> > - Refactor function get_agtype_value_object_value
> > - Age load issue (#188)
> > - Refactor agtype_access_operator
> > - Bugfix - Remove INLINE from function declaration
> > - Rebase VLE code
> > - Implement Merge Clause
> > - Bugfix: chained union logic
> > - Allow a path of one vertex
> > - Created functions for load graph from CSV files
> > - Add UNION into EXPLAIN grammar rule
> > - Implement `UNWIND` clause(#173)
> > - Bugfix:(nodejs) Corrects parsing for independence value(#177)
> > - Feat: Implement `OPTIONAL MATCH` (#175)
> >
> > *
> >
> > The git tag to be discussed and voted upon:
> > https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc0
> >
> > The git commit hash:
> > commit 6660aa419f967118cfba20f554b0db1549bb15f7
> >
> > The release files for 1.0.0, can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/age/1.0.0.rc0/
> >
> > Signatures used for AGE RCs can be found in this file:
> > https://downloads.apache.org/incubator/age/KEYS
> >
> > The fingerprint of key to sign release artifacts:
> > C3F1 A95F 43D0 CCF6 A5EF  92C5 4E03 406A 5227 E499
> >
> > For information about the contents of this release, see:
> > https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc0
> >
> > *
> >
> > Please vote:
> >
> > [ ] +1 Release this package as Apache AGE 1.0.0
> > [ ] 0  I won't get in the way
> > [ ] -1 Do not release this package because ...
> >
> >
> > This vote will be open for 72 hours.
> >
> > Thank you for your time.
> >
> >
> > Best Regards,
> > Nick Sorrell
> >
>

Re: [VOTE] Apache AGE 1.0.0-rc1 Release

[John Gemignani]

+1

- Verified commit hash is correct.
- Verified Signatures.
- Verified download links are valid.
- Verified LICENSE, NOTICE and DISCLAIMER files.
- Verified that all files have the appropriate licence header where
applicable.
- Verified that all links above are valid.

On Thu, Mar 31, 2022 at 5:42 AM Juan Pan  wrote:

> Hi, +1, here is my checking list.
>
>
>
>
> [x] Download links are valid.
>
> [x] Checksums and PGP signatures are valid.
>
> [x] LICENSE, NOTICE and DISCLAIMER files are correct.
>
> [x] All files have license headers if necessary.
>
>
>
> --
> Trista Pan
> Twitter & Github: tristaZero
>
>
>
>
> On 03/31/2022 07:37，Nicholas Sorrell wrote：
> Dear Apache Community,
>
> This is an official vote for Apache AGE release 1.0.0-rc1.
>
> To learn more about Apache AGE, please see https://age.apache.org/
>
> Functionality included and addressed in this release:
>
> - Add an upgrading SQL script file from 0.5.0 to 0.6.0
> - Add upgrading file age--0.6.0--0.7.0.sql
> - Refactor function get_agtype_value_object_value
> - Age load issue (issue #188)
> - Refactor agtype_access_operator
> - Bugfix - Remove INLINE from function declaration
> - Rebase VLE code
> - Implement Merge Clause
> - Bugfix: chained union logic
> - Allow a path of one vertex
> - Created functions for load graph from CSV files
> - Add UNION into EXPLAIN grammar rule
> - Implement UNWIND clause(issue #173)
> - Bugfix:(nodejs) Corrects parsing for independence value(issue #177)
> - Feat: Implement OPTIONAL MATCH (issue #175)
> - Update copyright in NOTICE
>
>
> *
>
> The git tag to be discussed and voted upon:
> https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc1
>
> The git commit hash:
> commit 282c24f4aa7150daceba15742966ac6be77a35c4
>
> The release files for 1.0.0, can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/age/1.0.0.rc1/
>
> Signatures used for AGE RCs can be found in this file:
> https://downloads.apache.org/incubator/age/KEYS
>
> The fingerprint of key to sign release artifacts:
> C3F1 A95F 43D0 CCF6 A5EF  92C5 4E03 406A 5227 E499
>
> For information about the contents of this release, see:
> https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc1
>
> *
>
> Please vote:
>
> [ ] +1 Release this package as Apache AGE 1.0.0-rc1
> [ ] 0  I won't get in the way
> [ ] -1 Do not release this package because ...
>
>
> This vote will be open for 72 hours.
>
> Thank you for your time.
>
>
> Best Regards,
> Nick Sorrell
>
>

Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 -> b5cdd67)

[John Gemignani]

@Nicholas Sorrell 

What was done that triggered this?

John

On Tue, Apr 5, 2022 at 4:38 PM  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> sorrell pushed a change to annotated tag v0.7.0
> in repository https://gitbox.apache.org/repos/asf/incubator-age.git
>
>
> *** WARNING: tag v0.7.0 was modified! ***
>
> from d0175f4  (commit)
>   to b5cdd67  (tag)
>  tagging d0175f4a2fb03f28c356ea43da3bd48a47f5ef42 (commit)
>  replaces v0.3.0.rc0-incubating
>   by Nick Sorrell
>   on Tue Apr 5 19:37:34 2022 -0400
>
> - Log -
> v0.7.0
> ---
>
>
> No new revisions were added by this update.
>
> Summary of changes:
>
>

Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 -> b5cdd67)

[John Gemignani]

My issues are twofold -

   1. Issues that involve the master repository, like this one, need to be
   addressed or communicated to the entire team.
   2. We do not delete anything from the master repository unless there is
   a compelling, valid reason. And, deletes, even tags, need to be
   communicated to the entire team.

Both of these basically come down to communication and verification. We
need to make sure everyone understands that anything that modifies the
master repository is communicated and okayed by others.

John

On Wed, Apr 6, 2022 at 9:17 AM Nicholas Sorrell  wrote:

> Hi John,
>
> The automated email is certainly misleading, as I don't know where it's
> getting the 0.3.0 stuff from.
>
> Here's the full context of the tagging:
> - Eya and I were trying to get the automated build to trigger at Docker
> Hub (https://hub.docker.com/r/apache/age)
> - I pushed a v0.7.0 annotated tag (on Saturday 2-APR) on top of the
> v0.7.0-rc0 tag (same commit hash (d0175f4)) to trigger the build
> - The build did not trigger at Docker Hub, so Eya and I worked together to
> fix the build trigger at Docker Hub
> - To re-trigger the build for v0.7.0, I first had to delete the existing
> v0.7.0 tag and then push a new one at the same commit hash (d0175f4)
> - That tag triggered a successful build at Docker Hub, and the tag can be
> viewed here as the most recent tag:
> https://github.com/apache/incubator-age/tags
> - The release, assets, and source code were not altered in any way, this
> was only a tag added to tree
>
> Hope this helps, and happy to answer any other questions.
> -Nick
>
> 
> From: John Gemignani 
> Sent: Wednesday, April 6, 2022 11:52 AM
> To: dev@age.apache.org ; Nicholas Sorrell <
> n...@cint.io>
> Cc: comm...@age.apache.org 
> Subject: Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 ->
> b5cdd67)
>
> @Nicholas Sorrell<mailto:n...@cint.io>
>
> What was done that triggered this?
>
> John
>
> On Tue, Apr 5, 2022 at 4:38 PM  sorr...@apache.org>> wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> sorrell pushed a change to annotated tag v0.7.0
> in repository https://gitbox.apache.org/repos/asf/incubator-age.git
>
>
> *** WARNING: tag v0.7.0 was modified! ***
>
> from d0175f4  (commit)
>   to b5cdd67  (tag)
>  tagging d0175f4a2fb03f28c356ea43da3bd48a47f5ef42 (commit)
>  replaces v0.3.0.rc0-incubating
>   by Nick Sorrell
>   on Tue Apr 5 19:37:34 2022 -0400
>
> - Log -
> v0.7.0
> ---
>
>
> No new revisions were added by this update.
>
> Summary of changes:
>
>

Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 -> b5cdd67)

[John Gemignani]

Eya,

I don't think it necessarily falls to you. Whomever is doing the work needs
to open a discussion thread. We should probably add this to our
documentation so that it doesn't feel like anyone specifically is being
singled out.

This is new to all of us, there will inevitably be mistakes that we can
learn from and add to our documentation.

John

On Wed, Apr 6, 2022 at 9:54 AM Eya Badal  wrote:

> Next time, I will open a discussion thread so everyone can have visibility
> on the steps and actions that need to be taken.
>
> As of now, I believe we need to have a better system to build the docker
> and push it to the docker hub.
>
> Thank you,
> Eya
>
> On 2022/04/06 16:48:47 John Gemignani wrote:
> > My issues are twofold -
> >
> >1. Issues that involve the master repository, like this one, need to
> be
> >addressed or communicated to the entire team.
> >2. We do not delete anything from the master repository unless there
> is
> >a compelling, valid reason. And, deletes, even tags, need to be
> >communicated to the entire team.
> >
> > Both of these basically come down to communication and verification. We
> > need to make sure everyone understands that anything that modifies the
> > master repository is communicated and okayed by others.
> >
> > John
> >
> > On Wed, Apr 6, 2022 at 9:17 AM Nicholas Sorrell  wrote:
> >
> > > Hi John,
> > >
> > > The automated email is certainly misleading, as I don't know where it's
> > > getting the 0.3.0 stuff from.
> > >
> > > Here's the full context of the tagging:
> > > - Eya and I were trying to get the automated build to trigger at Docker
> > > Hub (https://hub.docker.com/r/apache/age)
> > > - I pushed a v0.7.0 annotated tag (on Saturday 2-APR) on top of the
> > > v0.7.0-rc0 tag (same commit hash (d0175f4)) to trigger the build
> > > - The build did not trigger at Docker Hub, so Eya and I worked
> together to
> > > fix the build trigger at Docker Hub
> > > - To re-trigger the build for v0.7.0, I first had to delete the
> existing
> > > v0.7.0 tag and then push a new one at the same commit hash (d0175f4)
> > > - That tag triggered a successful build at Docker Hub, and the tag can
> be
> > > viewed here as the most recent tag:
> > > https://github.com/apache/incubator-age/tags
> > > - The release, assets, and source code were not altered in any way,
> this
> > > was only a tag added to tree
> > >
> > > Hope this helps, and happy to answer any other questions.
> > > -Nick
> > >
> > > 
> > > From: John Gemignani 
> > > Sent: Wednesday, April 6, 2022 11:52 AM
> > > To: dev@age.apache.org ; Nicholas Sorrell <
> > > n...@cint.io>
> > > Cc: comm...@age.apache.org 
> > > Subject: Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 ->
> > > b5cdd67)
> > >
> > > @Nicholas Sorrell<mailto:n...@cint.io>
> > >
> > > What was done that triggered this?
> > >
> > > John
> > >
> > > On Tue, Apr 5, 2022 at 4:38 PM  > > sorr...@apache.org>> wrote:
> > > This is an automated email from the ASF dual-hosted git repository.
> > >
> > > sorrell pushed a change to annotated tag v0.7.0
> > > in repository https://gitbox.apache.org/repos/asf/incubator-age.git
> > >
> > >
> > > *** WARNING: tag v0.7.0 was modified! ***
> > >
> > > from d0175f4  (commit)
> > >   to b5cdd67  (tag)
> > >  tagging d0175f4a2fb03f28c356ea43da3bd48a47f5ef42 (commit)
> > >  replaces v0.3.0.rc0-incubating
> > >   by Nick Sorrell
> > >   on Tue Apr 5 19:37:34 2022 -0400
> > >
> > > - Log -
> > > v0.7.0
> > > ---
> > >
> > >
> > > No new revisions were added by this update.
> > >
> > > Summary of changes:
> > >
> > >
> >
>

Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 -> b5cdd67)

[John Gemignani]

I totally agree with you Nick.

John

On Wed, Apr 6, 2022 at 9:59 AM Nicholas Sorrell  wrote:

> John,
>
> Your concerns are valid and I'm sorry for any confusion I created.
> However, the Developer Guidelines at https://age.apache.org don't reflect
> the process you'd like to see enforced. We should probably update those
> guidelines to reflect how we'd like the community to operate.
>
> -Nick
>
>
>
> 
> From: Eya Badal 
> Sent: Wednesday, April 6, 2022 12:54 PM
> To: dev@age.apache.org 
> Subject: Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 ->
> b5cdd67)
>
> Next time, I will open a discussion thread so everyone can have visibility
> on the steps and actions that need to be taken.
>
> As of now, I believe we need to have a better system to build the docker
> and push it to the docker hub.
>
> Thank you,
> Eya
>
> On 2022/04/06 16:48:47 John Gemignani wrote:
> > My issues are twofold -
> >
> >1. Issues that involve the master repository, like this one, need to
> be
> >addressed or communicated to the entire team.
> >2. We do not delete anything from the master repository unless there
> is
> >a compelling, valid reason. And, deletes, even tags, need to be
> >communicated to the entire team.
> >
> > Both of these basically come down to communication and verification. We
> > need to make sure everyone understands that anything that modifies the
> > master repository is communicated and okayed by others.
> >
> > John
> >
> > On Wed, Apr 6, 2022 at 9:17 AM Nicholas Sorrell  wrote:
> >
> > > Hi John,
> > >
> > > The automated email is certainly misleading, as I don't know where it's
> > > getting the 0.3.0 stuff from.
> > >
> > > Here's the full context of the tagging:
> > > - Eya and I were trying to get the automated build to trigger at Docker
> > > Hub (https://hub.docker.com/r/apache/age)
> > > - I pushed a v0.7.0 annotated tag (on Saturday 2-APR) on top of the
> > > v0.7.0-rc0 tag (same commit hash (d0175f4)) to trigger the build
> > > - The build did not trigger at Docker Hub, so Eya and I worked
> together to
> > > fix the build trigger at Docker Hub
> > > - To re-trigger the build for v0.7.0, I first had to delete the
> existing
> > > v0.7.0 tag and then push a new one at the same commit hash (d0175f4)
> > > - That tag triggered a successful build at Docker Hub, and the tag can
> be
> > > viewed here as the most recent tag:
> > > https://github.com/apache/incubator-age/tags
> > > - The release, assets, and source code were not altered in any way,
> this
> > > was only a tag added to tree
> > >
> > > Hope this helps, and happy to answer any other questions.
> > > -Nick
> > >
> > > 
> > > From: John Gemignani 
> > > Sent: Wednesday, April 6, 2022 11:52 AM
> > > To: dev@age.apache.org ; Nicholas Sorrell <
> > > n...@cint.io>
> > > Cc: comm...@age.apache.org 
> > > Subject: Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 ->
> > > b5cdd67)
> > >
> > > @Nicholas Sorrell<mailto:n...@cint.io>
> > >
> > > What was done that triggered this?
> > >
> > > John
> > >
> > > On Tue, Apr 5, 2022 at 4:38 PM  > > sorr...@apache.org>> wrote:
> > > This is an automated email from the ASF dual-hosted git repository.
> > >
> > > sorrell pushed a change to annotated tag v0.7.0
> > > in repository https://gitbox.apache.org/repos/asf/incubator-age.git
> > >
> > >
> > > *** WARNING: tag v0.7.0 was modified! ***
> > >
> > > from d0175f4  (commit)
> > >   to b5cdd67  (tag)
> > >  tagging d0175f4a2fb03f28c356ea43da3bd48a47f5ef42 (commit)
> > >  replaces v0.3.0.rc0-incubating
> > >   by Nick Sorrell
> > >   on Tue Apr 5 19:37:34 2022 -0400
> > >
> > > - Log -
> > > v0.7.0
> > > ---
> > >
> > >
> > > No new revisions were added by this update.
> > >
> > > Summary of changes:
> > >
> > >
> >
>

Re: [VOTE] Release Apache AGE 1.1.0-rc0

[John Gemignani]

Good job!

+1

On Thu, Aug 11, 2022 at 4:20 PM Dehowe Feng  wrote:

> I am pleased to see this release for the AGE community.
>
> Great job, Eya
>
> +1
>
> On Thu, Aug 11, 2022 at 7:14 AM Eya Badal  wrote:
>
> > Hello AGE community,
> >
> > I would like to call a vote for releasing Apache AGE 1.1.0-rc0.
> > The first release for Apache AGE as a top-level project. Please
> > note that the location of the artifacts file has changed as
> > we are now a top-level project.
> >
> >
> > The release candidate has been tagged in GitHub as v1.1.0-rc0, available
> > here:
> > https://github.com/apache/age/tree/v1.1.0-rc0
> >
> > Release Notes are here:
> > https://github.com/apache/age/releases/tag/v1.1.0-rc0
> >
> > The release artifacts have been uploaded here(source, signature, and
> > checksum):
> > https://dist.apache.org/repos/dist/dev/age/1.1.0.rc0/
> >
> > Keys are in the KEYS file:
> > https://downloads.apache.org/age/KEYS
> >
> > The git commit hash:
> > 4db7cea9e1c94e591da42997a1ca61f507105c24
> >
> > Some functionalities included and addressed in this release:
> > *Support for Agtype containment ops and GIN Indices.
> > *Add CALL [YIELD] grammar rules for the implementation of CALL
> procedures.
> > *VLE path variable integration performance patch.
> > *Improve WHERE clause performance and support index scans.
> > *Allow global graph contexts to see currentCommandIds.
> >
> >
> > Please review and vote. The vote will be open for at least 72 hours
> > and closes on Sunday, 14 August 2022, 7:20 AM PDT.
> >
> > [ ] +1 Approve
> > [ ] +0 No opinion
> > [ ] -1 Disapprove (and the reason why)
> >
> >
> > Thank you,
> > Eya Badal
> >
>

Re: [VOTE] Release Apache AGE 1.1.0-rc0

[John Gemignani]

Btw, my +1 was binding. Sorry for leaving that out.

john

On Thu, Aug 11, 2022 at 7:14 AM Eya Badal  wrote:

> Hello AGE community,
>
> I would like to call a vote for releasing Apache AGE 1.1.0-rc0.
> The first release for Apache AGE as a top-level project. Please
> note that the location of the artifacts file has changed as
> we are now a top-level project.
>
>
> The release candidate has been tagged in GitHub as v1.1.0-rc0, available
> here:
> https://github.com/apache/age/tree/v1.1.0-rc0
>
> Release Notes are here:
> https://github.com/apache/age/releases/tag/v1.1.0-rc0
>
> The release artifacts have been uploaded here(source, signature, and
> checksum):
> https://dist.apache.org/repos/dist/dev/age/1.1.0.rc0/
>
> Keys are in the KEYS file:
> https://downloads.apache.org/age/KEYS
>
> The git commit hash:
> 4db7cea9e1c94e591da42997a1ca61f507105c24
>
> Some functionalities included and addressed in this release:
> *Support for Agtype containment ops and GIN Indices.
> *Add CALL [YIELD] grammar rules for the implementation of CALL procedures.
> *VLE path variable integration performance patch.
> *Improve WHERE clause performance and support index scans.
> *Allow global graph contexts to see currentCommandIds.
>
>
> Please review and vote. The vote will be open for at least 72 hours
> and closes on Sunday, 14 August 2022, 7:20 AM PDT.
>
> [ ] +1 Approve
> [ ] +0 No opinion
> [ ] -1 Disapprove (and the reason why)
>
>
> Thank you,
> Eya Badal
>

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[John Gemignani]

It is also likely, for a little while at least, that AGE 11 will have more
current features and fixes than 12 or successive versions.

We are definitely going to need to come up with a process to address
features and fixes being added in and propagated through the appropriate
versions.

john

On Fri, Sep 30, 2022 at 1:14 AM Muhammad Shoaib 
wrote:

> Hi Pertejan,
>
> Currently this is not the case. However, in the future new versions might
> have more features than older versions.
>
> I'll support the following
>
>1. for PG 11, AGE_11_1.1.0
>2. for PG 12, AGE_12_1.1.0
>
>
> Kind regards
> Shoaib
>
> On Fri, Sep 30, 2022 at 9:52 AM Pieterjan De Potter
>  wrote:
>
> > Dear Everyone,
> >
> > I too think it would be nice to have similar version numbering for
> > similar feature sets.
> >
> > One question that could make this impossible though: will there be
> > future features that will only be implemented for some versions of
> > Postgres (11, 12, 13, 14, 15, ...) because of underlying features
> > supported by those particular Postgres versions? Or would that at that
> > point be a reason to stop support for Postgres versions that don't
> > support these underlying features?
> >
> > Kind regards,
> > Pieterjan
> >
> >
> > On 29.09.22 21:23, Jasper Blues wrote:
> > > I think it should be versioned after the main development/R&D version.
> > >
> > > *Reasons: *
> > > *
> > > *
> > >
> > >   * It is easy to tie back to what this version was based off, without
> > > looking up an index (which could be prone to error).
> > >   * If there is an as yet unfixed edge case bug affecting some portion
> > > of users on a particular version+pgVersion, they may have some
> > > confidence about what up/downgrade version to try should they also
> > > want to up/downgrade Postgres.
> > >   * Simplicity : It is one of the core XP values along with
> > > communication, feedback, courage and respect.
> > >
> > >
> > >
> > >> On Sep 30, 2022, at 5:18 AM, Eya Badal  > >> > wrote:
> > >>
> > >> Dear Everyone,
> > >>
> > >> We are planning on our first release of Apache AGE for Postgres 12. It
> > >> will be based on the Apache AGE 1.1.0 release that supports Postgres
> > >> 11. There will be a prefix for this release and all Postgres 12
> > >> supported releases.
> > >>
> > >> However, since this is the first Postgres 12 release, should the
> > >> version be 1.0.0 or 1.1.0 because it is based on the 1.1.0 release for
> > >> Postgres 11?
> > >>
> > >> Please share your thoughts and suggestions.
> > >>
> > >> Thank you very much,
> > >> Eya
> > >
> >
> >
>

[DISCUSS] Apache AGE 1.1.0 Release for PostgreSQL 12

[John Gemignani]

Dear Apache Community,



We would like to discuss the Apache AGE release 1.1.0 for PostgreSQL 12
(PG12) that we have been working on.



To learn more about Apache AGE, please see http://age.apache.org/



Functionalities included and addressed in this release:


   - Support for Agtype containment ops and GIN Indices.
   - Add CALL [YIELD] grammar rules for the implementation of CALL
   procedures.
   - VLE path variable integration performance patch.
   - Improve WHERE clause performance and support index scans.
   - Allow global graph contexts to see currentCommandIds.
   - Cache Agtype and GRAPHID OIDs.
   - Allow lists and maps to be used in the SET clause.
   - Fix bug in aggregate function collect().
   - Fix Bug in WHERE clause and property constraints.
   - Fix VLE local cache bug (crash).
   - Fix bug where integers were not being serialized correctly when stored
   in GIN indices.
   - Fix the VLE peek_stack_head routine to return a NULL if the stack is
   NULL.
   - Fix MERGE visibility in chained commands, SET specifically.
   - Fix github issue #212 <https://github.com/apache/age/pull/212> - Add
   access operator (->, ->>) to Agtype.
   - Fix github issue #220 <https://github.com/apache/age/issues/220> - fix
   local cached contexts for static procedures.
   - Fix github issue #224 <https://github.com/apache/age/pull/224> - fix
   regression tests to fix issues on mac with trigonometric functions.
   - Fix github issue #235 <https://github.com/apache/age/issues/235> -
   when MERGE and SET were used together.
   - Fix github issue #240 <https://github.com/apache/age/issues/240> -
   negative array bounds.
   - Fix github issue #240 <https://github.com/apache/age/issues/240> -
   negative array bounds - addendum.
   - Updated README.


*



The git tag to be discussed and voted upon:

https://github.com/apache/age/releases/tag/PG12/v.1.1.0-rc0
<https://github.com/apache/age/releases/tag/PG12%2Fv1.1.0-rc0>



The git commit hash:

 commit 1d9d60197e2cf3fc48aac573278f6f9e173ee78b

The release files for 1.1.0, can be found at:

 https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0
<https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0>



Signatures used for AGE RCs can be found in this file:

https://downloads.apache.org/age/KEYS
<https://downloads.apache.org/age/KEYS>



The fingerprint of key to sign release artifacts:

4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045



For information about the contents of this release, see:

https://github.com/apache/age/releases/tag/PG12/v1.1.0-rc0



Please share your thoughts and feedback and let us know if we can call for

a vote.

Thank you for your time.


John Gemignani

Re: [DISCUSS] Apache AGE 1.1.0 Release for PostgreSQL 12

[John Gemignani]

Thank you to everyone who took the time to give input. We will now be
closing the discussion and opening the vote.

John

On Tue, Nov 1, 2022 at 10:54 AM Eya Badal  wrote:

> Looks good to me.
>
> I checked the following:
>
> - Signature and hash - check.
> - LICENSE and NOTICE - check.
> - No unexpected binary files - check.
>
> Great Job!!
>
> Best,
> Eya
>
> On 2022/10/28 00:32:15 John Gemignani wrote:
> > Dear Apache Community,
> >
> >
> >
> > We would like to discuss the Apache AGE release 1.1.0 for PostgreSQL 12
> > (PG12) that we have been working on.
> >
> >
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> >
> >
> > Functionalities included and addressed in this release:
> >
> >
> >- Support for Agtype containment ops and GIN Indices.
> >- Add CALL [YIELD] grammar rules for the implementation of CALL
> >procedures.
> >- VLE path variable integration performance patch.
> >- Improve WHERE clause performance and support index scans.
> >- Allow global graph contexts to see currentCommandIds.
> >- Cache Agtype and GRAPHID OIDs.
> >- Allow lists and maps to be used in the SET clause.
> >- Fix bug in aggregate function collect().
> >- Fix Bug in WHERE clause and property constraints.
> >- Fix VLE local cache bug (crash).
> >- Fix bug where integers were not being serialized correctly when
> stored
> >in GIN indices.
> >- Fix the VLE peek_stack_head routine to return a NULL if the stack is
> >NULL.
> >- Fix MERGE visibility in chained commands, SET specifically.
> >- Fix github issue #212 <https://github.com/apache/age/pull/212> -
> Add
> >access operator (->, ->>) to Agtype.
> >- Fix github issue #220 <https://github.com/apache/age/issues/220> -
> fix
> >local cached contexts for static procedures.
> >- Fix github issue #224 <https://github.com/apache/age/pull/224> -
> fix
> >regression tests to fix issues on mac with trigonometric functions.
> >- Fix github issue #235 <https://github.com/apache/age/issues/235> -
> >when MERGE and SET were used together.
> >- Fix github issue #240 <https://github.com/apache/age/issues/240> -
> >negative array bounds.
> >- Fix github issue #240 <https://github.com/apache/age/issues/240> -
> >negative array bounds - addendum.
> >- Updated README.
> >
> >
> > *
> >
> >
> >
> > The git tag to be discussed and voted upon:
> >
> > https://github.com/apache/age/releases/tag/PG12/v.1.1.0-rc0
> > <https://github.com/apache/age/releases/tag/PG12%2Fv1.1.0-rc0>
> >
> >
> >
> > The git commit hash:
> >
> >  commit 1d9d60197e2cf3fc48aac573278f6f9e173ee78b
> >
> > The release files for 1.1.0, can be found at:
> >
> >  https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0
> > <https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0>
> >
> >
> >
> > Signatures used for AGE RCs can be found in this file:
> >
> > https://downloads.apache.org/age/KEYS
> > <https://downloads.apache.org/age/KEYS>
> >
> >
> >
> > The fingerprint of key to sign release artifacts:
> >
> > 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
> >
> >
> >
> > For information about the contents of this release, see:
> >
> > https://github.com/apache/age/releases/tag/PG12/v1.1.0-rc0
> >
> >
> >
> > Please share your thoughts and feedback and let us know if we can call
> for
> >
> > a vote.
> >
> > Thank you for your time.
> >
> >
> > John Gemignani
> >
>

[VOTE] Apache AGE 1.1.0 for PG12 Release

[John Gemignani]

Dear Apache Community,



We are now opening the vote for the Apache AGE release 1.1.0 for PostgreSQL
12 (PG12).



To learn more about Apache AGE, please see http://age.apache.org/



Functionalities included and addressed in this release:


   - Support for Agtype containment ops and GIN Indices.
   - Add CALL [YIELD] grammar rules for the implementation of CALL
   procedures.
   - VLE path variable integration performance patch.
   - Improve WHERE clause performance and support index scans.
   - Allow global graph contexts to see currentCommandIds.
   - Cache Agtype and GRAPHID OIDs.
   - Allow lists and maps to be used in the SET clause.
   - Fix bug in aggregate function collect().
   - Fix Bug in WHERE clause and property constraints.
   - Fix VLE local cache bug (crash).
   - Fix bug where integers were not being serialized correctly when stored
   in GIN indices.
   - Fix the VLE peek_stack_head routine to return a NULL if the stack is
   NULL.
   - Fix MERGE visibility in chained commands, SET specifically.
   - Fix github issue #212 <https://github.com/apache/age/pull/212> - Add
   access operator (->, ->>) to Agtype.
   - Fix github issue #220 <https://github.com/apache/age/issues/220> - fix
   local cached contexts for static procedures.
   - Fix github issue #224 <https://github.com/apache/age/pull/224> - fix
   regression tests to fix issues on mac with trigonometric functions.
   - Fix github issue #235 <https://github.com/apache/age/issues/235> -
   when MERGE and SET were used together.
   - Fix github issue #240 <https://github.com/apache/age/issues/240> -
   negative array bounds.
   - Fix github issue #240 <https://github.com/apache/age/issues/240> -
   negative array bounds - addendum.
   - Updated README.


*



The git tag to be discussed and voted upon:

https://github.com/apache/age/releases/tag/PG12/v.1.1.0-rc0
<https://github.com/apache/age/releases/tag/PG12%2Fv1.1.0-rc0>



The git commit hash:


 commit 1d9d60197e2cf3fc48aac573278f6f9e173ee78b


The release files for 1.1.0, can be found at:

 https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0
<https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0>



Signatures used for AGE RCs can be found in this file:

https://downloads.apache.org/age/KEYS
<https://downloads.apache.org/age/KEYS>



The fingerprint of key to sign release artifacts:


4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045



For information about the contents of this release, see:

https://github.com/apache/age/releases/tag/PG12/v1.1.0-rc0



Please review that everything meets your criteria and vote accordingly.


Please vote:


[ ] +1 Release this package as Apache AGE 0.7.0

[ ] 0 I won't get in the way

[ ] -1 Do not release this package because ...

This vote will be open for 72 hours.

As always, thank you for your time.


John Gemignani

Re: [VOTE] Apache AGE 1.1.0 for PG12 Release

[John Gemignani]

We are closing this voting thread and will announce the results shortly.

John

On Wed, Nov 9, 2022 at 9:28 AM Muhammad Shoaib 
wrote:

> +1 non binding
>
> I checked the following.
>
>   - PGP Signatures.
>  - SHA512 Checksums.
>   - LICENSE and NOTICE are fine.
>
> On Mon, 7 Nov 2022 at 21:21, Dehowe Feng  wrote:
>
> > +1
> >
> > On Mon, Nov 7, 2022 at 2:17 AM Nicholas Sorrell  wrote:
> >
> > > +1
> > >
> > > > On Nov 7, 2022, at 04:11, Pieterjan De Potter <
> > > pieterjan.depot...@ugent.be.invalid> wrote:
> > > >
> > > > +1
> > > >
> > > >> On 04.11.22 19:40, John Gemignani wrote:
> > > >> Dear Apache Community,
> > > >> We are now opening the vote for the Apache AGE release 1.1.0 for
> > > PostgreSQL
> > > >> 12 (PG12).
> > > >> To learn more about Apache AGE, please see http://age.apache.org/>>
> > > Functionalities included and addressed in this release:
> > > >>- Support for Agtype containment ops and GIN Indices.
> > > >>- Add CALL [YIELD] grammar rules for the implementation of CALL
> > > >>procedures.
> > > >>- VLE path variable integration performance patch.
> > > >>- Improve WHERE clause performance and support index scans.
> > > >>- Allow global graph contexts to see currentCommandIds.
> > > >>- Cache Agtype and GRAPHID OIDs.
> > > >>- Allow lists and maps to be used in the SET clause.
> > > >>- Fix bug in aggregate function collect().
> > > >>- Fix Bug in WHERE clause and property constraints.
> > > >>- Fix VLE local cache bug (crash).
> > > >>- Fix bug where integers were not being serialized correctly when
> > > stored
> > > >>in GIN indices.
> > > >>- Fix the VLE peek_stack_head routine to return a NULL if the
> stack
> > > is
> > > >>NULL.
> > > >>- Fix MERGE visibility in chained commands, SET specifically.
> > > >>- Fix github issue #212 <https://github.com/apache/age/pull/212
> -
> > > Add
> > > >>access operator (->, ->>) to Agtype.
> > > >>- Fix github issue #220 <
> https://github.com/apache/age/issues/220
> > -
> > > fix
> > > >>local cached contexts for static procedures.
> > > >>- Fix github issue #224 <https://github.com/apache/age/pull/224
> -
> > > fix
> > > >>regression tests to fix issues on mac with trigonometric
> functions.
> > > >>- Fix github issue #235 <
> https://github.com/apache/age/issues/235
> > -
> > > >>when MERGE and SET were used together.
> > > >>- Fix github issue #240 <
> https://github.com/apache/age/issues/240
> > -
> > > >>negative array bounds.
> > > >>- Fix github issue #240 <
> https://github.com/apache/age/issues/240
> > -
> > > >>negative array bounds - addendum.
> > > >>- Updated README.
> > > >> *
> > > >> The git tag to be discussed and voted upon:
> > > >> https://github.com/apache/age/releases/tag/PG12/v.1.1.0-rc0>> <
> > > https://github.com/apache/age/releases/tag/PG12%2Fv1.1.0-rc0>> The git
> > > commit hash:
> > > >>  commit 1d9d60197e2cf3fc48aac573278f6f9e173ee78b
> > > >> The release files for 1.1.0, can be found at:
> > > >>  https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0>> <
> > > https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0>> Signatures
> > > used for AGE RCs can be found in this file:
> > > >> https://downloads.apache.org/age/KEYS>> <
> > > https://downloads.apache.org/age/KEYS>> The fingerprint of key to sign
> > > release artifacts:
> > > >> 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
> > > >> For information about the contents of this release, see:
> > > >> https://github.com/apache/age/releases/tag/PG12/v1.1.0-rc0>> Please
> > > review that everything meets your criteria and vote accordingly.
> > > >> Please vote:
> > > >> [ ] +1 Release this package as Apache AGE 0.7.0
> > > >> [ ] 0 I won't get in the way
> > > >> [ ] -1 Do not release this package because ...
> > > >> This vote will be open for 72 hours.
> > > >> As always, thank you for your time.
> > > >> John Gemignani
> > >
> >
> --
> Muhammad *Shoaib, PhD*
> Data Scientist, Bioinformatician and AI Engineer
> PhD (Biomedical Engineering)
> Email: muhemmed.sho...@gmail.com
>

[RESULT][VOTE] Apache AGE 1.1.0 for PG12 Release

[John Gemignani]

Dear all,

The vote was successful for the Apache AGE 1.1.0 PG12 release.


Following is the vote breakdown -


There were 10 (+1) votes (6 binding and 4 non-binding), 1 (0) vote, and 0
(-1) votes.


*(+1) Binding votes:*
Eya Badal
Josh Innis
Dehowe Feng
Nick Sorrel
Jasper Blues
Pieterjan De Potter

*(+1) Non-binding votes:*
Young Seung Andrew Ko
Joe Suh
kwjeon - 신한별
Muhammad Shoaib

*(0) votes:*
Alex Kwak

VOTE thread:
https://lists.apache.org/thread/65770vjkgxsxl1obt6pb90d1hvd384qm

Regards,



John Gemignani

Re: [Discuss] Regarding renaming of Branches in AGE Repository

[John Gemignani]

Thank you Joe for your input!

Here are my general responses to your input in order of their appearance -

Github's master branch really only supports AGE for *one *version of
PostgreSQL (PG).

AGE started with PG 11, specifically PG 11.5, so the master branch is
technically AGE for PG 11.5. This really cannot change, at least not
easily. The only way would be if we had one version of AGE for all versions
of PG, *which is not trivial*. So, currently we are using branches off of
the master for these different PG versions of AGE.

The names of the current branches cannot be renamed. Once a branch is made
public, it needs to stay the way it is - no renaming or deleting. This is
because others (developers) may reference it and changing it would cause
those developers to become "unhappy". So, we cannot rename a branch. We can
only create new branches, where appropriate, with the appropriate name.
Case in point, the alpha branch for PG 12. This needs to stay named as is.
We will, however, be creating a branch for it called PG 12 that will be
used going forward.

The recent addition of AGE for PG 12 has caused us to revisit the naming of
our branches. So, we have looked at other repos and have discussed naming
conventions in previous [DISCUSS] threads and internal emails; you are
actually starting to see this with the release branch naming. Basically,
going forward, all main branches will be prefixed with *PG* and
all of their corresponding release branches with
*release/PG/* The names of the previous PG 11 release
branches will, however, remain the same while the new release branches will
be *release/PG11/*

There will, of course, be some exceptions to these naming standards, for
example, experimental branches.

Unfortunately, the only time that you will really get to see these changes
is when we either have a new version, a new release, or migrate something
from one to another. Which we will be doing with PG 12 shortly.

Hope this was helpful.

john

On Wed, Nov 30, 2022 at 8:46 PM Joe Suh  wrote:

> Hello everyone,
>
> I'm Joe (Github ID: jbiz805), one of the contributors in AGE.
>
> While I was working on the AGE readme for the past couple of months I
> couldn't help but notice questionable naming of branches in AGE repo.
> I am quite confused with the branch naming at the moment because the latest
> version is PG 12(AGE_PG12.1.0_ALPHA) and yet the Master branch dedicates to
> PG 11.
> Unlike other standalone software out there, I understand that there must be
> branches for each Postgres version for AGE, like the upcoming 13, 14, and
> 15.
> But if PG 12 is now official (as updated in *release/PG12/1.1.0*) I think
> the topics below need to be discussed.
> Also, I think the whole branch names need updates because to an outsider or
> non-developer pov, the branches seem quite unorganized.
>
> *1) Master Branch & Rename AGE_PG12.1.0_ALPHA*
> - since it's no longer Alpha, rename the alpha branch or remove the word
> alpha
> - also PG12 is the latest version for AGE, so shouldn't it be promoted to
> Master branch and PG 11 be made into a separate branch (for example,
> *AGE_PG11.1.0*)?
> - Just out of curiosity, does every GitHub repo require a master / main
> branch or can we just clearly specify branches for PG 11 and PG 12?
>
> *2) Update release notes for AGE_PG12.1.0_ALPHA (minor)*
> - currently showing Aug 11th release note, which belongs to PG 11
>
> *3) Rename PG 11 release branches *
> - right now PG 12 release branch is named *release/PG12/1.1.0*
> *-* suggestion to rename PG 11 release branches, for example,
> *release/PG11/0.6.0*, *release/PG11/0.7.0* so on)
>
> Let's discuss the topics above and see what we can do about organizing the
> branches.
>
> Best regards,
> Joe
>
>
>
>
> * Joe Suh / 서준섭*
>
> * 과장 / 마케팅전략팀*
>
> *M* : 010-5364-5357 * P* : 070-5038-5732
> *F * : 070-8677-2552
> 서울특별시 강남구 테헤란로 516 정헌빌딩 4층
> F4, 516, Teheran-ro, Gangnam-gu, Seoul, Republic of Korea
>

Re: [Discuss] Regarding renaming of Branches in AGE Repository

[John Gemignani]

I was always told (*and maybe I was told incorrectly*) that once something
was pushed to the master repository, one should only really add changes to
it - not delete it. That it was bad practice to do otherwise.

Other developers, like you and myself, generally clone the master
repository and base our work off of a local copy. I regularly sync my local
copy with the master to keep it up-to-date. If there are significant
changes (see below), that could easily cause confusion or make a mess with
rebasing. That mess can be very time consuming and frustrating to fix.
That's the "unhappy" part.

Another part of my issue, and maybe it is a bit of an overreaction, with
renaming *a remote branch*, is that it involves pushing a new branch (a
copy of the old branch) to the remote and then *deleting *the old branch on
the remote.

We had an issue, once, where a force push command was used on the remote
repository and it basically destroyed the master branch. Luckily, we had a
local copy that was current and were able to restore it. But, it was an
unpleasant experience; delete would likely be just as painful, if a mistake
were made. That is why I feel it is better to just not enter that territory.

john

On Mon, Dec 5, 2022 at 7:53 PM Joe Suh  wrote:

> Thank you John for the brief history of the naming of branches.
> I see now there are some strict rules regarding these branch names.
> I'm not quite sure exactly why or how developers will be 'unhappy' with the
> change,
> but since you already discussed this matter, I guess the branch names are
> set in stone.
>
> Aside from the branch names, I would also like to point out that the
> release notes for PG 12 branches (both alpha and release) are not updated
> yet.
> The latest release notes show August 11th, which I think is a release note
> for PG11.
> I would like to suggest at least updating that info by the end of this
> discussion.
>
>
>
>
> * Joe Suh / 서준섭*
>
> * 과장 / 마케팅전략팀*
>
> *M* : 010-5364-5357 * P* : 070-5038-5732
> *F * : 070-8677-2552
> 서울특별시 강남구 테헤란로 516 정헌빌딩 4층
> F4, 516, Teheran-ro, Gangnam-gu, Seoul, Republic of Korea
>
>
> 2022년 12월 2일 (금) 오전 4:11, John Gemignani 님이
> 작성:
>
> > Thank you Joe for your input!
> >
> > Here are my general responses to your input in order of their appearance
> -
> >
> > Github's master branch really only supports AGE for *one *version of
> > PostgreSQL (PG).
> >
> > AGE started with PG 11, specifically PG 11.5, so the master branch is
> > technically AGE for PG 11.5. This really cannot change, at least not
> > easily. The only way would be if we had one version of AGE for all
> versions
> > of PG, *which is not trivial*. So, currently we are using branches off of
> > the master for these different PG versions of AGE.
> >
> > The names of the current branches cannot be renamed. Once a branch is
> made
> > public, it needs to stay the way it is - no renaming or deleting. This is
> > because others (developers) may reference it and changing it would cause
> > those developers to become "unhappy". So, we cannot rename a branch. We
> can
> > only create new branches, where appropriate, with the appropriate name.
> > Case in point, the alpha branch for PG 12. This needs to stay named as
> is.
> > We will, however, be creating a branch for it called PG 12 that will be
> > used going forward.
> >
> > The recent addition of AGE for PG 12 has caused us to revisit the naming
> of
> > our branches. So, we have looked at other repos and have discussed naming
> > conventions in previous [DISCUSS] threads and internal emails; you are
> > actually starting to see this with the release branch naming. Basically,
> > going forward, all main branches will be prefixed with *PG* and
> > all of their corresponding release branches with
> > *release/PG/* The names of the previous PG 11 release
> > branches will, however, remain the same while the new release branches
> will
> > be *release/PG11/*
> >
> > There will, of course, be some exceptions to these naming standards, for
> > example, experimental branches.
> >
> > Unfortunately, the only time that you will really get to see these
> changes
> > is when we either have a new version, a new release, or migrate something
> > from one to another. Which we will be doing with PG 12 shortly.
> >
> > Hope this was helpful.
> >
> > john
> >
> > On Wed, Nov 30, 2022 at 8:46 PM Joe Suh  wrote:
> >
> > > Hello everyone,
> > >
> > > I'm Joe (Github ID: jbiz805), one of the contributors in AGE.
> > >
> > > While I was working 

Re: [Discuss] Regarding renaming of Branches in AGE Repository

[John Gemignani]

" Aside from the branch names, I would also like to point out that the
release notes for PG 12 branches (both alpha and release) are not updated
yet.
The latest release notes show August 11th, which I think is a release note
for PG11.
I would like to suggest at least updating that info by the end of this
discussion."

I need to clarify what you mean by release branches? Can you link the
release notes that you are referring to?

john

On Thu, Dec 8, 2022 at 4:09 PM John Gemignani 
wrote:

> I was always told (*and maybe I was told incorrectly*) that once
> something was pushed to the master repository, one should only really add
> changes to it - not delete it. That it was bad practice to do otherwise.
>
> Other developers, like you and myself, generally clone the master
> repository and base our work off of a local copy. I regularly sync my local
> copy with the master to keep it up-to-date. If there are significant
> changes (see below), that could easily cause confusion or make a mess with
> rebasing. That mess can be very time consuming and frustrating to fix.
> That's the "unhappy" part.
>
> Another part of my issue, and maybe it is a bit of an overreaction, with
> renaming *a remote branch*, is that it involves pushing a new branch (a
> copy of the old branch) to the remote and then *deleting *the old branch
> on the remote.
>
> We had an issue, once, where a force push command was used on the remote
> repository and it basically destroyed the master branch. Luckily, we had a
> local copy that was current and were able to restore it. But, it was an
> unpleasant experience; delete would likely be just as painful, if a mistake
> were made. That is why I feel it is better to just not enter that territory.
>
> john
>
> On Mon, Dec 5, 2022 at 7:53 PM Joe Suh  wrote:
>
>> Thank you John for the brief history of the naming of branches.
>> I see now there are some strict rules regarding these branch names.
>> I'm not quite sure exactly why or how developers will be 'unhappy' with
>> the
>> change,
>> but since you already discussed this matter, I guess the branch names are
>> set in stone.
>>
>> Aside from the branch names, I would also like to point out that the
>> release notes for PG 12 branches (both alpha and release) are not updated
>> yet.
>> The latest release notes show August 11th, which I think is a release note
>> for PG11.
>> I would like to suggest at least updating that info by the end of this
>> discussion.
>>
>>
>>
>>
>> * Joe Suh / 서준섭*
>>
>> * 과장 / 마케팅전략팀*
>>
>> *M* : 010-5364-5357 * P* : 070-5038-5732
>> *F * : 070-8677-2552
>> 서울특별시 강남구 테헤란로 516 정헌빌딩 4층
>> F4, 516, Teheran-ro, Gangnam-gu, Seoul, Republic of Korea
>>
>>
>> 2022년 12월 2일 (금) 오전 4:11, John Gemignani 님이
>> 작성:
>>
>> > Thank you Joe for your input!
>> >
>> > Here are my general responses to your input in order of their
>> appearance -
>> >
>> > Github's master branch really only supports AGE for *one *version of
>> > PostgreSQL (PG).
>> >
>> > AGE started with PG 11, specifically PG 11.5, so the master branch is
>> > technically AGE for PG 11.5. This really cannot change, at least not
>> > easily. The only way would be if we had one version of AGE for all
>> versions
>> > of PG, *which is not trivial*. So, currently we are using branches off
>> of
>> > the master for these different PG versions of AGE.
>> >
>> > The names of the current branches cannot be renamed. Once a branch is
>> made
>> > public, it needs to stay the way it is - no renaming or deleting. This
>> is
>> > because others (developers) may reference it and changing it would cause
>> > those developers to become "unhappy". So, we cannot rename a branch. We
>> can
>> > only create new branches, where appropriate, with the appropriate name.
>> > Case in point, the alpha branch for PG 12. This needs to stay named as
>> is.
>> > We will, however, be creating a branch for it called PG 12 that will be
>> > used going forward.
>> >
>> > The recent addition of AGE for PG 12 has caused us to revisit the
>> naming of
>> > our branches. So, we have looked at other repos and have discussed
>> naming
>> > conventions in previous [DISCUSS] threads and internal emails; you are
>> > actually starting to see this with the release branch naming. Basically,
>> > going forward, all main branches will be prefixed with *PG* and
>> > all of their corresponding rel

Re: [Discuss] Regarding renaming of Branches in AGE Repository

[John Gemignani]

The release notes in any branch named release/, are basically
frozen to when that release branch was created. Think of the releases as
snapshots, they won't change, once created.

The alpha PG12 branch that release/PG12/1.1.0 is based off of is the
release/1.1.0 branch (PG 11). That is why the release notes are the same.

FYI, to avoid confusion in the future, the next release for PG11 will be
release/PG11/ Basically, release/PG/

Hope this is helpful.

john

On Thu, Dec 8, 2022 at 4:27 PM Joe Suh  wrote:

> "Other developers, like you and myself, generally clone the master
> repository and base our work off of a local copy. I regularly sync my local
> copy with the master to keep it up-to-date. If there are significant
> changes (see below), that could easily cause confusion or make a mess with
> rebasing. That mess can be very time-consuming and frustrating to fix.
> That's the "unhappy" part."
>
> I'm not a developer, but I guess I get that part now.
> Thanks for clearing that up.
>
> The release branch I was talking about was
> https://github.com/apache/age/tree/release/PG12/1.1.0
> Also refer to https://github.com/apache/age/tree/AGE_PG12.1.0_ALPHA (alpha
> branch)
>
> These two branches have Aug 11th release notes as 'Latest'.
> I believe this is a release note for PG11.
> Although I see no differences between the release notes for Aug 11th and
> Oct 26th,
> Oct 26th states it's a release note for PG12, hence why I suggested the two
> branches be updated.
>
> Joe
>
>
>
>
> * Joe Suh / 서준섭*
>
> * 과장 / 마케팅전략팀*
>
> *M* : 010-5364-5357 * P* : 070-5038-5732
> *F * : 070-8677-2552
> 서울특별시 강남구 테헤란로 516 정헌빌딩 4층
> F4, 516, Teheran-ro, Gangnam-gu, Seoul, Republic of Korea
>
>
> 2022년 12월 9일 (금) 오전 9:12, John Gemignani 님이
> 작성:
>
> > " Aside from the branch names, I would also like to point out that the
> > release notes for PG 12 branches (both alpha and release) are not updated
> > yet.
> > The latest release notes show August 11th, which I think is a release
> note
> > for PG11.
> > I would like to suggest at least updating that info by the end of this
> > discussion."
> >
> > I need to clarify what you mean by release branches? Can you link the
> > release notes that you are referring to?
> >
> > john
> >
> > On Thu, Dec 8, 2022 at 4:09 PM John Gemignani <
> john.gemign...@bitnine.net>
> > wrote:
> >
> > > I was always told (*and maybe I was told incorrectly*) that once
> > > something was pushed to the master repository, one should only really
> add
> > > changes to it - not delete it. That it was bad practice to do
> otherwise.
> > >
> > > Other developers, like you and myself, generally clone the master
> > > repository and base our work off of a local copy. I regularly sync my
> > local
> > > copy with the master to keep it up-to-date. If there are significant
> > > changes (see below), that could easily cause confusion or make a mess
> > with
> > > rebasing. That mess can be very time consuming and frustrating to fix.
> > > That's the "unhappy" part.
> > >
> > > Another part of my issue, and maybe it is a bit of an overreaction,
> with
> > > renaming *a remote branch*, is that it involves pushing a new branch (a
> > > copy of the old branch) to the remote and then *deleting *the old
> branch
> > > on the remote.
> > >
> > > We had an issue, once, where a force push command was used on the
> remote
> > > repository and it basically destroyed the master branch. Luckily, we
> had
> > a
> > > local copy that was current and were able to restore it. But, it was an
> > > unpleasant experience; delete would likely be just as painful, if a
> > mistake
> > > were made. That is why I feel it is better to just not enter that
> > territory.
> > >
> > > john
> > >
> > > On Mon, Dec 5, 2022 at 7:53 PM Joe Suh  wrote:
> > >
> > >> Thank you John for the brief history of the naming of branches.
> > >> I see now there are some strict rules regarding these branch names.
> > >> I'm not quite sure exactly why or how developers will be 'unhappy'
> with
> > >> the
> > >> change,
> > >> but since you already discussed this matter, I guess the branch names
> > are
> > >> set in stone.
> > >>
> > >> Aside from the branch names, I would also like to point out that the
> > >> release notes for PG 12 bra

[DISCUSS] Apache AGE 1.2.0 Release for PostgreSQL 11

[John Gemignani]

Dear Apache Community,


We would like to discuss the Apache AGE release 1.2.0 for PostgreSQL 11



To learn more about Apache AGE, please see http://age.apache.org/



Included and addressed in this release:


Fix Python driver (#388).
Patch to apply PR (#203) - typos and incorrect hash init.
Update SET clause to support assigning a map (#468).
Fix WHERE clause wrong Expr bug (#339).
Fix multiple typos (#470).
Updated the volatility category (from STABLE to IMMUTABLE) of multiple
functions.
Graph naming convention now aligns with Cypher spec. (#349).
Fixed README typos (#436).
Create graph instruction fixed (#414).
Readme added for JDBC driver (#383).
Regression tests added (#341).
Regression tests added (#336).
Updated Python driver Readme for clarity.
Fixed compare_agtype_scalar to only return 1, 0, or -1.
Created complete graph function (#342).
Fix Travis CI warning messages.
Updated Golang version to 1.19 (#373).
Fixed NULL pointer on name compare (#376).
Multiple updates to the README.md file.
Implemented CI testing for Golang Driver (#372).
Modify the Python driver's parameterization.
Added license header to new files that it was missing from.
Modify the Golang driver's usage of parameterization.
Added the ability to pass PostgreSQL parameters to the cypher function
(specifically for drivers).
Use Debian Buster base image (#243).
Updated the CONTRIBUTING.md file (#348).
Invalid labels now return NULL instead of erroring out.
Removed incubating from overlooked files.
Fixed Golang driver module.
Removed DISCLAIMER file.
Fixed bug in delete_global_graphs.
Fixed EXPLAIN to allow for nested cypher commands.
Fixed bug with Call, YIELD clause ignores WHERE.
Graph names with empty string '' are now disallowed (#251).
Implement CALL YIELD for cypher functions.
Update NOTICE file.


*



The git tag to be discussed and voted upon:

https://github.com/apache/age/releases/tag/PG11%2Fv1.2.0-rc0


The git commit hash:

  commit 67cb875d2326a257ace8f47622988fdae2332eb1



The release files for 1.2.0, can be found at:

https://dist.apache.org/repos/dist/dev/age/PG11/1.2.0.rc0/



Signatures used for AGE RCs can be found in this file:

https://downloads.apache.org/age/KEYS
<https://downloads.apache.org/age/KEYS>



The fingerprint of key to sign release artifacts:

4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045



For information about the contents of this release, see:

https://github.com/apache/age/releases/tag/PG11%2Fv1.2.0-rc0



Please share your thoughts and feedback and let us know if we can call for

a vote.

Thank you,
John Gemignani

[DISCUSS] Apache AGE 1.1.1 Release for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

We would like to discuss the Apache AGE release 1.1.1 for PostgreSQL 12

To learn more about Apache AGE, please see http://age.apache.org/

Included and addressed in this release:

Issue (#318): PGXN Support added. (#367)
Add the ability to pass parameters to the cypher function.
Modify the python and go driver's parameterization.
Fix compare_agtype_scalar_values returned result.
Implement CI testing for Golang Driver (#372).
Update to go version 1.19, as 1.16 is EOL (#373).
Issue #388 - Fix python driver build from source (#389).
Updated README.md

*

The git tag to be discussed and voted upon:
https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc0

The git commit hash:
commit 8b8ad5fe0e30d8a3b6cdb3cfbeca1a3bb9df9c40

The release files for 1.1.1, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG12/1.1.1.rc0/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release, see:
https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc0

Please share your thoughts and feedback and let us know if we can call for
a vote.

Thank you,
John Gemignani

Re: [DISCUSS] Apache AGE 1.1.1 Release for PostgreSQL 12

[John Gemignani]

I am closing the discussion due to a few overlooked files. Once these are
corrected, I will reopen it.

Thank you all for your time!

john

On Wed, Jan 18, 2023 at 11:28 PM Dehowe Feng 
wrote:

> These changes are exciting for AGE. Looking forward what comes next.
>
> On Thu, Jan 19, 2023 at 8:31 AM John Gemignani  >
> wrote:
>
> > Dear Apache Community,
> >
> > We would like to discuss the Apache AGE release 1.1.1 for PostgreSQL 12
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > Included and addressed in this release:
> >
> > Issue (#318): PGXN Support added. (#367)
> > Add the ability to pass parameters to the cypher function.
> > Modify the python and go driver's parameterization.
> > Fix compare_agtype_scalar_values returned result.
> > Implement CI testing for Golang Driver (#372).
> > Update to go version 1.19, as 1.16 is EOL (#373).
> > Issue #388 - Fix python driver build from source (#389).
> > Updated README.md
> >
> > *
> >
> > The git tag to be discussed and voted upon:
> > https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc0
> >
> > The git commit hash:
> > commit 8b8ad5fe0e30d8a3b6cdb3cfbeca1a3bb9df9c40
> >
> > The release files for 1.1.1, can be found at:
> > https://dist.apache.org/repos/dist/dev/age/PG12/1.1.1.rc0/
> >
> > Signatures used for AGE RCs can be found in this file:
> > https://downloads.apache.org/age/KEYS
> >
> > The fingerprint of key to sign release artifacts:
> > 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
> >
> > For information about the contents of this release, see:
> > https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc0
> >
> > Please share your thoughts and feedback and let us know if we can call
> for
> > a vote.
> >
> > Thank you,
> > John Gemignani
> >
>

[DISCUSS] Apache AGE 1.1.1 Release for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

We would like to discuss (reopen) the Apache AGE release 1.1.1 for
PostgreSQL 12

To learn more about Apache AGE, please see http://age.apache.org/

Included and addressed in this release:

Upgrade script from AGE for PG12 1.1.0 to 1.1.1
Issue (#318): PGXN Support added. (#367)
Add the ability to pass parameters to the cypher function.
Modify the python driver's parameterization.
Modify the go driver's parameterization.
Fix compare_agtype_scalar_values returned result.
Implement CI testing for Golang Driver (#372).
Update to go version 1.19, as 1.16 is EOL (#373).
Issue #388 - Fix python driver build from source (#389).
Updated README.md

*

The git tag to be discussed and voted upon:
https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1

The git commit hash:
commit 2f85a37f781e8f7a1112aa36e0812d9c3a50d971

The release files for 1.1.1, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG12/1.1.1.rc1/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release, see:
https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1

Please share your thoughts and feedback and let us know if we can call for
a vote.

Thank you,
John Gemignani

Re: [DISCUSS] Apache AGE 1.1.1 Release for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

Since there are no objections, I am closing the DISCUSS thread and will
open the official vote for Apache AGE 1.1.1 for PostgreSQL 12 shortly.

Best regards,


John


On Wed, Jan 25, 2023 at 5:14 PM Dehowe Feng  wrote:

> This release brings some much needed additions to AGE. Great job to
> everyone involved.
>
>
> On Thu, Jan 26, 2023 at 7:05 AM Eya Badal  wrote:
>
> > Looks good to me.
> >
> > I checked the following:
> >
> > - Signature and hash - check.
> > - LICENSE and NOTICE - check.
> > - No unexpected binary files - check.
> >
> > Great Job!!
> >
> > Best,
> > Eya
> >
> > On 2023/01/20 00:52:50 John Gemignani wrote:
> > > Dear Apache Community,
> > >
> > > We would like to discuss (reopen) the Apache AGE release 1.1.1 for
> > > PostgreSQL 12
> > >
> > > To learn more about Apache AGE, please see http://age.apache.org/
> > >
> > > Included and addressed in this release:
> > >
> > > Upgrade script from AGE for PG12 1.1.0 to 1.1.1
> > > Issue (#318): PGXN Support added. (#367)
> > > Add the ability to pass parameters to the cypher function.
> > > Modify the python driver's parameterization.
> > > Modify the go driver's parameterization.
> > > Fix compare_agtype_scalar_values returned result.
> > > Implement CI testing for Golang Driver (#372).
> > > Update to go version 1.19, as 1.16 is EOL (#373).
> > > Issue #388 - Fix python driver build from source (#389).
> > > Updated README.md
> > >
> > > *
> > >
> > > The git tag to be discussed and voted upon:
> > > https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1
> > >
> > > The git commit hash:
> > > commit 2f85a37f781e8f7a1112aa36e0812d9c3a50d971
> > >
> > > The release files for 1.1.1, can be found at:
> > > https://dist.apache.org/repos/dist/dev/age/PG12/1.1.1.rc1/
> > >
> > > Signatures used for AGE RCs can be found in this file:
> > > https://downloads.apache.org/age/KEYS
> > >
> > > The fingerprint of key to sign release artifacts:
> > > 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
> > >
> > > For information about the contents of this release, see:
> > > https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1
> > >
> > > Please share your thoughts and feedback and let us know if we can call
> > for
> > > a vote.
> > >
> > > Thank you,
> > > John Gemignani
> > >
> >
>

Re: [DISCUSS] Apache AGE 1.2.0 Release for PostgreSQL 11

[John Gemignani]

Dear Apache Community,

Since there are no objections, I am closing the DISCUSS thread and will
open the official vote for Apache AGE 1.2.0 for PostgreSQL 11 shortly.

Best regards,


John


On Tue, Jan 17, 2023 at 9:37 AM Eya Badal  wrote:

> Looks good to me.
>
> I checked the following:
>
> - Signature and hash - check.
> - LICENSE and NOTICE - check.
> - No unexpected binary files - check.
>
> Great Job!!
>
> Best,
> Eya
>
> On 2023/01/13 23:58:30 John Gemignani wrote:
> > Dear Apache Community,
> >
> >
> > We would like to discuss the Apache AGE release 1.2.0 for PostgreSQL 11
> >
> >
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> >
> >
> > Included and addressed in this release:
> >
> >
> > Fix Python driver (#388).
> > Patch to apply PR (#203) - typos and incorrect hash init.
> > Update SET clause to support assigning a map (#468).
> > Fix WHERE clause wrong Expr bug (#339).
> > Fix multiple typos (#470).
> > Updated the volatility category (from STABLE to IMMUTABLE) of
> multiple
> > functions.
> > Graph naming convention now aligns with Cypher spec. (#349).
> > Fixed README typos (#436).
> > Create graph instruction fixed (#414).
> > Readme added for JDBC driver (#383).
> > Regression tests added (#341).
> > Regression tests added (#336).
> > Updated Python driver Readme for clarity.
> > Fixed compare_agtype_scalar to only return 1, 0, or -1.
> > Created complete graph function (#342).
> > Fix Travis CI warning messages.
> > Updated Golang version to 1.19 (#373).
> > Fixed NULL pointer on name compare (#376).
> > Multiple updates to the README.md file.
> > Implemented CI testing for Golang Driver (#372).
> > Modify the Python driver's parameterization.
> > Added license header to new files that it was missing from.
> > Modify the Golang driver's usage of parameterization.
> > Added the ability to pass PostgreSQL parameters to the cypher
> function
> > (specifically for drivers).
> > Use Debian Buster base image (#243).
> > Updated the CONTRIBUTING.md file (#348).
> > Invalid labels now return NULL instead of erroring out.
> > Removed incubating from overlooked files.
> > Fixed Golang driver module.
> > Removed DISCLAIMER file.
> > Fixed bug in delete_global_graphs.
> > Fixed EXPLAIN to allow for nested cypher commands.
> > Fixed bug with Call, YIELD clause ignores WHERE.
> > Graph names with empty string '' are now disallowed (#251).
> > Implement CALL YIELD for cypher functions.
> > Update NOTICE file.
> >
> >
> > *
> >
> >
> >
> > The git tag to be discussed and voted upon:
> >
> > https://github.com/apache/age/releases/tag/PG11%2Fv1.2.0-rc0
> >
> >
> > The git commit hash:
> >
> >   commit 67cb875d2326a257ace8f47622988fdae2332eb1
> >
> >
> >
> > The release files for 1.2.0, can be found at:
> >
> > https://dist.apache.org/repos/dist/dev/age/PG11/1.2.0.rc0/
> >
> >
> >
> > Signatures used for AGE RCs can be found in this file:
> >
> > https://downloads.apache.org/age/KEYS
> > <https://downloads.apache.org/age/KEYS>
> >
> >
> >
> > The fingerprint of key to sign release artifacts:
> >
> > 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
> >
> >
> >
> > For information about the contents of this release, see:
> >
> > https://github.com/apache/age/releases/tag/PG11%2Fv1.2.0-rc0
> >
> >
> >
> > Please share your thoughts and feedback and let us know if we can call
> for
> >
> > a vote.
> >
> > Thank you,
> > John Gemignani
> >
>

[VOTE] Apache AGE 1.2.0 Release for PostgreSQL 11

[John Gemignani]

Dear Apache Community,

This is an official vote for the Apache AGE 1.2.0 Release for PostgreSQL 11.

To learn more about Apache AGE, please see http://age.apache.org/

Included and addressed in this release:

Fix Python driver (#388).
Patch to apply PR (#203) - typos and incorrect hash init.
Update SET clause to support assigning a map (#468).
Fix WHERE clause wrong Expr bug (#339).
Fix multiple typos (#470).
Updated the volatility category (from STABLE to IMMUTABLE) of multiple
functions.
Graph naming convention now aligns with Cypher spec. (#349).
Fixed README typos (#436).
Create graph instruction fixed (#414).
Readme added for JDBC driver (#383).
Regression tests added (#341).
Regression tests added (#336).
Updated Python driver Readme for clarity.
Fixed compare_agtype_scalar to only return 1, 0, or -1.
Created complete graph function (#342).
Fix Travis CI warning messages.
Updated Golang version to 1.19 (#373).
Fixed NULL pointer on name compare (#376).
Multiple updates to the README.md file.
Implemented CI testing for Golang Driver (#372).
Modify the Python driver's parameterization.
Added license header to new files that it was missing from.
Modify the Golang driver's usage of parameterization.
Added the ability to pass PostgreSQL parameters to the cypher function
(specifically for drivers).
Use Debian Buster base image (#243).
Updated the CONTRIBUTING.md file (#348).
Invalid labels now return NULL instead of erroring out.
Removed incubating from overlooked files.
Fixed Golang driver module.
Removed DISCLAIMER file.
Fixed bug in delete_global_graphs.
Fixed EXPLAIN to allow for nested cypher commands.
Fixed bug with Call, YIELD clause ignores WHERE.
Graph names with empty string '' are now disallowed (#251).
Implement CALL YIELD for cypher functions.
Update NOTICE file.

*

The git tag to be discussed and voted upon:
https://github.com/apache/age/releases/tag/PG11%2Fv1.2.0-rc0

The git commit hash:
commit 67cb875d2326a257ace8f47622988fdae2332eb1

The release files for 1.2.0, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG11/1.2.0.rc0/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release, see:
https://github.com/apache/age/releases/tag/PG11%2Fv1.2.0-rc0

Please vote (if you are a binding vote, please state it):

[ ] +1 Release this package as Apache AGE 1.2.0 for PostgreSQL 11

[ ] 0 I won't get in the way

[ ] -1 Do not release this package because ...


This vote will be open for 72 hours.

Thank you,

John Gemignani

[VOTE] Apache AGE Release 1.1.1 for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

This is an official vote for the Apache AGE Release 1.1.1 for PostgreSQL 12.

To learn more about Apache AGE, please see http://age.apache.org/

Included and addressed in this release:

Upgrade script from AGE for PG12 1.1.0 to 1.1.1
Issue (#318): PGXN Support added. (#367)
Add the ability to pass parameters to the cypher function.
Modify the python driver's parameterization.
Modify the go driver's parameterization.
Fix compare_agtype_scalar_values returned result.
Implement CI testing for Golang Driver (#372).
Update to go version 1.19, as 1.16 is EOL (#373).
Issue #388 - Fix python driver build from source (#389).
Updated README.md

*

The git tag to be discussed and voted upon:
https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1

The git commit hash:
commit 2f85a37f781e8f7a1112aa36e0812d9c3a50d971

The release files for 1.1.1, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG12/1.1.1.rc1/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release, see:
https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1

Please vote (if you are a binding vote, please state it):

[ ] +1 Release this package as Apache AGE 1.2.0 for PostgreSQL 11
[ ] 0 I won't get in the way
[ ] -1 Do not release this package because ...


This vote will be open for 72 hours.

Thank you,

John Gemignani

Re: [VOTE] Apache AGE Release 1.1.1 for PostgreSQL 12

[John Gemignani]

Canceling this vote due to some typos. Will be reissuing momentarily.

john

On Thu, Jan 26, 2023 at 1:10 PM John Gemignani 
wrote:

> Dear Apache Community,
>
> This is an official vote for the Apache AGE Release 1.1.1 for PostgreSQL
> 12.
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
> Included and addressed in this release:
>
> Upgrade script from AGE for PG12 1.1.0 to 1.1.1
> Issue (#318): PGXN Support added. (#367)
> Add the ability to pass parameters to the cypher function.
> Modify the python driver's parameterization.
> Modify the go driver's parameterization.
> Fix compare_agtype_scalar_values returned result.
> Implement CI testing for Golang Driver (#372).
> Update to go version 1.19, as 1.16 is EOL (#373).
> Issue #388 - Fix python driver build from source (#389).
> Updated README.md
>
> *
>
> The git tag to be discussed and voted upon:
> https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1
>
> The git commit hash:
> commit 2f85a37f781e8f7a1112aa36e0812d9c3a50d971
>
> The release files for 1.1.1, can be found at:
> https://dist.apache.org/repos/dist/dev/age/PG12/1.1.1.rc1/
>
> Signatures used for AGE RCs can be found in this file:
> https://downloads.apache.org/age/KEYS
>
> The fingerprint of key to sign release artifacts:
> 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
>
> For information about the contents of this release, see:
> https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1
>
> Please vote (if you are a binding vote, please state it):
>
> [ ] +1 Release this package as Apache AGE 1.2.0 for PostgreSQL 11
> [ ] 0 I won't get in the way
> [ ] -1 Do not release this package because ...
>
>
> This vote will be open for 72 hours.
>
> Thank you,
>
> John Gemignani
>

[VOTE] Apache AGE Release 1.1.1 for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

This is an official *RE-ISSUED* vote for the Apache AGE Release 1.1.1 for
PostgreSQL 12.

To learn more about Apache AGE, please see http://age.apache.org/

Included and addressed in this release:

Upgrade script from AGE for PG12 1.1.0 to 1.1.1
Issue (#318): PGXN Support added. (#367)
Add the ability to pass parameters to the cypher function.
Modify the python driver's parameterization.
Modify the go driver's parameterization.
Fix compare_agtype_scalar_values returned result.
Implement CI testing for Golang Driver (#372).
Update to go version 1.19, as 1.16 is EOL (#373).
Issue #388 - Fix python driver build from source (#389).
Updated README.md

*

The git tag to be discussed and voted upon:
https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1

The git commit hash:
commit 2f85a37f781e8f7a1112aa36e0812d9c3a50d971

The release files for 1.1.1, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG12/1.1.1.rc1/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release, see:
https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1

Please vote (if you are a binding vote, please state it):

[ ] +1 Release this package as Apache AGE 1.1.1 for PostgreSQL 12
[ ] 0 I won't get in the way
[ ] -1 Do not release this package because ...


This vote will be open for 72 hours.

Thank you,

John Gemignani

Re: [VOTE] Apache AGE Release 1.1.1 for PostgreSQL 12

[John Gemignani]

Dear all,

This is a canceled release thread, your votes will not count here. Please
vote in the latest thread for PG12.

Thanks!

John

On Fri, Jan 27, 2023 at 8:37 AM Dehowe Feng  wrote:

> +1 (binding)
>
> On Fri, Jan 27, 2023 at 4:23 PM Pieterjan De Potter
>  wrote:
>
> > +1
> >
> > On 26/01/2023 22:10, John Gemignani wrote:
> > > Dear Apache Community,
> > >
> > > This is an official vote for the Apache AGE Release 1.1.1 for
> PostgreSQL
> > 12.
> > >
> > > To learn more about Apache AGE, please see http://age.apache.org/>>
> > > Included and addressed in this release:
> > >
> > > Upgrade script from AGE for PG12 1.1.0 to 1.1.1
> > > Issue (#318): PGXN Support added. (#367)
> > > Add the ability to pass parameters to the cypher function.
> > > Modify the python driver's parameterization.
> > > Modify the go driver's parameterization.
> > > Fix compare_agtype_scalar_values returned result.
> > > Implement CI testing for Golang Driver (#372).
> > > Update to go version 1.19, as 1.16 is EOL (#373).
> > > Issue #388 - Fix python driver build from source (#389).
> > > Updated README.md
> > >
> > > *
> > >
> > > The git tag to be discussed and voted upon:
> > > https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1>>
> > > The git commit hash:
> > > commit 2f85a37f781e8f7a1112aa36e0812d9c3a50d971
> > >
> > > The release files for 1.1.1, can be found at:
> > > https://dist.apache.org/repos/dist/dev/age/PG12/1.1.1.rc1/>>
> > > Signatures used for AGE RCs can be found in this file:
> > > https://downloads.apache.org/age/KEYS>>
> > > The fingerprint of key to sign release artifacts:
> > > 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
> > >
> > > For information about the contents of this release, see:
> > > https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1>>
> > > Please vote (if you are a binding vote, please state it):
> > >
> > > [ ] +1 Release this package as Apache AGE 1.2.0 for PostgreSQL 11
> > > [ ] 0 I won't get in the way
> > > [ ] -1 Do not release this package because ...
> > >
> > >
> > > This vote will be open for 72 hours.
> > >
> > > Thank you,
> > >
> > > John Gemignani
> > >
> >
> >
>

Re: [VOTE] Apache AGE 1.2.0 Release for PostgreSQL 11

[John Gemignani]

We would like to thank everyone who participated in the voting process and
are now closing this vote and will be sending out the results shortly.

John Gemignani

On Mon, Jan 30, 2023 at 8:03 AM Eya Badal  wrote:

> +1 (Binding)
>
> Checked the following:
>
> - Signature and hash - check.
> - LICENSE and NOTICE - check.
> - No unexpected binary files - check.
>
> Great Job!!
>
>
> On 2023/01/26 21:05:37 John Gemignani wrote:
> > Dear Apache Community,
> >
> > This is an official vote for the Apache AGE 1.2.0 Release for PostgreSQL
> 11.
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > Included and addressed in this release:
> >
> > Fix Python driver (#388).
> > Patch to apply PR (#203) - typos and incorrect hash init.
> > Update SET clause to support assigning a map (#468).
> > Fix WHERE clause wrong Expr bug (#339).
> > Fix multiple typos (#470).
> > Updated the volatility category (from STABLE to IMMUTABLE) of
> multiple
> > functions.
> > Graph naming convention now aligns with Cypher spec. (#349).
> > Fixed README typos (#436).
> > Create graph instruction fixed (#414).
> > Readme added for JDBC driver (#383).
> > Regression tests added (#341).
> > Regression tests added (#336).
> > Updated Python driver Readme for clarity.
> > Fixed compare_agtype_scalar to only return 1, 0, or -1.
> > Created complete graph function (#342).
> > Fix Travis CI warning messages.
> > Updated Golang version to 1.19 (#373).
> > Fixed NULL pointer on name compare (#376).
> > Multiple updates to the README.md file.
> > Implemented CI testing for Golang Driver (#372).
> > Modify the Python driver's parameterization.
> > Added license header to new files that it was missing from.
> > Modify the Golang driver's usage of parameterization.
> > Added the ability to pass PostgreSQL parameters to the cypher
> function
> > (specifically for drivers).
> > Use Debian Buster base image (#243).
> > Updated the CONTRIBUTING.md file (#348).
> > Invalid labels now return NULL instead of erroring out.
> > Removed incubating from overlooked files.
> > Fixed Golang driver module.
> > Removed DISCLAIMER file.
> > Fixed bug in delete_global_graphs.
> > Fixed EXPLAIN to allow for nested cypher commands.
> > Fixed bug with Call, YIELD clause ignores WHERE.
> > Graph names with empty string '' are now disallowed (#251).
> > Implement CALL YIELD for cypher functions.
> > Update NOTICE file.
> >
> > *
> >
> > The git tag to be discussed and voted upon:
> > https://github.com/apache/age/releases/tag/PG11%2Fv1.2.0-rc0
> >
> > The git commit hash:
> > commit 67cb875d2326a257ace8f47622988fdae2332eb1
> >
> > The release files for 1.2.0, can be found at:
> > https://dist.apache.org/repos/dist/dev/age/PG11/1.2.0.rc0/
> >
> > Signatures used for AGE RCs can be found in this file:
> > https://downloads.apache.org/age/KEYS
> >
> > The fingerprint of key to sign release artifacts:
> > 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
> >
> > For information about the contents of this release, see:
> > https://github.com/apache/age/releases/tag/PG11%2Fv1.2.0-rc0
> >
> > Please vote (if you are a binding vote, please state it):
> >
> > [ ] +1 Release this package as Apache AGE 1.2.0 for PostgreSQL 11
> >
> > [ ] 0 I won't get in the way
> >
> > [ ] -1 Do not release this package because ...
> >
> >
> > This vote will be open for 72 hours.
> >
> > Thank you,
> >
> > John Gemignani
> >
>

Re: [VOTE] Apache AGE Release 1.1.1 for PostgreSQL 12

[John Gemignani]

We would like to thank everyone who participated in the voting process and
are now closing this vote and will be sending out the results shortly.

John Gemignani

On Mon, Jan 30, 2023 at 8:01 AM Eya Badal  wrote:

> +1 (Binding)
>
> Checked the following:
>
> - Signature and hash - check.
> - LICENSE and NOTICE - check.
> - No unexpected binary files - check.
>
> Great Job!!
>
>
>
>
> On 2023/01/26 21:14:24 John Gemignani wrote:
> > Dear Apache Community,
> >
> > This is an official *RE-ISSUED* vote for the Apache AGE Release 1.1.1 for
> > PostgreSQL 12.
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > Included and addressed in this release:
> >
> > Upgrade script from AGE for PG12 1.1.0 to 1.1.1
> > Issue (#318): PGXN Support added. (#367)
> > Add the ability to pass parameters to the cypher function.
> > Modify the python driver's parameterization.
> > Modify the go driver's parameterization.
> > Fix compare_agtype_scalar_values returned result.
> > Implement CI testing for Golang Driver (#372).
> > Update to go version 1.19, as 1.16 is EOL (#373).
> > Issue #388 - Fix python driver build from source (#389).
> > Updated README.md
> >
> > *
> >
> > The git tag to be discussed and voted upon:
> > https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1
> >
> > The git commit hash:
> > commit 2f85a37f781e8f7a1112aa36e0812d9c3a50d971
> >
> > The release files for 1.1.1, can be found at:
> > https://dist.apache.org/repos/dist/dev/age/PG12/1.1.1.rc1/
> >
> > Signatures used for AGE RCs can be found in this file:
> > https://downloads.apache.org/age/KEYS
> >
> > The fingerprint of key to sign release artifacts:
> > 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
> >
> > For information about the contents of this release, see:
> > https://github.com/apache/age/releases/tag/PG12/v1.1.1-rc1
> >
> > Please vote (if you are a binding vote, please state it):
> >
> > [ ] +1 Release this package as Apache AGE 1.1.1 for PostgreSQL 12
> > [ ] 0 I won't get in the way
> > [ ] -1 Do not release this package because ...
> >
> >
> > This vote will be open for 72 hours.
> >
> > Thank you,
> >
> > John Gemignani
> >
>

[RESULT][VOTE] Apache AGE 1.2.0 Release for PostgreSQL 11

[John Gemignani]

Dear Apache Community,

The vote successfully passed with 5, +1 (binding) votes and 3, +1
(non-binding votes). There were no -1 or 0 votes.

Following are the detailed results:

*Total of 8 (+1) votes. * *5, +1 (Binding)* Jasper Blues Nicholas Sorrell
Pieterjan De Potter Dehowe Feng Eya Badal *3, +1 (Non Binding)* Joe Suh
Young Seung Andrew Ko Muhammad Shoaib

VOTE thread:
https://lists.apache.org/thread/2f7qpmojq7y7mglxy2trv27pc63kk7gr

Thank you,

John Gemignani

[RESULT][VOTE] Apache AGE Release 1.1.1 for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

The vote successfully passed with 4, +1 (binding) votes and 3, +1
(non-binding votes). There were no -1 or 0 votes.

Following are the detailed results:

Total of 7 (+1) votes. +1 (Binding) Jasper Blues Nicholas Sorrell Dehowe
Feng Eya Badal +1 (Non Binding) Joe Suh Young Seung Andrew Ko Muhammad
Shoaib

VOTE thread:
https://lists.apache.org/thread/prrlmxdq9qghpktghojdz684vspm0hgc

Thank you,

John Gemignani

CVE-2022-45786: Apache AGE: Python and Golang drivers allow data manipulation and exposure due to SQL injection

[John Gemignani]

Severity: important

Description:

There are issues with the AGE drivers for Golang and Python that enable SQL 
injections to occur. This impacts AGE for PostgreSQL 11 & AGE for PostgreSQL 
12, all versions up-to-and-including 1.1.0, when using those drivers.

The fix is to update to the latest Golang and Python drivers in addition to the 
latest version of AGE that is used for PostgreSQL 11 or  PostgreSQL 12.

The update of AGE will add a new function to enable parameterization of the 
cypher() function, which, in conjunction with the driver updates, will resolve 
this issue.

Background (for those who want more information):

After thoroughly researching this issue, we found that due to the nature of the 
cypher() function, it was not easy to parameterize the values passed into it. 
This enabled SQL injections, if the developer of the driver wasn't careful. The 
developer of the Golang and Pyton drivers didn't fully utilize 
parameterization, likely because of this, thus enabling SQL injections.

The obvious fix to this issue is to use parameterization in the drivers for all 
PG SQL queries. However, parameterizing all PG queries is complicated by the 
fact that the cypher() function call itself cannot be parameterized directly, 
as it isn't a real function. At least, not the parameters that would take the 
graph name and cypher query.

The reason the cypher() function cannot have those values parameterized is 
because the function is a placeholder and never actually runs. The cypher() 
function node, created by PG in the query tree, is transformed and replaced 
with a query tree for the actual cypher query during the analyze phase. The 
problem is that parameters - that would be passed in and that the cypher() 
function transform needs to be resolved - are only resolved in the execution 
phase, which is much later. Since the transform of the cypher() function needs 
to know the graph name and cypher query prior to execution, they can't be 
passed as parameters.

The fix that we are testing right now, and are proposing to use, is to create a 
function that will be called prior to the execution of the cypher() function 
transform. This new function will allow values to be passed as parameters for 
the graph name and cypher query. As this command will be executed prior to the 
cypher() function transform, its values will be resolved. These values can then 
be cached for the immediately following cypher() function transform to use. As 
added features, the cached values will store the calling session's pid, for 
validation. And, the cypher() function transform will clear this cached 
information after function invocation, regardless of whether it was used.

This method will allow the parameterizing of the cypher() function indirectly 
and provide a way to lock out SQL injection attacks.

References:

https://age.apache.org
https://www.cve.org/CVERecord?id=CVE-2022-45786

[DISCUSS] Migration strategy for commits to newly supported, unsynchronized, AGE PG version branches.

[John Gemignani]

Hi All,

There is a need to discuss our strategy going forward for migrating commits
from, as an example, AGE for PG 11 (called PG11 from this point) to AGE for
PG 12, 13, etc. (called PG, from this point) for newly supported
PostgreSQL version branches.

First, I'm no Github expert and welcome any viable, potential alternatives.
So, please do add suggestions or comments.

The issues that arise come down to the *author *and *co-author* of the work
being moved from one version to another. These issues are due to the
creation of newly supported PostgreSQL version branches and the adding of
commits that were not part of the previous version, at the time of the
creation of these new branches.

Please note: Once a new branch is synchronized (brought up to current), it
will be up to the individuals who put forth a PR, to apply it to applicable
versions. We will only be migrating commits to synchronize newly created
branches. This means that, once a branch is synchronized, any new PRs
added, are the responsibility of the PR creators. For example, if one
creates a PR for PG11, and PG12 and PG13 have been synchronized at the
time, it will be up to that person to create a PR for PG12 and PG13.

As far as I'm aware, other than modifying patch files directly, there are
only 2 ways to migrate a commit from one separate branch to another.
Remember, these branches are diverging.

   1. Extract a patch manually, apply it to a local feature branch, make
   sure that everything works as expected, rebase it to the local PG branch,
   then push that branch back to the remote.
   2. This is similar to #1, except it is done as a PR.

Using option #1, the original author of the patch is preserved, but there
is no co-author information for the person doing the migration.
Additionally, it doesn't use a PR, so isn't as trackable.
Using option #2, the original author is changed to the PR creator and the
original author is now the co-author.

Our preference would be to preserve the original author, as the author, and
have the person writing the PR become the co-author. However, it doesn't
appear as if that is possible. The co-author is important to keep as a
record of who did the work migrating the PR and, they potentially did a lot
of work to migrate that patch.

Being faced with these two options, neither of which are ideal, we're
leaning towards option #2.

This is where anyone who has any comments, experience, or expertise is
welcome to speak up. Additionally, if there are any reasonably viable
alternatives, we would be interested in hearing them out.

Otherwise, provided no input or reasonable alternatives we will be going
with option #2.

Thank you to everyone in advance,

John Gemignani

Re: [DISCUSS] Migration strategy for commits to newly supported, unsynchronized, AGE PG version branches.

[John Gemignani]

I haven't done anything with cherry picking but I will look into this to
see if it is helpful.

john

On Wed, Feb 8, 2023 at 11:18 AM Nicholas Sorrell  wrote:

> I’m curious if any experimentation has been done with the `git
> cherry-pick` command? This sounds like the ideal use case where it would
> preserve the history and give the PR initiator co-authorship. You might
> have already explored this, but just wanted to mention it. Here’s a small
> article explaining a similar use case:
> http://technosophos.com/2009/12/04/git-cherry-picking-move-small-code-patches-across-branches.html
>
> > On Feb 7, 2023, at 4:32 PM, John Gemignani 
> wrote:
> >
> > Hi All,
> >
> > There is a need to discuss our strategy going forward for migrating
> commits
> > from, as an example, AGE for PG 11 (called PG11 from this point) to AGE
> for
> > PG 12, 13, etc. (called PG, from this point) for newly supported
> > PostgreSQL version branches.
> >
> > First, I'm no Github expert and welcome any viable, potential
> alternatives.
> > So, please do add suggestions or comments.
> >
> > The issues that arise come down to the *author *and *co-author* of the
> work
> > being moved from one version to another. These issues are due to the
> > creation of newly supported PostgreSQL version branches and the adding of
> > commits that were not part of the previous version, at the time of the
> > creation of these new branches.
> >
> > Please note: Once a new branch is synchronized (brought up to current),
> it
> > will be up to the individuals who put forth a PR, to apply it to
> applicable
> > versions. We will only be migrating commits to synchronize newly created
> > branches. This means that, once a branch is synchronized, any new PRs
> > added, are the responsibility of the PR creators. For example, if one
> > creates a PR for PG11, and PG12 and PG13 have been synchronized at the
> > time, it will be up to that person to create a PR for PG12 and PG13.
> >
> > As far as I'm aware, other than modifying patch files directly, there are
> > only 2 ways to migrate a commit from one separate branch to another.
> > Remember, these branches are diverging.
> >
> >   1. Extract a patch manually, apply it to a local feature branch, make
> >   sure that everything works as expected, rebase it to the local PG
> branch,
> >   then push that branch back to the remote.
> >   2. This is similar to #1, except it is done as a PR.
> >
> > Using option #1, the original author of the patch is preserved, but there
> > is no co-author information for the person doing the migration.
> > Additionally, it doesn't use a PR, so isn't as trackable.
> > Using option #2, the original author is changed to the PR creator and the
> > original author is now the co-author.
> >
> > Our preference would be to preserve the original author, as the author,
> and
> > have the person writing the PR become the co-author. However, it doesn't
> > appear as if that is possible. The co-author is important to keep as a
> > record of who did the work migrating the PR and, they potentially did a
> lot
> > of work to migrate that patch.
> >
> > Being faced with these two options, neither of which are ideal, we're
> > leaning towards option #2.
> >
> > This is where anyone who has any comments, experience, or expertise is
> > welcome to speak up. Additionally, if there are any reasonably viable
> > alternatives, we would be interested in hearing them out.
> >
> > Otherwise, provided no input or reasonable alternatives we will be going
> > with option #2.
> >
> > Thank you to everyone in advance,
> >
> > John Gemignani
>
>

[DISCUSS] Apache AGE 1.3.0 Release for PostgreSQL 13

[John Gemignani]

e:

https://downloads.apache.org/age/KEYS



The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045



For information about the contents of this release, see:

https://github.com/apache/age/releases/tag/PG13/v1.3.0-rc0



Please share your thoughts and feedback and let us know if we can call for
a vote.


Thank you for your time.


John Gemignani

[DISCUSS] Apache AGE 1.3.0 Release for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

We would like to open a discussion for the Apache AGE release 1.3.0 for
PostgreSQL 12.

To learn more about Apache AGE, please see http://age.apache.org/

Functionalities included and addressed in this release are:


Apache AGE 1.3.0 for PostgreSQL 12 Release Notes


NOTE: Due to modifications to core tables, there is no upgrade
path from previous versions.

Implement CALL ...[YIELD] for cypher functions. (#630)

Graph names with the empty string '' are no longer allowed. (#251)

Fix typos at multiple locations. (#470)

Fix Bug with CALL... [YIELD], clause ignores WHERE.

Fix EXPLAIN to allow for nested cypher commands.

Fix delete_global_graphs and add regression tests. (#336)

Invalid labels now return NULL.

Update CONTRIBUTING.md (#348)

Fix null pointer on name compare. (#376)

Fix Travis CI warning messages.

Additional regression tests added for age_global_graph. (#341)

Readme Added for AGE-JDBC-Driver. (#383)

Updated volatility categories for many functions.

Fix issue 339 - entities in WHERE clause have wrong Expr. (#391)

Create complete graph function. (#342) (#662)

Fix issue 317: Graph naming convention. (#349)

Update SET clause to support assigning a map to a variable. (#468)

Patch to address PR 203 that appears to be inactive. (#671)

Add additional comments for create_graph function. (#582)

Optimize age_exists function. (#586)

Implement plus-equal operator in SET clause. (#638)

Implement CI test for python driver. (#587)

Move from travis CI to github actions for build. (#673)

Update all driver CIs to Github actions.

Fix build warnings. (#709)

Updated Readme for drivers folder. (#642)

Remove async from function definitions. (#680)

Barbell graph generation (#648) and Barbell regress tests. (#708)

Update Python Driver ANTLR 4.9.3 -> 4.11.1 (#706)

Fix WITH ignoring WHERE clause. (#646)

Implement isEmpty() predicate function. (#710)

Fix cypher function input argument checks. (#718)

Fix Issue 693 - server termination from return exists(path). (#721)

Update regression tests for cypher_with. (#725)

Fix issue 733 - create_complete_graph() terminates the server. (#734)
Prevent MATCH from following OPTIONAL MATCH. (#740)
Fix property constraints against resolved variables. (#724) (#751) (#701)
(#747)
Include invalid labels in reused variables. (#751) (#762)
Fix update_entity_tuple to use correct CommandId. (#769)
Remove check for scalar agtypes in unwind. (#736)
Update PG12 CI workflows. (#776)
Update readme and version for python driver. (#780)
Update README.md

*

The git tag to be discussed and voted on:
https://github.com/apache/age/releases/tag/PG12/v1.3.0-rc0

The git commit hash:
commit 01486efe5b8a2b316ae766299e6ec78b488fcff2

The release files for 1.3.0, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG12/1.3.0.rc0/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release see:
https://github.com/apache/age/releases/tag/PG12/v1.3.0-rc0

Please verify the above links, files, and signatures in addition to sharing
your thoughts and feedback and if we can call for a vote.

Thank you for your time.

John Gemignani

Re: [DISCUSS] Apache AGE 1.3.0 Release for PostgreSQL 13

[John Gemignani]

Dear Apache Community,

Since there are no objections, I am closing the [DISCUSS] thread and will
open the official vote for Apache AGE 1.3.0 for PostgreSQL 13 shortly.

Thank you all for your time!

John Gemignani

On Fri, Mar 31, 2023 at 2:43 PM John Gemignani 
wrote:

> Dear Apache Community,
>
>
>
> We would like to open a discussion for the Apache AGE release 1.3.0 for
> PostgreSQL 13.
>
>
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
>
>
> Functionalities included and addressed in this release:
>
>
>
> Apache AGE 1.3.0 for PostgreSQL 13 Release Notes
>
> NOTE: Due to this being the first release for PostgreSQL 13, there is no
>
> upgrade path from other versions.
>
> Implement CALL ...[YIELD] for cypher functions. (#630
> <https://github.com/apache/age/pull/630>)
>
> Graph names with the empty string '' are no more allowed. (#251
> <https://github.com/apache/age/pull/251>)
>
> Fix typos at multiple locations. (#470
> <https://github.com/apache/age/pull/470>)
>
> Fix Bug with CALL... [YIELD], clause ignores WHERE.
>
> Fix EXPLAIN to allow for nested cypher commands.
>
> Fix delete_global_graphs and add regression tests. (#336
> <https://github.com/apache/age/pull/336>)
>
> Invalid labels now return NULL.
>
> Update CONTRIBUTING.md (#348 <https://github.com/apache/age/pull/348>)
>
> Fix null pointer on name compare. (#376
> <https://github.com/apache/age/pull/376>)
>
> Fix Travis CI warning messages.
>
> Additional regression tests added for age_global_graph. (#341
> <https://github.com/apache/age/pull/341>)
>
> Readme Added for AGE-JDBC-Driver. (#383
> <https://github.com/apache/age/pull/383>)
>
> Updated volitility categories for many functions.
>
> Fix issue 339 - entities in WHERE clause have wrong Expr. (#391
> <https://github.com/apache/age/pull/391>)
>
> Create complete graph function. (#342
> <https://github.com/apache/age/pull/342>) (#662
> <https://github.com/apache/age/pull/662>)
>
> Fix issue 317: Graph naming convention. (#349
> <https://github.com/apache/age/pull/349>)
>
> Update SET clause to support assigning a map to a variable. (#468
> <https://github.com/apache/age/pull/468>)
>
> Patch to address PR 203 that appears to be inactive. (#671
> <https://github.com/apache/age/pull/671>)
>
> Add additional comments for create_graph function. (#582
> <https://github.com/apache/age/pull/582>)
>
> Optimize age_exists function. (#586
> <https://github.com/apache/age/pull/586>)
>
> Implement plus-equal operator in SET clause. (#638
> <https://github.com/apache/age/pull/638>)
>
> Implement CI test for python driver. (#587
> <https://github.com/apache/age/pull/587>)
>
> Move from travis CI to github actions for build. (#673
> <https://github.com/apache/age/pull/673>)
>
> Update all driver CIs to Github actions.
>
> Fix build warnings. (#709 <https://github.com/apache/age/pull/709>)
>
> Updated Readme for drivers folder. (#642
> <https://github.com/apache/age/pull/642>)
>
> Removed async from function definitions. (#680
> <https://github.com/apache/age/pull/680>)
>
> Barbell graph generation (#648 <https://github.com/apache/age/pull/648>)
> and Barbell regress tests. (#708 <https://github.com/apache/age/pull/708>)
>
> UPDATED Python Driver ANTLR 4.9.3 -> 4.11.1 (#706
> <https://github.com/apache/age/pull/706>)
>
> Fix WITH ignoring WHERE clause. (#646
> <https://github.com/apache/age/pull/646>)
>
> Implement isEmpty() predicate function. (#710
> <https://github.com/apache/age/pull/710>)
>
> Fix cypher function input argument checks. (#718
> <https://github.com/apache/age/issues/718>)
>
> Fix Issue 693 - server termination from return exists(path). (#721
> <https://github.com/apache/age/pull/721>)
>
> Update regression tests for cypher_with. (#725
> <https://github.com/apache/age/pull/725>)
>
> Fix issue 733 - create_complete_graph() terminates the server. (#734
> <https://github.com/apache/age/pull/734>)
>
> Prevent MATCH from following OPTIONAL MATCH. (#740
> <https://github.com/apache/age/pull/740>)
>
> Fix property constraints against resolved variables. (#724
> <https://github.com/apache/age/issues/724>) (#751
> <https://github.com/apache/age/pull/751>) (#701
> <https://github.com/apache/age/issues/701>) (#747
> <https://github.com/apache/age/pull/747>)
>
> Include invalid labels in reused variables. (#751
> <https://github.com/apache/age/pull/751>

[VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13

[John Gemignani]

Dear Apache Community,

This is an official vote for the Apache AGE release 1.3.0 for PostgreSQL 13.

To learn more about Apache AGE, please see http://age.apache.org/

Functionalities included and issues addressed in this release:
*
 Apache AGE 1.3.0 for PostgreSQL 13 Release Notes

 NOTE: Due to this being the first release for PostgreSQL 13, there is
no
 upgrade path from other versions.

 Implement CALL ...[YIELD] for cypher functions. (#630)
 Graph names with the empty string '' are disallowed. (#251)
 Fix typos at multiple locations. (#470)
 Fix Bug with CALL... [YIELD], clause ignores WHERE.
 Fix EXPLAIN to allow for nested cypher commands.
 Fix delete_global_graphs and add regression tests. (#336)
 Invalid labels now return NULL.
 Update CONTRIBUTING.md (#348)
 Fix null pointer on name compare. (#376)
 Fix Travis CI warning messages.
 Additional regression tests added for age_global_graph. (#341)
 Readme Added for AGE-JDBC-Driver. (#383)
 Updated volatility categories for many functions.
 Fix issue 339 - entities in WHERE clause have wrong Expr. (#391)
 Create complete graph function. (#342) (#662)
 Fix issue 317: Graph naming convention. (#349)
 Update SET clause to support assigning a map to a variable. (#468)
 Patch to address PR 203 that appears to be inactive. (#671)
 Add additional comments for create_graph function. (#582)
 Optimize age_exists function. (#586)
 Implement plus-equal operator in SET clause. (#638)
 Implement CI test for python driver. (#587)
 Move from travis CI to github actions for build. (#673)
 Update all driver CIs to Github actions.
 Fix build warnings. (#709)
 Updated Readme for drivers folder. (#642)
 Removed async from function definitions. (#680)
 Barbell graph generation (#648) and Barbell regress tests. (#708)
 Updated Python Driver ANTLR 4.9.3 -> 4.11.1 (#706)
 Fix WITH ignoring WHERE clause. (#646)
 Implement isEmpty() predicate function. (#710)
 Fix cypher function input argument checks. (#718)
 Fix Issue 693 - server termination from return exists(path). (#721)
 Update regression tests for cypher_with. (#725)
 Fix issue 733 - create_complete_graph() terminates the server. (#734)
 Prevent MATCH from following OPTIONAL MATCH. (#740)
 Fix property constraints against resolved variables. (#724) (#751)
(#701) (#747)
 Include invalid labels in reused variables. (#751) (#762)
 Fix update_entity_tuple to use correct CommandId. (#769)
 Remove check for scalar agtypes in unwind. (#736)
 Update PG13 CI workflows. (#775)
 Update readme and version for python driver. (#780)
 Update README.md
*

The git tag to be discussed and voted on:
https://github.com/apache/age/releases/tag/PG13/v1.3.0-rc0

The git commit hash:
commit 09e8cb4495f19badeb1aa20bf0990a874a120fbe

The release files for 1.3.0, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG13/1.3.0.rc0/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release, see:
https://github.com/apache/age/releases/tag/PG13/v1.3.0-rc0

!!! IMPORTANT !!!
Please note that Apache REQUIRES the following information to be in your
response the the vote -

- If you are a binding vote, a PMC, then you MUST state it in your
response.
- You MUST state what you checked, to support your vote.

Please vote -

+1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
  0, I won't get in the way of the vote.
 -1, Do not release this package because 

For example -

 +1 (Binding)
 Checked the following:
 - Signature and hash - check.
 - Tags and links - check.
 - LICENSE and NOTICE - check.
 - No unexpected binary files - check.

This vote will be open for 72 hours.

Thank you for your time.

John Gemignani

Re: [VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13

[John Gemignani]

Dear Apache Community,

Due to multiple issues and errors with the voting process for this release
(AGE 1.3.0 for PG13) -

1) Community members not stating what they checked or not checking
everything. This is not optional.
2) Community members who are PMCs, not stating that they are binding.
This is not optional.
3) Community members who are NOT PMCs, stating that they are binding.
Only PMCs are binding.

It is necessary to cancel this vote and resubmit it later. Please
understand that your vote is important but Apache needs it to be done
correctly. The Apache board reviews these votes and gives us feedback on
them. It is important for the community to do its best to look good.

Still, I do thank everyone who took part in the vote! We just need to
strive to do it better.

John Gemignani

On Tue, Apr 11, 2023 at 1:31 PM Waleed Ahmed Shahid
 wrote:

> +1 (Binding)
>  Checked the following:
>   Signature and hash-checked.
> - Tags and links - checked.
> - LICENSE and NOTICE - checked.
> - No unexpected binary files - checked.
>
> Good to go
>
> On Tue, Apr 11, 2023 at 12:41 PM Waleed Ahmed Shahid <
> wshahid.bscs19se...@seecs.edu.pk> wrote:
>
> > +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
> >
> > On Tue, 11 Apr 2023, 12:37 Daniel John,  wrote:
> >
> >> +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
> >>
> >> On Tue, Apr 11, 2023, 8:15 AM Hammad Saleem  >
> >> wrote:
> >>
> >> > +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
> >> >
> >> > On Tue, 11 Apr 2023, 11:39 AM Rahimullah Shaheen, <
> >> > rahimullah.shaheen...@gmail.com> wrote:
> >> >
> >> > > +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
> >> > >
> >> > > On Tue, 11 Apr 2023 at 11:21, Steve Shin 
> wrote:
> >> > >
> >> > > > +1
> >> > > >
> >> > > >
> >> > > > 2023년 4월 10일 (월) 오후 8:34, Muhammad Zahid <
> >> zahidmuhammad...@gmail.com
> >> > >님이
> >> > > > 작성:
> >> > > >
> >> > > > > +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
> >> > > > >
> >> > > > > On Tue, 11 Apr 2023, 6:43 am fatima raza, <
> >> fatimaraza...@gmail.com>
> >> > > > wrote:
> >> > > > >
> >> > > > > > +1, Release this package as Apache AGE 1.3.0 for
> PostgreSQL
> >> 13.
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>

Re: [VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13

[John Gemignani]

This thread has been canceled i.e. closed; please do not reply to it.

Thank you!

John Gemignani

On Tue, Apr 11, 2023 at 9:19 PM Nimra Tahir 
wrote:

> +1  Release this package as Apache age 1.3.0 for Postgresql 13.
> I did the usual checks, all looks good to me!
>
>
>1. Tags and links are checked
>2. License and Notice checked
>3. Checked for unexpected binary files
>
> Regards,
> Nimra Tahir
>
> On Wed, Apr 12, 2023 at 3:39 AM John Gemignani  >
> wrote:
>
> > Dear Apache Community,
> >
> > Due to multiple issues and errors with the voting process for this
> release
> > (AGE 1.3.0 for PG13) -
> >
> > 1) Community members not stating what they checked or not checking
> > everything. This is not optional.
> > 2) Community members who are PMCs, not stating that they are binding.
> > This is not optional.
> > 3) Community members who are NOT PMCs, stating that they are binding.
> > Only PMCs are binding.
> >
> > It is necessary to cancel this vote and resubmit it later. Please
> > understand that your vote is important but Apache needs it to be done
> > correctly. The Apache board reviews these votes and gives us feedback on
> > them. It is important for the community to do its best to look good.
> >
> > Still, I do thank everyone who took part in the vote! We just need to
> > strive to do it better.
> >
> > John Gemignani
> >
> > On Tue, Apr 11, 2023 at 1:31 PM Waleed Ahmed Shahid
> >  wrote:
> >
> > > +1 (Binding)
> > >  Checked the following:
> > >   Signature and hash-checked.
> > > - Tags and links - checked.
> > > - LICENSE and NOTICE - checked.
> > > - No unexpected binary files - checked.
> > >
> > > Good to go
> > >
> > > On Tue, Apr 11, 2023 at 12:41 PM Waleed Ahmed Shahid <
> > > wshahid.bscs19se...@seecs.edu.pk> wrote:
> > >
> > > > +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
> > > >
> > > > On Tue, 11 Apr 2023, 12:37 Daniel John,  wrote:
> > > >
> > > >> +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
> > > >>
> > > >> On Tue, Apr 11, 2023, 8:15 AM Hammad Saleem <
> > hammadsaleem1...@gmail.com
> > > >
> > > >> wrote:
> > > >>
> > > >> > +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
> > > >> >
> > > >> > On Tue, 11 Apr 2023, 11:39 AM Rahimullah Shaheen, <
> > > >> > rahimullah.shaheen...@gmail.com> wrote:
> > > >> >
> > > >> > > +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13.
> > > >> > >
> > > >> > > On Tue, 11 Apr 2023 at 11:21, Steve Shin 
> > > wrote:
> > > >> > >
> > > >> > > > +1
> > > >> > > >
> > > >> > > >
> > > >> > > > 2023년 4월 10일 (월) 오후 8:34, Muhammad Zahid <
> > > >> zahidmuhammad...@gmail.com
> > > >> > >님이
> > > >> > > > 작성:
> > > >> > > >
> > > >> > > > > +1, Release this package as Apache AGE 1.3.0 for PostgreSQL
> > 13.
> > > >> > > > >
> > > >> > > > > On Tue, 11 Apr 2023, 6:43 am fatima raza, <
> > > >> fatimaraza...@gmail.com>
> > > >> > > > wrote:
> > > >> > > > >
> > > >> > > > > > +1, Release this package as Apache AGE 1.3.0 for
> > > PostgreSQL
> > > >> 13.
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > > >
> > >
> >
>

[VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13

[John Gemignani]

cked the following:   Checked the following:
   - Signature and Hash.   - Signature and Hash.
   - Tags and Links.   - Tags and Links.
   - LICENSE and NOTICE.  - LICENSE and NOTICE.
   - No unexpected binary files. - No unexpected binary files.

-1, Failed due to 0 (binding)
Checked the following:   Checked the following:
   - Signature and Hash. - Signature and Hash.
   - Tags and Links. - Tags and Links.
   - BAD LICENSE and NOTICE.   - LICENSE and NOTICE.
   - No unexpected binary files.  - No unexpected binary files.

Again, those are just samples for guidance, DO NOT copy/paste. However,
your responses should be similar in form.

Please note that it is not a good practice to copy/paste someone else's
response, you may inadvertently misrepresent yourself or your vote.

This vote will be open for 72 hours.

Thank you for your time.

John Gemignani

Re: ID generation for vertices and edges

[John Gemignani]

My understanding for having the label ID as part of the ID for the vertices
or edges was due to vertices and edges only being allowed to have 1 label,
a design decision.

Since vertices and edges could only have 1 label, they could be stored in a
table named as such. The idea was that this would increase performance by
having vertices and edges separated by labels, and therefore speed up
access to them. By storing the label ID in the vertex or edge ID, it
allowed one to find the label table more easily, and then the actual entry.

However, I'm not sure that this would necessarily increase performance as
going between multiple tables may be just as inefficient as keeping all the
entries in one. And, everything comes at a cost. The cost here is at the
expense of making it more difficult to support multiple labels or using the
maximum number of graph components.

Hopefully, this was helpful.

john

Below are some queries showing this structure, for reference -

psql-11.5-5432-pgsql=# select * from ag_label;
   name   | graph | id | kind |relation |
 seq_name
--+---++--+-+-
 _ag_label_vertex | 16943 |  1 | v| graph1._ag_label_vertex |
_ag_label_vertex_id_seq
 _ag_label_edge   | 16943 |  2 | e| graph1._ag_label_edge   |
_ag_label_edge_id_seq
 zero | 16943 |  3 | v| graph1.zero |
zero_id_seq
 knows| 16943 | 36 | e| graph1.knows|
knows_id_seq
(4 rows)

psql-11.5-5432-pgsql=# select * from graph1.zero;
   id| properties
-+-
 844424930131969 | {"name": "Zero", "value": 2.71828182845905}
(1 row)

psql-11.5-5432-pgsql=# select * from graph1.knows;
id |start_id | end_id  | properties
---+-+-+
 10133099161583617 | 281474976710657 | 281474976710658 | {}
(1 row)

psql-11.5-5432-pgsql=# SELECT * from cypher('graph1', $$ MATCH (n:zero)
RETURN n $$) as (result agtype);
   result
-
 {"id": 844424930131969, "label": "zero", "properties": {"name": "Zero",
"value": 2.71828182845905}}::vertex
(1 row)

psql-11.5-5432-pgsql=# SELECT * from cypher('graph1', $$ MATCH
()-[e:knows]->() RETURN e $$) as (result agtype);
   result
-
 {"id": 10133099161583617, "label": "knows", "end_id": 281474976710658,
"start_id": 281474976710657, "properties": {}}::edge
(1 row)

psql-11.5-5432-pgsql=#

On Wed, Apr 12, 2023 at 1:45 PM Panagiotis Foliadis 
wrote:

> Hey all,
> After digging around in the source code I've discovered that the id's for
> vertices and edges are generated
> through the same procedure (by applying a mask on the label id of the
> different vertices and edges). That leads
> to the fact that the id's generated are solely based on the id of the
> label that they would be inserted, and also
> that the potential id's are huge numbers (since the mask applied is
> 0x). Is there a reason for this?
> Why can't the sequence be used and generated id's starting from 1, without
> applying the mask, for each vertix and edge?
>

Re: [VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13

[John Gemignani]

Dear Apache Community,

We would like to thank everyone who participated in the voting process and
are now closing this vote. We will be sending out the results shortly.

John Gemignani

On Sat, Apr 15, 2023 at 5:11 AM JawadAli Abbasi
 wrote:

> +1
> I've checked the following:
> Signature and HashNo unexpected binary filesLicense and NoticeTags and
> Links
>
> Sent from Yahoo Mail on Android
>
>   On Sat, Apr 15, 2023 at 1:44 AM, Omar Saad
> wrote:   +1
> checked :
> - Signature and Hash - checked
> - License and Notice - checked
> - Merged Pull Requests - checked
>
> On Wed, Apr 12, 2023 at 6:57 PM John Gemignani  >
> wrote:
>
> > Dear Apache Community,
> >
> > Please carefully read all instructions as they may have changed since the
> > last vote thread.
> >
> > This is an official vote for Apache AGE release 1.3.0 for PostgreSQL 13.
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > Functionalities included and issues addressed in this release:
> > *
> >  Apache AGE 1.3.0 for PostgreSQL 13 Release Notes
> >
> >  NOTE: Due to this being the first release for PostgreSQL 13, there
> >  is no upgrade path from other versions.
> >
> >  Implement CALL ...[YIELD] for cypher functions. (#630)
> >  Graph names with the empty string '' are disallowed. (#251)
> >  Fix typos at multiple locations. (#470)
> >  Fix Bug with CALL... [YIELD], clause ignores WHERE.
> >  Fix EXPLAIN to allow for nested cypher commands.
> >  Fix delete_global_graphs and add regression tests. (#336)
> >  Invalid labels now return NULL.
> >  Update CONTRIBUTING.md (#348)
> >  Fix null pointer on name compare. (#376)
> >  Fix Travis CI warning messages.
> >  Additional regression tests added for age_global_graph. (#341)
> >  Readme Added for AGE-JDBC-Driver. (#383)
> >  Updated volatility categories for many functions.
> >  Fix issue 339 - entities in WHERE clause have wrong Expr. (#391)
> >  Create complete graph function. (#342) (#662)
> >  Fix issue 317: Graph naming convention. (#349)
> >  Update SET clause to support assigning a map to a variable. (#468)
> >  Patch to address PR 203 that appears to be inactive. (#671)
> >  Add additional comments for create_graph function. (#582)
> >  Optimize age_exists function. (#586)
> >  Implement plus-equal operator in SET clause. (#638)
> >  Implement CI test for python driver. (#587)
> >  Move from travis CI to github actions for build. (#673)
> >  Update all driver CIs to Github actions.
> >  Fix build warnings. (#709)
> >  Updated Readme for drivers folder. (#642)
> >  Removed async from function definitions. (#680)
> >  Barbell graph generation (#648) and Barbell regress tests. (#708)
> >  Updated Python Driver ANTLR 4.9.3 -> 4.11.1 (#706)
> >  Fix WITH ignoring WHERE clause. (#646)
> >  Implement isEmpty() predicate function. (#710)
> >  Fix cypher function input argument checks. (#718)
> >  Fix Issue 693 - server termination from return exists(path). (#721)
> >  Update regression tests for cypher_with. (#725)
> >  Fix issue 733 - create_complete_graph() terminates the server.
> (#734)
> >  Prevent MATCH from following OPTIONAL MATCH. (#740)
> >  Fix property constraints against resolved variables. (#724) (#751)
> > (#701) (#747)
> >  Include invalid labels in reused variables. (#751) (#762)
> >  Fix update_entity_tuple to use correct CommandId. (#769)
> >  Remove check for scalar agtypes in unwind. (#736)
> >  Update PG13 CI workflows. (#775)
> >  Update readme and version for python driver. (#780)
> >  Update README.md
> > *
> >
> > !!! PLEASE VERIFY ALL of the below tags, hash, links, signatures, and
> keys
> > !!!
> >
> > The git tag to be discussed and voted on:
> > https://github.com/apache/age/releases/tag/PG13/v1.3.0-rc0
> >
> > The git commit hash:
> > commit 09e8cb4495f19badeb1aa20bf0990a874a120fbe
> >
> > The release files for 1.3.0, can be found at:
> > https://dist.apache.org/repos/dist/dev/age/PG13/1.3.0.rc0/
> >
> > Signatures used for AGE RCs can be found in this file:
> > https://downloads.apache.org/age/KEYS
> >
> > The fingerprint of key to sign release artifacts:
> > 4293 0603 8E

[RESULT][VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13

[John Gemignani]

Dear Apache Community,

The vote successfully passed with 3 +1 (binding) and 33 +1 (non-binding)
votes. There were no 0 or -1 votes. There was 1 voided vote due to not
following voting instructions.

Following are the abbreviated detailed results :

Total of 36 (+1) votes.

3 +1 (binding)
Dehowe Feng
Nicholas Sorrel
Eya Badal

33 +1 (non-binding)
Due to the large number of votes, please see the vote thread for these.

1 voided vote
fatima raza (stated binding when not a binding vote)

VOTE thread:
https://lists.apache.org/thread/k6qgjnzp3p0k70wgyf72tg5xgpr1xol3

Thank you all!

John Gemignani

Re: [DISCUSS] Apache AGE 1.3.0 Release for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

Since there are no objections, I am closing the DISCUSS thread and will
open the official VOTE thread for Apache AGE 1.3.0 for PostgreSQL 12
shortly.

Thank you,

John Gemignani

On Tue, Apr 11, 2023 at 11:30 AM Aditya Gupta  wrote:

> It looks good to me.
>
> Best
> Aditya Gupta
>
> On Tue, Apr 11, 2023, 11:30 PM Muneeb Khan 
> wrote:
>
> > +1
> >
> > I have checked:
> >
> > > Graph names with the empty string '' are no longer allowed. (#251)
> >
> > > Fix typos at multiple locations. (#470)
> >
> > > Fix Bug with CALL... [YIELD], clause ignores WHERE.
> >
> > > Fix EXPLAIN to allow for nested cypher commands.
> >
> > > Fix delete_global_graphs and add regression tests. (#336)
> >
> > > Invalid labels now return NULL.
> >
> > > Fix null pointer on name compare. (#376)
> >
> > > Updated volatility categories for many functions.
> >
> > > Fix issue 317: Graph naming convention. (#349)
> >
> > These changes are correct, to the best of my knowledge.
> >
> > Regards,
> > Muneeb
> >
> > On Tue, Apr 11, 2023 at 1:17 AM Eya Badal  wrote:
> >
> > > Looks good to me!!
> > >
> > > I checked the following:
> > >
> > > - Signature and hash - check.
> > > - LICENSE and NOTICE - check.
> > > - No unexpected binary files - check.
> > >
> > > Great Job!!
> > >
> > > Best,
> > > Eya
> > >
> > > On 2023/04/05 22:34:23 John Gemignani wrote:
> > > > Dear Apache Community,
> > > >
> > > > We would like to open a discussion for the Apache AGE release 1.3.0
> for
> > > > PostgreSQL 12.
> > > >
> > > > To learn more about Apache AGE, please see http://age.apache.org/
> > > >
> > > > Functionalities included and addressed in this release are:
> > > >
> > > >
> > > > Apache AGE 1.3.0 for PostgreSQL 12 Release Notes
> > > >
> > > >
> > > > NOTE: Due to modifications to core tables, there is no upgrade
> > > > path from previous versions.
> > > >
> > > > Implement CALL ...[YIELD] for cypher functions. (#630)
> > > >
> > > > Graph names with the empty string '' are no longer allowed. (#251)
> > > >
> > > > Fix typos at multiple locations. (#470)
> > > >
> > > > Fix Bug with CALL... [YIELD], clause ignores WHERE.
> > > >
> > > > Fix EXPLAIN to allow for nested cypher commands.
> > > >
> > > > Fix delete_global_graphs and add regression tests. (#336)
> > > >
> > > > Invalid labels now return NULL.
> > > >
> > > > Update CONTRIBUTING.md (#348)
> > > >
> > > > Fix null pointer on name compare. (#376)
> > > >
> > > > Fix Travis CI warning messages.
> > > >
> > > > Additional regression tests added for age_global_graph. (#341)
> > > >
> > > > Readme Added for AGE-JDBC-Driver. (#383)
> > > >
> > > > Updated volatility categories for many functions.
> > > >
> > > > Fix issue 339 - entities in WHERE clause have wrong Expr. (#391)
> > > >
> > > > Create complete graph function. (#342) (#662)
> > > >
> > > > Fix issue 317: Graph naming convention. (#349)
> > > >
> > > > Update SET clause to support assigning a map to a variable. (#468)
> > > >
> > > > Patch to address PR 203 that appears to be inactive. (#671)
> > > >
> > > > Add additional comments for create_graph function. (#582)
> > > >
> > > > Optimize age_exists function. (#586)
> > > >
> > > > Implement plus-equal operator in SET clause. (#638)
> > > >
> > > > Implement CI test for python driver. (#587)
> > > >
> > > > Move from travis CI to github actions for build. (#673)
> > > >
> > > > Update all driver CIs to Github actions.
> > > >
> > > > Fix build warnings. (#709)
> > > >
> > > > Updated Readme for drivers folder. (#642)
> > > >
> > > > Remove async from function definitions. (#680)
> > > >
> > > > Barbell graph generation (#648) and Barbell regress tests. (#708)
> > > >
> > > > Update Python Driver ANTLR 4.9.3 ->

[VOTE] Apache AGE 1.3.0 Release for PostgreSQL 12

[John Gemignani]

   - LICENSE and NOTICE.  - LICENSE and NOTICE.

   - No unexpected binary files. - No unexpected binary files.


-1, Failed due to 0 (binding)

Checked the following:   Checked the following:

   - Signature and Hash. - Signature and Hash.

   - Tags and Links. - Tags and Links.

   - BAD LICENSE and NOTICE.   - LICENSE and NOTICE.

   - No unexpected binary files.  - No unexpected binary files.



Again, those are just samples for guidance, DO NOT copy/paste. However,
your responses should be similar in form.


Please note that it is not a good practice to copy/paste someone else's
response, you may inadvertently misrepresent yourself or your vote.


This vote will be open for 72 hours.


Thank you for your time.


John Gemignani

Re: [VOTE] Apache AGE 1.3.0 Release for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

Due to an error in the RELEASE file, I will be canceling this release. Once
the issue has been corrected and all files have been updated, I will
reissue the vote.

Thank you for your time and effort.

John Gemignani

On Thu, Apr 20, 2023 at 10:15 PM Muhammad Taha Naveed
 wrote:

> -1
>
> - Found error in release notes. PR #709 (Fix build warnings) was only meant
> for PG13 but it is also included in PG12 release notes.
>
> Regards
> Muhammad Taha Naveed
>
> On Fri, Apr 21, 2023, 01:38 Arunabh Das  wrote:
>
> > +1
> > Checked:
> > - Signature and Hash
> > - Tags and Links
> > - LICENSE and NOTICE
> > - Merged Pull Requests
> > - No unexpected binary files.
> >
> > With regards,
> > Arunabh
> >
> > __
> > LinkedIn: https://www.linkedin.com/in/arunabh-das-b9959720b
> >
> > On Tue, 18 Apr 2023, 05:33 John Gemignani, 
> > wrote:
> >
> > > Dear Apache Community,
> > >
> > > Please carefully read all instructions as they may have changed since
> the
> > > last vote thread.
> > >
> > > This is an official vote for Apache AGE release 1.3.0 for PostgreSQL
> 12.
> > >
> > > To learn more about Apache AGE, please see http://age.apache.org/
> > >
> > > Functionalities included and addressed in this release are:
> > >
> > > *
> > > Apache AGE 1.3.0 for PostgreSQL 12 Release Notes
> > >
> > >
> > > NOTE: Due to modifications to core tables, there is no upgrade
> > > path from previous versions.
> > >
> > > Implement CALL ...[YIELD] for cypher functions. (#630)
> > >
> > > Graph names with the empty string '' are no longer allowed. (#251)
> > >
> > > Fix typos at multiple locations. (#470)
> > >
> > > Fix Bug with CALL... [YIELD], clause ignores WHERE.
> > >
> > > Fix EXPLAIN to allow for nested cypher commands.
> > >
> > > Fix delete_global_graphs and add regression tests. (#336)
> > >
> > > Invalid labels now return NULL.
> > >
> > > Update CONTRIBUTING.md (#348)
> > >
> > > Fix null pointer on name compare. (#376)
> > >
> > > Fix Travis CI warning messages.
> > >
> > > Additional regression tests added for age_global_graph. (#341)
> > >
> > > Readme Added for AGE-JDBC-Driver. (#383)
> > >
> > > Updated volatility categories for many functions.
> > >
> > > Fix issue 339 - entities in WHERE clause have wrong Expr. (#391)
> > >
> > > Create complete graph function. (#342) (#662)
> > >
> > > Fix issue 317: Graph naming convention. (#349)
> > >
> > > Update SET clause to support assigning a map to a variable. (#468)
> > >
> > > Patch to address PR 203 that appears to be inactive. (#671)
> > >
> > > Add additional comments for create_graph function. (#582)
> > >
> > > Optimize age_exists function. (#586)
> > >
> > > Implement plus-equal operator in SET clause. (#638)
> > >
> > > Implement CI test for python driver. (#587)
> > >
> > > Move from travis CI to github actions for build. (#673)
> > >
> > > Update all driver CIs to Github actions.
> > >
> > > Fix build warnings. (#709)
> > >
> > > Updated Readme for drivers folder. (#642)
> > >
> > > Remove async from function definitions. (#680)
> > >
> > > Barbell graph generation (#648) and Barbell regress tests. (#708)
> > >
> > > Update Python Driver ANTLR 4.9.3 -> 4.11.1 (#706)
> > >
> > > Fix WITH ignoring WHERE clause. (#646)
> > >
> > > Implement isEmpty() predicate function. (#710)
> > >
> > > Fix cypher function input argument checks. (#718)
> > >
> > > Fix Issue 693 - server termination from return exists(path). (#721)
> > >
> > > Update regression tests for cypher_with. (#725)
> > >
> > > Fix issue 733 - create_complete_graph() terminates the server. (#734)
> > > Prevent MATCH from following OPTIONAL MATCH. (#740)
> > > Fix property constraints against resolved variables. (#724) (#751)
> (#701)
> > > (#747)
> > > Include invalid labels in reused variables. (#751) (#762)
> > > Fix update_entity_tuple to use correct CommandId. (#769)
> > > Remove check for scalar agtypes 

[VOTE] Apache AGE 1.3.0 Release for PostgreSQL 12

[John Gemignani]

  - Tags and Links.- Tags and Links.
   - LICENSE, RELEASE, &   - LICENSE, RELEASE, &
 NOTICE. NOTICE.
   - No unexpected binary files.  - No unexpected binary files.

  -1, Failed due to  0 (binding)
  Checked the following:Checked the following:
- Signature and Hash. - Signature and Hash.
- Tags and Links. - Tags and Links.
- BAD LICENSE and NOTICE.   - LICENSE, RELEASE, &
- No unexpected binary files. NOTICE.
- No unexpected
binary files.

Again, those are just samples for guidance, DO NOT copy/paste. However,
your responses should be similar in form.

Please note that it is not a good practice to copy/paste someone else's
response, you may inadvertently misrepresent yourself or your vote.

This vote will be open for 72 hours.

Thank you for your time.

John Gemignani

Re: [VOTE] Apache AGE 1.3.0 Release for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

We would like to thank everyone who participated in the voting process and
are now closing this vote and will be sending out the results shortly.

Thank you!

John Gemignani

On Wed, Apr 26, 2023 at 3:32 PM Bhaskar Sharma 
wrote:

> +1
>
> - Signature and Hash - checked
> - Tags and links - checked
> - No unexpected binary files - checked
> - Validity of release notes - checked
> - Regression tests - checked
> - Driver tests - checked
>
> On Wed, Apr 26, 2023 at 5:03 AM Carla Sanches 
> wrote:
>
> > +1
> > Checked the following:
> > - Signature and hash.
> > - Tags and links.
> > - No unexpected binary files.
> > - Regression tests.
> > - LICENSE and NOTICE.
> >
> > Checked the following merged Pull Requests:
> > - Create complete graph function. (#342) (#662);
> > - Update SET clause to support assigning a map to a variable. (#468);
> > - Implement isEmpty() predicate function. (#710);
> > - Graph names with the empty string '' are no more allowed. (#251);
> > - Fix typos at multiple locations. (#470);
> > - Update CONTRIBUTING.md (#348);
> > - Additional regression tests added for age_global_graph. (#341);
> > - Fix issue 317: Graph naming convention. (#349);
> > - Fix cypher function input argument checks. (#718);
> > - Fix Issue 693 - server termination from return exists(path). (#721);
> > - Update regression tests for cypher_with. (#725);
> > - Fix issue 733 - create_complete_graph() terminates the server. (#734);
> > - Prevent MATCH from following OPTIONAL MATCH. (#740);
> > - Update README.md.
> >
> > Em sex., 21 de abr. de 2023 às 21:02, John Gemignani <
> > john.gemign...@bitnine.net> escreveu:
> >
> > > Dear Apache Community,
> > >
> > > Please carefully read all instructions as they may have changed since
> the
> > > last vote thread.
> > >
> > > This is an official vote for Apache AGE release 1.3.0 for PostgreSQL
> 12.
> > > This release corrects an issue with the RELEASE notes from the previous
> > > vote.
> > >
> > > To learn more about Apache AGE, please see http://age.apache.org/
> > >
> > > Functionalities included and addressed in this release are:
> > >
> > > *
> > > Apache AGE 1.3.0 for PostgreSQL 12 Release Notes
> > >
> > > NOTE: Due to modifications to core tables, there is no upgrade
> > > path from previous versions.
> > >
> > > Implement CALL ...[YIELD] for cypher functions. (#630)
> > > Graph names with the empty string '' are no longer allowed. (#251)
> > > Fix typos at multiple locations. (#470)
> > > Fix Bug with CALL... [YIELD], clause ignores WHERE.
> > > Fix EXPLAIN to allow for nested cypher commands.
> > > Fix delete_global_graphs and add regression tests. (#336)
> > > Invalid labels now return NULL.
> > > Update CONTRIBUTING.md (#348)
> > > Fix null pointer on name compare. (#376)
> > > Fix Travis CI warning messages.
> > > Additional regression tests added for age_global_graph. (#341)
> > > Readme Added for AGE-JDBC-Driver. (#383)
> > > Updated volatility categories for many functions.
> > > Fix issue 339 - entities in WHERE clause have wrong Expr. (#391)
> > > Create complete graph function. (#342) (#662)
> > > Fix issue 317: Graph naming convention. (#349)
> > > Update SET clause to support assigning a map to a variable. (#468)
> > > Patch to address PR 203 that appears to be inactive. (#671)
> > > Add additional comments for create_graph function. (#582)
> > > Optimize age_exists function. (#586)
> > > Implement plus-equal operator in SET clause. (#638)
> > > Implement CI test for python driver. (#587)
> > > Move from travis CI to github actions for build. (#673)
> > > Update all driver CIs to Github actions.
> > > Fix build warnings.
> > > Updated Readme for drivers folder. (#642)
> > > Remove async from function definitions. (#680)
> > > Barbell graph generation (#648) and Barbell regress tests. (#708)
> > > Update Python Driver ANTLR 4.9.3 -> 4.11.1 (#706)
> > > Fix WITH ignoring WHERE clause. (#646)
> > > Implement isEmpty() predicate function. (#710)
> > > Fix cypher function input argument checks. (#718)
> > > Fix Issue 693 - server termination from return exists(path). (#721)
> > > Update regression tests for cypher_with. (#725)
> > > Fix issue 733 - cre

[RESULT][VOTE] Apache AGE 1.3.0 Release for PostgreSQL 12

[John Gemignani]

Dear Apache Community,

The vote successfully passed with 3 +1 (binding) and 7 +1 (non-binding)
votes. There were no 0 or -1 votes.

Following are the detailed results :

Total of 10 (+1) votes.

3 +1 (binding)
Dehowe Feng
Nicholas Sorrel
Eya Badal

7 +1 (non-binding)
Bhaskar Sharma
Carla Sanches
Moiez Ibrar
JawadAli Abbasi
Kamlesh Kumar
Mohamed Mokhtar
Mohammad Taha Naveed

VOTE thread:
https://lists.apache.org/thread/t4kjb9rhbkyxscvbx4948wrbcz0hj2fq

Thank you all!

John Gemignani

[DISCUSS] Apache AGE 1.3.0 Release for PostgreSQL 11

[John Gemignani]

Dear Apache Community,

We would like to open a discussion for the Apache AGE release 1.3.0 for
PostgreSQL 11.

To learn more about Apache AGE, please see http://age.apache.org/

Functionalities included and addressed in this release are:

*
Release Notes for Apache AGE release v1.3.0 for PostgreSQL 11

Add additional comments for create_graph function. (#582)
Optimize age_exists function. (#586)
Implement plus-equal operator in SET clause. (#638)
Implement CI test for python driver. (#587)
Move from travis CI to github actions for build. (#673)
Update all driver CIs to Github actions.
Fix build warnings.
Fix golang driver workflow (#563)
Updated Readme for drivers folder. (#642)
Removed async from function definitions. (#680)
Barbell graph generation (#648) and Barbell regress tests. (#708)
Updated Python Driver ANTLR 4.9.3 -> 4.11.1 (#706)
Modify docker url for JDBC driver tests (#716)
Fix WITH ignoring WHERE clause. (#646)
Implement isEmpty() predicate function. (#710)
Fix cypher function input argument checks. (#718)
Fix Issue 693 - server termination from return exists(path). (#721)
Update regression tests for cypher_with. (#725)
Fix issue 733 - create_complete_graph() terminates the server. (#734)
Prevent MATCH from following OPTIONAL MATCH. (#740)
Fix property constraints against resolved variables. (#724) (#751) (#701)
(#747)
Include invalid labels in reused variables. (#751) (#762)
Remove check for scalar agtypes in unwind. (#736)
Update PG11 CI workflows.
Update readme and version for python driver. (#780)
Update README.md
*

The git tag to be discussed and voted on:
https://github.com/apache/age/releases/tag/PG11/v1.3.0-rc0

The git commit hash:
commit 1a452595fe59975c1df4941e4f8eeb12c097bab7

The release files for 1.3.0, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG11/1.3.0.rc0/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release see:
https://github.com/apache/age/releases/tag/PG11/v1.3.0-rc0

Please verify the above links, files, and signatures in addition to sharing
your thoughts and feedback and if we can call for a vote.

Thank you for your time.

John Gemignani

Re: [DISCUSS] Apache AGE 1.3.0 Release for PostgreSQL 11

[John Gemignani]

Dear Apache Community,

Since there are no objections, I am closing the DISCUSS thread and will
open the official VOTE thread for Apache AGE 1.3.0 for PostgreSQL 11
shortly.

Thank you for your time.

John Gemignani

On Tue, May 9, 2023 at 11:14 AM Muhammad Shoaib 
wrote:

> +1 Looks good to me.
>
> I have checked the following
>
> - Signature and hash - check.
> - LICENSE and NOTICE - check.
> - No unexpected binary files - check.
>
> Ciao,
> Shoaib
>
>
> On Wed, May 3, 2023 at 8:51 PM Muneeb Khan 
> wrote:
>
> > +1
> > - Signature and hash - checked.
> > - LICENSE and NOTICE - checked.
> > - No unexpected binary files - checked.
> > - Merged Pull Requests - checked.
> >
> > Thanks
> >
> > On Fri, Apr 28, 2023 at 11:52 PM John Gemignani <
> > john.gemign...@bitnine.net>
> > wrote:
> >
> > > Dear Apache Community,
> > >
> > > We would like to open a discussion for the Apache AGE release 1.3.0 for
> > > PostgreSQL 11.
> > >
> > > To learn more about Apache AGE, please see http://age.apache.org/
> > >
> > > Functionalities included and addressed in this release are:
> > >
> > > *
> > > Release Notes for Apache AGE release v1.3.0 for PostgreSQL 11
> > >
> > > Add additional comments for create_graph function. (#582)
> > > Optimize age_exists function. (#586)
> > > Implement plus-equal operator in SET clause. (#638)
> > > Implement CI test for python driver. (#587)
> > > Move from travis CI to github actions for build. (#673)
> > > Update all driver CIs to Github actions.
> > > Fix build warnings.
> > > Fix golang driver workflow (#563)
> > > Updated Readme for drivers folder. (#642)
> > > Removed async from function definitions. (#680)
> > > Barbell graph generation (#648) and Barbell regress tests. (#708)
> > > Updated Python Driver ANTLR 4.9.3 -> 4.11.1 (#706)
> > > Modify docker url for JDBC driver tests (#716)
> > > Fix WITH ignoring WHERE clause. (#646)
> > > Implement isEmpty() predicate function. (#710)
> > > Fix cypher function input argument checks. (#718)
> > > Fix Issue 693 - server termination from return exists(path). (#721)
> > > Update regression tests for cypher_with. (#725)
> > > Fix issue 733 - create_complete_graph() terminates the server. (#734)
> > > Prevent MATCH from following OPTIONAL MATCH. (#740)
> > > Fix property constraints against resolved variables. (#724) (#751)
> (#701)
> > > (#747)
> > > Include invalid labels in reused variables. (#751) (#762)
> > > Remove check for scalar agtypes in unwind. (#736)
> > > Update PG11 CI workflows.
> > > Update readme and version for python driver. (#780)
> > > Update README.md
> > > *
> > >
> > > The git tag to be discussed and voted on:
> > > https://github.com/apache/age/releases/tag/PG11/v1.3.0-rc0
> > >
> > > The git commit hash:
> > > commit 1a452595fe59975c1df4941e4f8eeb12c097bab7
> > >
> > > The release files for 1.3.0, can be found at:
> > > https://dist.apache.org/repos/dist/dev/age/PG11/1.3.0.rc0/
> > >
> > > Signatures used for AGE RCs can be found in this file:
> > > https://downloads.apache.org/age/KEYS
> > >
> > > The fingerprint of key to sign release artifacts:
> > > 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
> > >
> > > For information about the contents of this release see:
> > > https://github.com/apache/age/releases/tag/PG11/v1.3.0-rc0
> > >
> > > Please verify the above links, files, and signatures in addition to
> > sharing
> > > your thoughts and feedback and if we can call for a vote.
> > >
> > > Thank you for your time.
> > >
> > > John Gemignani
> > >
> >
>

[VOTE] Apache AGE release 1.3.0 for PostgreSQL 11

[John Gemignani]

Dear Apache Community,

Please carefully read all instructions as they may have changed since the
last vote thread.

This is an official [VOTE] for Apache AGE release 1.3.0 for PostgreSQL 11.

To learn more about Apache AGE, please see http://age.apache.org/

Functionalities included and addressed in this release are:

*
Release Notes for Apache AGE release v1.3.0 for PostgreSQL 11

Add additional comments for create_graph function. (#582)
Optimize age_exists function. (#586)
Implement plus-equal operator in SET clause. (#638)
Implement CI test for python driver. (#587)
Move from travis CI to github actions for build. (#673)
Update all driver CIs to Github actions.
Fix build warnings.
Fix golang driver workflow (#563)
Updated Readme for drivers folder. (#642)
Removed async from function definitions. (#680)
Barbell graph generation (#648) and Barbell regress tests. (#708)
Updated Python Driver ANTLR 4.9.3 -> 4.11.1 (#706)
Modify docker url for JDBC driver tests (#716)
Fix WITH ignoring WHERE clause. (#646)
Implement isEmpty() predicate function. (#710)
Fix cypher function input argument checks. (#718)
Fix Issue 693 - server termination from return exists(path). (#721)
Update regression tests for cypher_with. (#725)
Fix issue 733 - create_complete_graph() terminates the server. (#734)
Prevent MATCH from following OPTIONAL MATCH. (#740)
Fix property constraints against resolved variables. (#724) (#751) (#701)
(#747)
Include invalid labels in reused variables. (#751) (#762)
Remove check for scalar agtypes in unwind. (#736)
Update PG11 CI workflows.
Update readme and version for python driver. (#780)
Update README.md
*

The git tag to be discussed and voted on:
https://github.com/apache/age/releases/tag/PG11/v1.3.0-rc0

The git commit hash:
commit 1a452595fe59975c1df4941e4f8eeb12c097bab7

The release files for 1.3.0, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG11/1.3.0.rc0/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release see:
https://github.com/apache/age/releases/tag/PG11/v1.3.0-rc0

!!! IMPORTANT PLEASE READ !!!

Please note that Apache REQUIRES the following information to be in your
response to the vote, in order for it to be valid -

- If you are a binding vote, a PMC, then you MUST state it in your
  response. Otherwise, leave it out. Do not mention it if you are
  not a PMC.

- You MUST state what you checked to support your vote. See
  the samples given below for guidance.

- You MUST, at a minimum, check the above tags, hash,
   links, and signatures for validity.

- You CANNOT just say, +1 or 0. You need to state what items
  you checked.

If your vote DOES NOT follow the above guidelines or samples below, it may
be thrown out.

!!! IMPORTANT PLEASE READ !!!

Please vote as follows -

+1, Release this package as Apache AGE 1.3.0 for PostgreSQL 11.
  0, I won't get in the way of the vote.
 -1, Do not release this package because 

 !!! Followed by what you checked !!!

Sample responses, two for PMCs (binding) and two for regular committers.
These are only samples, do not copy/paste.

Remember, (binding) is ONLY for PMCs. If you are not a PMC, DO NOT say
binding. If you are a PMC, you must state it.

   +1 (binding)   +1
   Checked the following:   Checked the following:
   - Signature and Hash.   - Signature and Hash.
   - Tags and Links.   - Tags and Links.
   - LICENSE and NOTICE.  - LICENSE and NOTICE.
   - No unexpected binary files. - No unexpected binary files.

-1, Failed due to 0 (binding)
Checked the following:   Checked the following:
   - Signature and Hash. - Signature and Hash.
   - Tags and Links. - Tags and Links.
   - BAD LICENSE and NOTICE.   - LICENSE and NOTICE.
   - No unexpected binary files.  - No unexpected binary files.

Again, those are just samples for guidance, DO NOT copy/paste. However,
your responses should be similar in form.

Please note that it is not a good practice to copy/paste someone else's
response, you may inadvertently misrepresent yourself or your vote.

This vote will be open for 72 hours.

Thank you for your time.

John Gemignani

Re: [VOTE] Apache AGE release 1.3.0 for PostgreSQL 11

[John Gemignani]

Dear Apache Community,

We would like to thank everyone who participated in the voting process and
are now closing this vote and will be sending out the results shortly.

John Gemignani

On Tue, May 9, 2023 at 2:30 PM John Gemignani 
wrote:

> Dear Apache Community,
>
> Please carefully read all instructions as they may have changed since the
> last vote thread.
>
> This is an official [VOTE] for Apache AGE release 1.3.0 for PostgreSQL 11.
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
> Functionalities included and addressed in this release are:
>
> *
> Release Notes for Apache AGE release v1.3.0 for PostgreSQL 11
>
> Add additional comments for create_graph function. (#582)
> Optimize age_exists function. (#586)
> Implement plus-equal operator in SET clause. (#638)
> Implement CI test for python driver. (#587)
> Move from travis CI to github actions for build. (#673)
> Update all driver CIs to Github actions.
> Fix build warnings.
> Fix golang driver workflow (#563)
> Updated Readme for drivers folder. (#642)
> Removed async from function definitions. (#680)
> Barbell graph generation (#648) and Barbell regress tests. (#708)
> Updated Python Driver ANTLR 4.9.3 -> 4.11.1 (#706)
> Modify docker url for JDBC driver tests (#716)
> Fix WITH ignoring WHERE clause. (#646)
> Implement isEmpty() predicate function. (#710)
> Fix cypher function input argument checks. (#718)
> Fix Issue 693 - server termination from return exists(path). (#721)
> Update regression tests for cypher_with. (#725)
> Fix issue 733 - create_complete_graph() terminates the server. (#734)
> Prevent MATCH from following OPTIONAL MATCH. (#740)
> Fix property constraints against resolved variables. (#724) (#751) (#701)
> (#747)
> Include invalid labels in reused variables. (#751) (#762)
> Remove check for scalar agtypes in unwind. (#736)
> Update PG11 CI workflows.
> Update readme and version for python driver. (#780)
> Update README.md
> *
>
> The git tag to be discussed and voted on:
> https://github.com/apache/age/releases/tag/PG11/v1.3.0-rc0
>
> The git commit hash:
> commit 1a452595fe59975c1df4941e4f8eeb12c097bab7
>
> The release files for 1.3.0, can be found at:
> https://dist.apache.org/repos/dist/dev/age/PG11/1.3.0.rc0/
>
> Signatures used for AGE RCs can be found in this file:
> https://downloads.apache.org/age/KEYS
>
> The fingerprint of key to sign release artifacts:
> 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
>
> For information about the contents of this release see:
> https://github.com/apache/age/releases/tag/PG11/v1.3.0-rc0
>
> !!! IMPORTANT PLEASE READ !!!
>
> Please note that Apache REQUIRES the following information to be in your
> response to the vote, in order for it to be valid -
>
> - If you are a binding vote, a PMC, then you MUST state it in your
>   response. Otherwise, leave it out. Do not mention it if you are
>   not a PMC.
>
> - You MUST state what you checked to support your vote. See
>   the samples given below for guidance.
>
> - You MUST, at a minimum, check the above tags, hash,
>links, and signatures for validity.
>
> - You CANNOT just say, +1 or 0. You need to state what items
>   you checked.
>
> If your vote DOES NOT follow the above guidelines or samples below, it may
> be thrown out.
>
> !!! IMPORTANT PLEASE READ !!!
>
> Please vote as follows -
>
> +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 11.
>   0, I won't get in the way of the vote.
>  -1, Do not release this package because 
>
>  !!! Followed by what you checked !!!
>
> Sample responses, two for PMCs (binding) and two for regular committers.
> These are only samples, do not copy/paste.
>
> Remember, (binding) is ONLY for PMCs. If you are not a PMC, DO NOT say
> binding. If you are a PMC, you must state it.
>
>+1 (binding)   +1
>Checked the following:   Checked the following:
>- Signature and Hash.   - Signature and Hash.
>- Tags and Links.   - Tags and Links.
>- LICENSE and NOTICE.  - LICENSE and NOTICE.
>- No unexpected binary files. - No unexpected binary files.
>
> -1, Failed due to 0 (binding)
> Checked the following:   Checked the following:
>- Signature and Hash. - Signature and Hash.
>- Tags and Links. - Tags and Links.
>- BAD LICENSE and NOTICE.   - LICENSE an

[RESULT][VOTE] Apache AGE release 1.3.0 for PostgreSQL 11

[John Gemignani]

Dear Apache Community,

The vote successfully passed with 3 +1 (binding) and 11 +1 (non-binding)

votes. There were no 0 or -1 votes.


Following are the detailed results :

Total of 14 (+1) votes.

3 +1(Binding): Nick Sorrel
Eya Badal Dehowe Feng 11 +1(Non Binding) Fatima Raza Carla Sanches Muneeb
Khan Arunabh Das Mohamad Mokhtar Muhammad Shoaib Rahimullah Shaheen Daniel
John Bhaskar Sharma Mahmudul Islam JawadAli Abbasi

VOTE thread:
https://lists.apache.org/thread/hc4znhck7k0074f8kvpfjfqkz341x09j

Thank you all for your participation!

John Gemignani

Re: Offset and out of bounds

[John Gemignani]

Could you give some example cases?

john

On Mon, Jun 12, 2023 at 11:12 AM Panagiotis Foliadis 
wrote:

> Hey all,
>
> I'm having a hard time understanding the offset​ functionality in
> fill_agtype_value​().
> There are many times when this function is called that the offset​ is
> greater than the
> length of the base_addr​ resulting in fetching a value from out of bounds.
> How do the
> out-of-bounds values get initialized and what are we trying to achieve by
> having the offset
> reach for the out-of-bounds values?
>

Re: Offset and out of bounds

[John Gemignani]

You are looking at why it is called, right? In gdb you can use the *up *command
to look up the call stack to see what called something.

That function, btw, will get called by anything that needs to deserialize
agtype to agtype_value, even multiple times within a single agtype, due to
nested structures.

john



On Mon, Jun 12, 2023 at 12:08 PM Panagiotis Foliadis 
wrote:

> Yes of course.
>
> When we run the basic select * from cypher
> ('test', $$ create (u) return u) as (u agtype), fill_agtype_value() is
> being called multiple times.
> There are times when its called with the base_addr having the value
> "idlabelproperties" and the offset
> helps breaking down this string to fill correctly the json object that
> will be return to the client. But there
> are cases that when the fill_agtype_value() is called, for example when
> the node we are creating has
> no label, that the offset is 32, which is larger than the length of the
> base_addr. Running gdb with
> fill_agtype_value() as a breaking point would make it easier to understand
> what im trying to say.
>
> 
> Από: John Gemignani 
> Στάλθηκε: Δευτέρα, 12 Ιουνίου 2023 10:03 μμ
> Προς: dev@age.apache.org 
> Θέμα: Re: Offset and out of bounds
>
> Could you give some example cases?
>
> john
>
> On Mon, Jun 12, 2023 at 11:12 AM Panagiotis Foliadis <
> pfolia...@hotmail.com>
> wrote:
>
> > Hey all,
> >
> > I'm having a hard time understanding the offset​ functionality in
> > fill_agtype_value​().
> > There are many times when this function is called that the offset​ is
> > greater than the
> > length of the base_addr​ resulting in fetching a value from out of
> bounds.
> > How do the
> > out-of-bounds values get initialized and what are we trying to achieve by
> > having the offset
> > reach for the out-of-bounds values?
> >
>

Re: Release Nomenclature and Process

[John Gemignani]

Hi Taylor,

Thank you for your interest in Apache AGE!

Our goal is to have a complete version of AGE for each supported version of
PostgreSQL. That is our goal. I'm sorry if that sounded too much like
marketing talk.

As our project has grown a lot in the past few months and years, we have
had to reassess our versioning, branching, support, and CI strategies. What
you are seeing right now is our team trying to iron out a lot of these
issues in real time.

So, to address your questions, given that quick background,...

For the "pre-release" tags, we are still cleaning up our release procedure
documents and process and this item needs to be addressed and clarified.
The page that you linked is outdated and needs to be corrected as well.
Thank you for bringing this to our attention.

The distinction between pre-release and release is, before and after the
Apache vote, for the official release; assuming it was successful. It
appears that was overlooked in the documentation and it too needs to be
updated.  Thank you for bringing this to our attention as well.  Btw, for
clarification, the latest release should be the highest PostgreSQL version
of AGE.

There are separate releases for each version of PostgreSQL due to,
sometimes significant, changes between the different versions of
PostgreSQL. For example, PostgreSQL 11 and 12 are significantly different
due to the removal of OIDs. This created a huge undertaking to rewrite code
to address those changes.

Our policy is to drop off support of versions of PostgreSQL as PostgreSQL
drops support for them. As for newer versions, we are currently trying to
catch up to the latest fully released versions of PostgreSQL. After we
reach that point, we will need to work out the best strategy for the beta
versions of PostgreSQL.

As for a timeline or timeframe for PostgreSQL 14 and 15 support: 14 is
nearly ready, 15 is close behind. I would rather not give anything more
specific than that because something inevitably happens to cause delays.
For example, right now we are finishing off some significant features and
bug fixes in the master. We will then be propagating them to all supported
PostgreSQL versions and then 14 and 15.

For clarification, the latest versions of AGE are 1.3.0 and are available
for PostgreSQL 11, 12, & 13.

Hopefully this helps cover all of your questions. If not, please let me
know.

I should point out that our policies are always subject to change if a
better approach is found.

john

On Mon, Jun 26, 2023 at 10:09 AM Riggan, Taylor 
wrote:

> Hi all,
>
> In reviewing the Release process on the website (
> https://age.apache.org/contribution/process) I'm not seeing any reference
> to "pre-releases".  There are currently two pre-releases available on the
> GitHub repo (1.2.0 and 1.3.0) for Apache AGE.  What constitutes a release
> being a "pre-release" and when does this become a full "release"?
>
> There are also separate releases for each version of Postgres.  What is
> the rationale behind having separate releases for each Postgres release
> versus building a version scheme that mirrors the Postgres versioning?
>
> What is the policy for back-porting bugs/features for older version of
> Postgres?  Is there intent to always maintain a version of Apache AGE for
> every version of Postgres starting with v11, or will support for older
> versions drop off at some point?   Along those same lines, what is the
> planned cadence (or lag) for keeping up with Postgres versions?  Postgres
> is now shipping 16-beta.  Which means there are production versions of
> Postgres 14 and 15.  When will Apache AGE have support for those versions?
>
> Thank you,
>
> --
> Taylor Riggan
> Sr. Graph Architect | Amazon Neptune | AWS
>
>

[DISCUSS] Apache AGE 1.4.0 Release for PostgreSQL 14

[John Gemignani]

Dear Apache Community,

We would like to open a discussion for the Apache AGE release 1.4.0 for
PostgreSQL 14.

To learn more about Apache AGE, please see http://age.apache.org/

Functionalities included and addressed in this release are:

*
Release Notes for Apache AGE release v1.4.0 for PostgreSQL 14

NOTE: This is an initial release of PG14. There are no upgrade
  scripts to this release.

NOTE: Some of these reference the master branch PR that was
  either applied to lower versions via a separate PR or
  merged into a newly created branch.

Added license in Python driver README.md (#956)
Added the toStringList() function (#1128)
Added toBooleanList() (#1165)
Added toFloatList() function (#1016)
Added toIntegerList() function (#1025)
Added regression tests for MATCH clause using labels only (#1019)
Added REGTYPEOID to toString function (#1036)
Added Dockerfile.dev & move docker-related files to "docker/" (#943)
Fixed complex MERGE causes crash (#897) (#961)
Fixed docker build files (#1104)
Fixed case sensitivity on label usage of reserved keyword (#1040)
Fixed issue 1000: Indexes created on WHERE (#1133)
Fixed issue 1002: Invalid reuse of variables in MATCH clause (#1003)
Fixed issue 1033: access operator on vle edge lists (#1037)
Fixed issue 1043: ERROR:  container must be an array or object (#1046)
Fixed issue 1124: Segmentation fault when using specific tables (#1125)
Fixed issue 395: ERROR: container is not an agtype array (#1039)
Fixed issue 870: regarding orderability and added regression tests (#994)
Fixed issue 876: column reference "_age_default_alias_0" is ambiguous (#931)
Fixed issue 975: Invalid reuse of variables in CREATE clause (#977)
Fixed issue 989: Impossible to create array with > 100 items (#1001)
Fixed memory leak issues with age_load (#1142)
Fixed memory leaks in MERGE (merge_edge & merge_vertex) (#958)
Fixed MERGE crashes due to incorrect label type (#957)
Fixed MERGE variable reuse (#997)
Fixed misspellings in many AGE files (#985)
Fixed warning messages in DockerHub builds. (#1075)
Modified test_agtypes to view useful testing message (#992)
Optimised Antlr4ResultHandler initialization (#1169)
Updated CIs to pull correct image based on branch (#1105)
Updated files, format, and version information (#1063)
Updated README.

*

The git tag to be discussed and voted on:
https://github.com/apache/age/releases/tag/PG14/v1.4.0-rc0

The git commit hash:
commit a33b3cf996edaa6d334e30a153ad1ff712c65518

The release files for 1.4.0, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG14/1.4.0.rc0/

Signatures used for AGE RCs can be found in this file:
https://downloads.apache.org/age/KEYS

The fingerprint of key to sign release artifacts:
4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045

For information about the contents of this release see:
https://github.com/apache/age/releases/tag/PG14/v1.4.0-rc0

Please verify the above links, files, and signatures in addition to sharing
your thoughts and feedback and if we can call for a vote.

Thank you for your time.

John Gemignani

Re: [DISCUSS] Apache AGE 1.4.0 Release for PostgreSQL 14

[John Gemignani]

Dear Apache Community,

Since there are no objections, I am closing the DISCUSS thread and will
open the official VOTE thread for Apache AGE 1.4.0 for PostgreSQL 14
shortly.

Thank you all for your input.


John Gemignani


On Wed, Aug 30, 2023 at 9:33 AM Muhammad Shoaib 
wrote:

> Looks good.
> - Verified signature
> - Checked commit hash and links
> - Checked License and Notice file
> - Checked for binary files
>
>
>
> On Wed, 30 Aug 2023 at 18:31, Rafsun Masud  wrote:
>
> > +1 Looks good.
> > - Verified signature
> > - Checked commit hash and links
> > - Checked License and Notice file
> > - Checked for binary files
> >
> > Thanks for the good work!
> >
> > Regards,
> > Rafsun Masud
> >
> >
> > On Tue, Aug 29, 2023 at 3:51 PM Dehowe Feng 
> > wrote:
> >
> > > Looks good to me. Exciting for this release
> > >
> > > I checked the signature and hash,
> > > tags and links,
> > > the license and notice,
> > > made sure there was no unexpected binary files.
> > >
> > > I also reviewed the patch notes as well
> > >
> > > Cheers.
> > >
> > > On Wed, Aug 23, 2023 at 12:12 PM John Gemignani <
> > > john.gemign...@bitnine.net>
> > > wrote:
> > >
> > > > Dear Apache Community,
> > > >
> > > > We would like to open a discussion for the Apache AGE release 1.4.0
> for
> > > > PostgreSQL 14.
> > > >
> > > > To learn more about Apache AGE, please see http://age.apache.org/
> > > >
> > > > Functionalities included and addressed in this release are:
> > > >
> > > > *
> > > > Release Notes for Apache AGE release v1.4.0 for PostgreSQL 14
> > > >
> > > > NOTE: This is an initial release of PG14. There are no upgrade
> > > >   scripts to this release.
> > > >
> > > > NOTE: Some of these reference the master branch PR that was
> > > >   either applied to lower versions via a separate PR or
> > > >   merged into a newly created branch.
> > > >
> > > > Added license in Python driver README.md (#956)
> > > > Added the toStringList() function (#1128)
> > > > Added toBooleanList() (#1165)
> > > > Added toFloatList() function (#1016)
> > > > Added toIntegerList() function (#1025)
> > > > Added regression tests for MATCH clause using labels only (#1019)
> > > > Added REGTYPEOID to toString function (#1036)
> > > > Added Dockerfile.dev & move docker-related files to "docker/" (#943)
> > > > Fixed complex MERGE causes crash (#897) (#961)
> > > > Fixed docker build files (#1104)
> > > > Fixed case sensitivity on label usage of reserved keyword (#1040)
> > > > Fixed issue 1000: Indexes created on WHERE (#1133)
> > > > Fixed issue 1002: Invalid reuse of variables in MATCH clause (#1003)
> > > > Fixed issue 1033: access operator on vle edge lists (#1037)
> > > > Fixed issue 1043: ERROR:  container must be an array or object
> (#1046)
> > > > Fixed issue 1124: Segmentation fault when using specific tables
> (#1125)
> > > > Fixed issue 395: ERROR: container is not an agtype array (#1039)
> > > > Fixed issue 870: regarding orderability and added regression tests
> > (#994)
> > > > Fixed issue 876: column reference "_age_default_alias_0" is ambiguous
> > > > (#931)
> > > > Fixed issue 975: Invalid reuse of variables in CREATE clause (#977)
> > > > Fixed issue 989: Impossible to create array with > 100 items (#1001)
> > > > Fixed memory leak issues with age_load (#1142)
> > > > Fixed memory leaks in MERGE (merge_edge & merge_vertex) (#958)
> > > > Fixed MERGE crashes due to incorrect label type (#957)
> > > > Fixed MERGE variable reuse (#997)
> > > > Fixed misspellings in many AGE files (#985)
> > > > Fixed warning messages in DockerHub builds. (#1075)
> > > > Modified test_agtypes to view useful testing message (#992)
> > > > Optimised Antlr4ResultHandler initialization (#1169)
> > > > Updated CIs to pull correct image based on branch (#1105)
> > > > Updated files, format, and version information (#1063)
> > > > Updated README.
> > > >
> > > > **

[DISCUSS] Apache AGE 1.4.0 Release for PostgreSQL 14

[John Gemignani]

lowing:

   - Signature and Hash. - Signature and Hash.

   - Tags and Links. - Tags and Links.

   - BAD LICENSE and NOTICE.   - LICENSE and NOTICE.

   - No unexpected binary files.  - No unexpected binary files.



Again, those are just samples for guidance, DO NOT copy/paste. However,
your responses should be similar in form.


Please note that it is not a good practice to copy/paste someone else's
response either, you may inadvertently misrepresent yourself or your vote.


This vote will be open for 72 hours.


Thank you for your time.


John Gemignani

Re: [DISCUSS] Apache AGE 1.4.0 Release for PostgreSQL 14

[John Gemignani]

Please do not respond to this as it has the incorrect subject.

john

On Wed, Sep 6, 2023 at 12:09 PM John Gemignani 
wrote:

> Dear Apache Community,
>
> Please carefully read all instructions as they may have changed since the
> last vote thread.
>
> This is an official vote for Apache AGE release 1.4.0 for PostgreSQL 14.
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
> Functionalities included and addressed in this release are:
>
> *
> Release Notes for Apache AGE release v1.4.0 for PostgreSQL 14
>
> NOTE: This is an initial release of PG14. There are no upgrade
>   scripts to this release.
>
> NOTE: Some of these reference the master branch PR that was
>   either applied to lower versions via a separate PR or
>   merged into a newly created branch.
>
> Added license in Python driver README.md (#956)
> Added the toStringList() function (#1128)
> Added toBooleanList() (#1165)
> Added toFloatList() function (#1016)
> Added toIntegerList() function (#1025)
> Added regression tests for MATCH clause using labels only (#1019)
> Added REGTYPEOID to toString function (#1036)
> Added Dockerfile.dev & move docker-related files to "docker/" (#943)
> Fixed complex MERGE causes crash (#897) (#961)
> Fixed docker build files (#1104)
> Fixed case sensitivity on label usage of reserved keyword (#1040)
> Fixed issue 1000: Indexes created on WHERE (#1133)
> Fixed issue 1002: Invalid reuse of variables in MATCH clause (#1003)
> Fixed issue 1033: access operator on vle edge lists (#1037)
> Fixed issue 1043: ERROR:  container must be an array or object (#1046)
> Fixed issue 1124: Segmentation fault when using specific tables (#1125)
> Fixed issue 395: ERROR: container is not an agtype array (#1039)
> Fixed issue 870: regarding orderability and added regression tests (#994)
> Fixed issue 876: column reference "_age_default_alias_0" is ambiguous
> (#931)
> Fixed issue 975: Invalid reuse of variables in CREATE clause (#977)
> Fixed issue 989: Impossible to create array with > 100 items (#1001)
> Fixed memory leak issues with age_load (#1142)
> Fixed memory leaks in MERGE (merge_edge & merge_vertex) (#958)
> Fixed MERGE crashes due to incorrect label type (#957)
> Fixed MERGE variable reuse (#997)
> Fixed misspellings in many AGE files (#985)
> Fixed warning messages in DockerHub builds. (#1075)
> Modified test_agtypes to view useful testing message (#992)
> Optimised Antlr4ResultHandler initialization (#1169)
> Updated CIs to pull correct image based on branch (#1105)
> Updated files, format, and version information (#1063)
> Updated README.
>
> *
>
>
> !!! PLEASE VERIFY ALL of the below tags, hash, links, signatures, and keys
> !!!
>
> The git tag to be discussed and voted on:
> https://github.com/apache/age/releases/tag/PG14/v1.4.0-rc0
>
> The git commit hash:
> commit a33b3cf996edaa6d334e30a153ad1ff712c65518
>
> The release files for 1.4.0, can be found at:
> https://dist.apache.org/repos/dist/dev/age/PG14/1.4.0.rc0/
>
> Signatures used for AGE RCs can be found in this file:
> https://downloads.apache.org/age/KEYS
>
> The fingerprint of key to sign release artifacts:
> 4293 0603 8E35 AC05 4DBB  4B58 26B6 CD9D CD5B 0045
>
> For information about the contents of this release see:
> https://github.com/apache/age/releases/tag/PG14/v1.4.0-rc0
>
> *
>
>
> !!! IMPORTANT PLEASE READ !!!
>
>
> Please note that Apache REQUIRES the following information to be in your
> response to the vote, in order for it to be valid -
>
>
> - If you are a binding vote, a PMC, then you MUST state it in your
>
>   response. Otherwise, leave it out. Do not mention it if you are
>
>   not a PMC.
>
>
> - You MUST state what you checked to support your vote. See
>
>   the samples given below for guidance.
>
>
> - You MUST, at a minimum, check the above tags, hash,
>
> links, and signatures for validity.
>
>
> - You CANNOT just say, +1 or 0. You need to state what items
>
>   you checked.
>
>
> If your vote DOES NOT follow the above guidelines or samples below, it may
> be thrown out.
>
>
> !!! IMPORTANT PLEASE READ !!!
>
>
> Please vote as follows -
>
>
> +1, Release this package as Apache AGE 1.4.0 for PostgreSQL 14.
>
>   0, I won't get in the way of the vote.
>
>  -1, Do not release this package because 
>
>
>  !!! Followed by what you checked !!!
>
>
> 

[VOTE] Apache AGE 1.4.0 Release for PostgreSQL 14

[John Gemignani]

sh. - Signature and Hash.
   - Tags and Links. - Tags and Links.
   - BAD LICENSE and NOTICE.   - LICENSE and NOTICE.
   - No unexpected binary files.  - No unexpected binary files.


Again, those are just samples for guidance, DO NOT copy/paste. However,
your responses should be similar in form.


Please note that it is not a good practice to copy/paste someone else's
response either, you may inadvertently misrepresent yourself or your vote.

This vote will be open for 72 hours.

Thank you for your time.

John Gemignani