Re: [I] Proposal: Vector handling with extension(pgvector) [age]

[Josh Innis]

Wouldn't count on it

On Sun, Aug 11, 2024 at 11:01 AM tan-yong-sheng (via GitHub) 
wrote:

>
> tan-yong-sheng commented on issue #1121:
> URL: https://github.com/apache/age/issues/1121#issuecomment-2282805503
>
>Hi, just wanna follow up on this... I wish to try both postgres's
> extension: `apache age` with `pgvector`... Is the docker-compose image
> working for both extensions? Thanks, and hope for reply.
>
>
> --
> 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: [VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13

[Josh Innis]

+1

On Wed, Apr 12, 2023 at 12:50 AM Nicholas Sorrell  wrote:

> +1 binding
> 
> From: Dehowe Feng 
> Sent: Tuesday, April 11, 2023 11:22:07 AM
> To: dev@age.apache.org 
> Subject: Re: [VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13
>
> +1 (binding),
>
> Did all of the usual checks, looks good.:
>  - checked the signature and hash
>  - checked tags and links
>  - License and Notice looks good
>  - checked for unexpected binary files
>
> On Tue, Apr 11, 2023 at 7:11 AM Maaz Ahmad  wrote:
>
> >  +1
> >
> > Checked the following:
> >
> > - Signature and hash - checked.
> > - Tags and links - checked.
> > - LICENSE and NOTICE - checked.
> > - No unexpected binary files - checked
> >
> >
> > On Tue, 11 Apr 2023 at 04:42, John Gemignani  >
> > wrote:
> >
> > > 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

Re: [VOTE] Apache AGE 1.1.0 for PG12 Release

[Josh Innis]

+1

On Sat, Nov 5, 2022 at 9:20 AM Jasper Blues 
wrote:

> +1
>
> > On 5 Nov 2022, at 10:16 am, Eya Badal Abdisho 
> wrote:
> >
> > +1 I checked the following.
> >
> >  - PGP Signatures.
> > - SHA512 Checksums.
> >  - LICENSE and NOTICE are fine.
> >
> > Thank you for the great release and work.
> >
> > Best regards,
> >
> >
> > On Fri, Nov 4, 2022 at 11:40 AM John Gemignani <
> john.gemign...@bitnine.net>
> > 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  -
> Add
> >>   access operator (->, ->>) to Agtype.
> >>   - Fix github issue #220  -
> >> fix
> >>   local cached contexts for static procedures.
> >>   - Fix github issue #224  -
> fix
> >>   regression tests to fix issues on mac with trigonometric functions.
> >>   - Fix github issue #235  -
> >>   when MERGE and SET were used together.
> >>   - Fix github issue #240  -
> >>   negative array bounds.
> >>   - Fix github issue #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
> >> 
> >>
> >>
> >>
> >> 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
> >> 
> >>
> >>
> >>
> >> 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.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
> >>
> >
> >
> > --
> >
> > Bitnine Global, Inc. - We create value for our clients by connecting the
> > world's data.
> >
> >
> > *Eya Badal Abdisho*
> >
> > Technical Engineer
> >
> > E-mail : eya.abdi...@bitnine.net 
> >
> > Mobile : +1 408-966-3301
> >
> > 3945 Freedom Cir., Suite 260,
> > Santa Clara, CA 95054
> >
> > www.bitnine.net
>
>

Re: AGE Unable to install properly

[Josh Innis]

Hello,

Which version of Postgres are you using?


On Wed, Aug 24, 2022 at 8:54 AM ~~~ <1026398...@qq.com.invalid> wrote:

> Hello Sir：
> When we installed Linux using source code, we were unable to install, and
> the error message could not find pg_class_d.h, pg_namespace_d.h file.
>
>
> We do not know how to solve this problem, can you help me to complete the
> installation

Re: [VOTE] Release Apache AGE 1.1.0-rc0

[Josh Innis]

+1 (Binding)

All links are valid
Commit hash is correct
verified the hash and signature

On Fri, Aug 12, 2022 at 8:37 AM John Gemignani 
wrote:

> 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
> >
>

[DISCUSS] How Docker can support multiple versions of Postgres

[Josh Innis]

Hello All,

We are currently working on the Postgres 12 version of AGE and nearing
completion. However there is an issue with the Dockerfile. The line:

FROM postgres:11

in the Dockerfile obviously needs to change for Postgres 12, however we
still want to support Postgres 11. Given that the different versions will
be in separate branches, what is a good way to approach this problem?

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

[Josh Innis]

Hi Nick,

Do we know why the original 0.7.0 tag wasn't building on Docker? Also,
given the JIRA ticket: https://issues.apache.org/jira/browse/INFRA-22727
only allows for this regex: /^v(\d+\.\d+\.\d+)$” Does this mean the rc.*
tags are not included?

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
>
> 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] Apache AGE 1.0.0-rc1 Release

[Josh Innis]

+1

[x] incubating in name
[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] LICENSE, NOTICE and DISCLAIMER files exist.
[x] All files have license headers if necessary.

On Wed, Mar 30, 2022 at 4:38 PM 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: [VOTE] Apache AGE 1.0.0 Release

[Josh Innis]

+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
>

[DISCUSS] AGE Versioning in Master

[Josh Innis]

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 Viewer 1.0.0 (rc2) Release

[Josh Innis]

+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] Website Overhaul

[Josh Innis]

Awesome Research. As long as we can maintain documentation for all our
versions, I agree we should overhaul the website. Improving our SEO and
making it easier for people to contribute to the project are crucial
concerns for us helping us grow the community. As for the static site
generator we use: I think using the tool with the largest and most active
community is probably best. It will mean that there is better support and
likely more robust feature set and documentation to take advantage of.

On Thu, Feb 10, 2022 at 5:51 PM Nicholas Sorrell  wrote:

> I did some research tonight and here are my findings.
>
> - Are there examples of other sites using Hugo? There are sites using
> static site generators (SSG) and below is a quick survey of what's being
> used.
>   + The following sites use docusaurus (MIT)
>  * Yunikorn: https://github.com/apache/incubator-yunikorn-site
>  * InLong: https://github.com/apache/incubator-inlong-website
>  * Shenyu: https://github.com/apache/incubator-shenyu-website
>  * Linkis: https://github.com/apache/incubator-linkis-website
>  * Seatunnel: https://github.com/apache/incubator-seatunnel-website
>  * Eventmesh: https://github.com/apache/incubator-eventmesh-site
>  * StreamPipes:
> https://github.com/apache/incubator-streampipes-website
>   + The following sites use Jekyll (MIT)
>  * Nuttx: https://github.com/apache/incubator-nuttx-website
>  * brpc: https://github.com/apache/incubator-brpc-website
>  * Tuweni: https://github.com/apache/incubator-tuweni-website
>  * Wayang: https://github.com/apache/incubator-wayang-website
>  * Pegasus: https://github.com/apache/incubator-pegasus-website
>  * Livy: https://github.com/apache/incubator-livy-website
>   + The following sites use Vuepress (MIT)
>  * Doris: https://github.com/apache/incubator-doris-website
>  * Teaclave: https://github.com/apache/incubator-teaclave-website
>   + The following sites use Hugo (Apache)
>  * Kyuubi: https://github.com/apache/incubator-kyuubi-website
> (doesn't do docs)
>   + The following sites use Eleventy (MIT)
>  * Annotator: https://github.com/apache/incubator-annotator-website
>
> - Can we maintain multiple versions of the docs using Hugo?
>   + I think so. If using Docsy, they address that here:
> https://www.docsy.dev/docs/adding-content/versioning/
>  * An example of a site doing this is here (top right corner is
> version switcher): https://www.kubeflow.org/docs/
>   + I also found Doks, which is an npm wrapper around Hugo. This page
> describes versioning:
> https://getdoks.org/docs/extensions/versioned-documentation/
>
>
>
> 
> From: Jasper Blues 
> Sent: Thursday, February 10, 2022 4:36 PM
> To: dev@age.apache.org 
> Subject: Re: [DISCUSS] Website Overhaul
>
> Sounds great. Also visible links in and out of the site should help with
> Google site ranking as well as sharing. For example, by giving bloggers,
> social media users etc links that relate directly to their talking points.
>
>
> > On Feb 10, 2022, at 10:02 PM, Nicholas Sorrell  wrote:
> >
> > All,
> >
> > I wanted to propose that we overhaul the website (
> https://github.com/apache/incubator-age-website) to make it easier to
> contribute to, easier to modify, more extensible, more accessible, and
> easier to optimize for searching and performance.
> >
> > When I created the site, there were a couple of a factors in the design
> decisions:
> >
> > Time - we were racing to get something done and presentable before a
> conference the team was presenting at. This meant creating a site with
> minimal "flare."
> > Libraries - when we built the site way back then, we weren't sure what
> 3rd party libraries we could incorporate. We weren't sure if Apache had
> rules limiting the use of them, so we chose to use no libraries. This also
> impacted the site (negatively in my opinion).
> >
> > Since then, we've seen other Apache sites using 3rd party libs and we
> now have time to redesign the site. I propose that we redesign the site
> using Hugo. This gives us the ability to utilize Markdown, which is much
> more accessible for contributors, and also offers more extensibility
> through themes and plugins. I think it could also make the process of
> generating the docs easier but I haven't fully investigated that.
> >
> > Another negative about the current website is linking to content.
> Because of the way that I've utilized anchors to show/hide content, this
> keeps the URL slug the same no matter where you go, which makes it
> difficult to share, for example, a "Getting Started" page with someone.
> >
> > So in summary, here are the potential benefits I see:
> > + easier to modify: because the content is written in markdown, it is
> easier for people change existing pages without knowledge of HTML/CSS/JS
> > + easier to contribute: again, because we will use markdown for content,
> it is easier for people to contribute new content
> >

Re: [DISCUSS] Apache AGE Roadmap

[Josh Innis]

This is a great list of ideas. Also maybe we should add Label Inheritance
to the list of features. That was a very powerful feature in Apache AGE's
predecessor that we should consider adding.

On Mon, Feb 14, 2022 at 10:53 AM Eya Badal  wrote:

> Dear AGE community,
>
> I would like to initiate a discussion and propose the following roadmap for
> Apache AGE.
>
>
>-
>
>Supporting PG 12 and beyond
>-
>
>Improve User Interface
>-
>
>   AGE CLI
>   -
>
>   Procedural Languages
>   -
>
>   Improve and Add Drivers
>   -
>
>   API
>   -
>
>  Rest API
>  -
>
>  GraphQL
>  -
>
>Distributed Database (Citius and/or ShardingSphere)
>-
>
>Graph Machine Learning and AI
>-
>
>   Knowledge Graphs
>   -
>
>   Deep Learning
>   -
>
>   Anomaly Detection
>   -
>
>   Natural Language Processing
>   -
>
>   Graph Coloring
>   -
>
>   PageRank
>   -
>
>Graph Analytics
>-
>
>   Flow Network
>   -
>
>   Centrality
>   -
>
>   Betweenes
>   -
>
>   Segmentation
>   -
>
>   Degree
>   -
>
>   Distance
>   -
>
>   Connectivity
>   -
>
>Graph Traversal (Expanding the VLE)
>-
>
>   Breadth-First Search
>   -
>
>   Shortest Path: Dijkstra, Bellman-Ford, All-pair shortest path,
>   Floyd-Warshall, Johns Algorithm, Viterbi Algorithm, etc
>   -
>
>   A*
>   -
>
>Graph Generation
>-
>
>Performance Tuning
>-
>
>Improve Documentation:
>-
>
>   More Dataset for AGE
>   -
>
>   Complete Cypher Documentation
>   -
>
>   More Use Cases
>   -
>
>Backup and High Availability Tools
>-
>
>Migration Tools:
>-
>
>   Improve the import and export process
>   -
>
>   Migration Script
>   -
>
>PG style indexing
>-
>
>Implement CALL … [YIELD]
>-
>
>EXCEPT and INTERSECT clauses
>-
>
>Add ON CREATE and ON MATCH to MERGE
>-
>
>Datasets
>-
>
>Website Improvement
>-
>
>Improve AGE Viewer
>-
>
>   Rest API
>   -
>
>   Dockerfile
>   -
>
>   etc
>   -
>
>AGE Tutorial:
>-
>
>   Video, webinars, etc
>   -
>
>Add Gremlin Query Language
>-
>
>Add SPARQL
>
>
>
> Looking forward to hearing everyone's thoughts and feedback.
>
> Best regards,
> Eya
>

Re: [DISCUSS] Website Overhaul

[Josh Innis]

As Pieterjan said, Sphinx allows us to have documentation for each release,
which is a useful feature to have and we should try and keep it. However,
if we are creating a new website then one of the side goals for
accessibility should be a consistent theme throughout the website. Does
Hugo and Sphinx have overlapping theme templates that could allow us to
have both?

On Thu, Feb 10, 2022 at 6:50 AM Pieterjan De Potter
 wrote:

> I think this is a great idea.
>
> The current website consists of a single HTML page, which indeed makes
> it more difficult to maintain, contribute to and link to content.
>
> I'm also in favor of using a static site generator to generate HTML out
> of Markdown. Hugo seems to be one of the most (if not the most) popular
> ones around, but I personally haven't used it yet.
>
> Are there examples of other Apache sites using Hugo?
>
> The documentation has already been converted to Markdown by Joe Fagan
> and Josh Innis. Currently, Sphinx
> (https://www.sphinx-doc.org/en/master/) is used to generate HTML pages.
> In the current setup, multiple versions of the documentation can be
> generated, which is not yet possible with Hugo as far as I could find
> (https://github.com/google/docsy/issues/114).
>
> Best regards,
> Pieterjan
>
>
> On 10.02.22 15:02, Nicholas Sorrell wrote:
> > All,
> >
> > I wanted to propose that we overhaul the website (
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-age-website&data=04%7C01%7CPieterjan.DePotter%40ugent.be%7Cffb7ffea9a1945fe276108d9ec9df500%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C637800986184870331%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=e9J1J1i%2BIcLVZ2W2KsWvwSQTOEHg%2FFQb0J2rnhPNgqI%3D&reserved=0)
> to make it easier to contribute to, easier to modify, more extensible, more
> accessible, and easier to optimize for searching and performance.
> >
> > When I created the site, there were a couple of a factors in the design
> decisions:
> >
> > Time - we were racing to get something done and presentable before a
> conference the team was presenting at. This meant creating a site with
> minimal "flare."
> > Libraries - when we built the site way back then, we weren't sure what
> 3rd party libraries we could incorporate. We weren't sure if Apache had
> rules limiting the use of them, so we chose to use no libraries. This also
> impacted the site (negatively in my opinion).
> >
> > Since then, we've seen other Apache sites using 3rd party libs and we
> now have time to redesign the site. I propose that we redesign the site
> using Hugo. This gives us the ability to utilize Markdown, which is much
> more accessible for contributors, and also offers more extensibility
> through themes and plugins. I think it could also make the process of
> generating the docs easier but I haven't fully investigated that.
> >
> > Another negative about the current website is linking to content.
> Because of the way that I've utilized anchors to show/hide content, this
> keeps the URL slug the same no matter where you go, which makes it
> difficult to share, for example, a "Getting Started" page with someone.
> >
> > So in summary, here are the potential benefits I see:
> > + easier to modify: because the content is written in markdown, it is
> easier for people change existing pages without knowledge of HTML/CSS/JS
> > + easier to contribute: again, because we will use markdown for content,
> it is easier for people to contribute new content
> > + more extensible: because Hugo has a large ecosystem, we can tap into
> the work of others
> > + more accessible:  this redesign will also have a focus on
> accessibility so all users can engage with the content
> > + better SEO:  designing with SEO in mind so that users can find out
> about AGE is important
> > + possibly easier to build docs: right now we're using a Github workflow
> to generate these, and we could possibly wrap all of this into a single
> step of static site generation with Hugo
> > + possible blog:  another important aspect of both SEO and community
> engagement is a blog, which can show examples and use cases of AGE's new
> functionality with each release. The approval process for blog posts should
> probably part of a separate conversation.
> >
> > Looking forward to hearing the community's thoughts.
> >
> > Thanks,
> > Nick Sorrell
> >
> >
>

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

[Josh Innis]

Hi Trista,

[1] When AGE Viewer was donated to Apache, it already supported both
AgensGraph and AGE as backend database connections. To completely remove
all references to AgensGraph would mean removing AGE Viewer's ability to
connect to AgensGraph as a backend database.
[2] Before AGE was donated to Apache, its name was AgensGraph-Extension. In
the proposal process, the community determined that the project had to be
renamed. AgensGraph itself is not a part of Apache.

Thanks,
Josh

On Thu, Feb 3, 2022 at 4:28 AM Juan Pan  wrote:

> Hi Josh,
>
>
> Actually, our ppmc of AGE more care about AGE project (its brand,
> community, etc.) rather than AgensGraph.
> My suggestion is to erase the marks around them as possible as we can for
> safety, based on
> 1. Why do our AGE viewer need to be compatible with AgensGraph? Is
> AgensGraph part of this incubator project?
> 2. AgensGraph is suggested to be renamed in gene...@incubator.ml by other
> IPMCs, I remember?
>
>
> Best,
> Trista
>
> --
> Trista Pan, Twitter: @tristaZero
>
>
> On 02/3/2022 01:26，Josh Innis wrote：
> HI Juan,
>
> 1. AGE Viewer connects to two databases: Apache AGE and AgensGraph. No code
> from AgensGraph resides in AGE Viewer. When AGE Viewer is connected to
> AgensGraph, is it an issue if AGE Viewer gives a context specific language
> in code or in messages given to the user?
>
> For example:
> backend/src/util/JsonBuilder.js:66
> if (flavor === 'AGE') {
> return AGECreateEdge(client, graphPathStr, createQ);
> } else {
> return AgensGraphCreateEdge(client, graphPathStr, createQ);
> }
>
> Since AgensGraphCreateEdge is used only when AGE Viewer is connected to
> AgensGraph, is it necessary to change it?
>
> 2. Some of the results are for modules that handles the connection to the
> database. It looks like this is from when the source code was originally
> donated to Apache from Bitnine. These modules probably need to be renamed
> to something generic.
>
> 3. Since AGE Viewer originally connected to AgensGraph and extended to
> support AGE there are some hardcoded values that need to be altered.
>
> For example:
> frontend/src/components/frame/presentations/ServerStatusFrame.jsx:86
> if (status === 'disconnected') {
> return (
> ...
> Connection Status
> You are currently not connected to AgensGraph
> ...
>
> This code displays a message to the user when there is a connection error.
> Personally, I think this needs a conditional expression for the type of
> database the user is connecting to, but if all references to Agensgraph
> need to be removed it could instead display: You are currently not
> connected for all database connection types.
>
> 4. Many of the results come from the file
> frontend/src/documents/tutorial/northwind.jsx. This file is a tutorial that
> shows how to use AGE Viewer with AgensGraph. Should this file be removed?
>
> On Wed, Feb 2, 2022 at 3:39 AM Juan Pan  wrote:
>
> I also have no idea about this vote.
>
>
> I tracked the whole thread and found others raised some issues, but some
> have had no feedback so far. Could anyone sync me this vote is still in the
> process and double check the issue I mentioned?
>
>
> It is the first time for the community to release AGE-view. It is
> efficient to solve all the potential issues internally and definitely will
> cost our lots of efforts and patients.
>
>
> My check list,
>
>
> [x] Download links are valid.
> [x] Checksums and PGP signatures are valid.
> [ ] LICENSE, NOTICE and DISCLAIMER files are correct. (Need double check)
> [x] All files have license headers if necessary.
>
>
> Most of the files are fine, but it still has some bits around AgensGraph
> or bitnine.
>
>
> Run
> ```
> grep bitnine . -R -n
> grep AgensGraph  . -R -n
> ```
> It will show you, like
> ```
> ./frontend/src/components/frame/presentations/ServerStatusFrame.jsx:92:
> You are currently not connected to AgensGraph
> ./frontend/src/components/frame/presentations/ServerDisconnectFrame.jsx:32:
> disconnectToAgensGraph,
> ```
>
>
> Please keep in mind Apache AGE totally has nothing to do with AgensGraph
> or bitnine business currently and in the future. (Maybe AgensGraph is in
> consideration to rename?)
>
>
>
>
>
> --
> Juan Pan(Trista), Twitter: @tristaZero
>
>
> On 02/1/2022 02:10，John Gemignani wrote：
> 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 contin

Re: [DISCUSS] Ambiguity in the MERGE Specification

[Josh Innis]

I made a Jira ticket to allow this topic to be a configuration option:
https://issues.apache.org/jira/browse/AGE2-656. I propose for the 0.8.0
release the option is to make a right directed edge, as Neo4J does.
Please give your thoughts.

On Mon, Jan 24, 2022 at 6:36 PM Josh Innis  wrote:

> Personally I think long term: Alex brings up a good point with the GUC
> configuration. Let the database owner decide the behavior.
>
> On Mon, Jan 24, 2022 at 6:15 PM Josh Innis  wrote:
>
> > A directed graph and undirected graph both excel at modeling different
> > problems and are used by an overlapping (though neither is a subset of
> the
> > other) set of algorithms. AGE, Neo4J and cypher are all directed models
> > that have some undirected features, which are  inherently designed to be
> > ambiguous (such as MATCH with no direction given). The AGE edge datatype
> is
> > not designed to handle true undirected edges, and can only emulate them
> > using two directed edges. Which mathematically speaking and from an
> > algorithm design point of view have some subtle differences.
> >
> > On Mon, Jan 24, 2022 at 6:07 PM Jasper Blues  >
> > wrote:
> >
> >> Sounds reasonable 👍
> >>
> >> Officially the docs say undefined, so please don’t rely upon it.
> >> But the defacto standard is consistent.
> >>
> >> The model is a directed graph, but when direction does not matter,
> CYPHER
> >> allows to ignore it.
> >>
> >> Are there some cases where adding support for true undirected edges adds
> >> value over the above approach?
> >>
> >> > On Jan 25, 2022, at 10:01 AM, Josh Innis  wrote:
> >> >
> >> > I have spent some time on the Neo4J console. I was running this set of
> >> > commands:
> >> >
> >> > 1. MERGE ({side: 'left'})-[:edge]-({side:'right'})
> >> > 2. MATCH (l{side: 'left'})-[:edge]->(r{side:'right'}) RETURN l, r
> >> > 3. MATCH (l{side: 'left'})<-[:edge]-(r{side:'right'}) RETURN l, r
> >> > 4. MATCH (n) DETACH DELETE n
> >> >
> >> > No matter how many times I deleted the nodes and ran the merge
> command:
> >> > Line 2 returns 1 row and line 3 returns 0 rows. Even though the
> >> > documentation says it is ambiguous, for the version freely
> >> > available for what is the defacto standard: this ambiguous query will
> >> > always create relationships going left to right.
> >> >
> >> > 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 <
> >> john.gemign...@bitnine.net
> >> >>>
> >> >> 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 <
> >> jas...@liberation-data.com
> >> >>>
> >> >>> 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 

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

[Josh Innis]

HI Juan,

1. AGE Viewer connects to two databases: Apache AGE and AgensGraph. No code
from AgensGraph resides in AGE Viewer. When AGE Viewer is connected to
AgensGraph, is it an issue if AGE Viewer gives a context specific language
in code or in messages given to the user?

For example:
backend/src/util/JsonBuilder.js:66
if (flavor === 'AGE') {
 return AGECreateEdge(client, graphPathStr, createQ);
} else {
 return AgensGraphCreateEdge(client, graphPathStr, createQ);
}

Since AgensGraphCreateEdge is used only when AGE Viewer is connected to
AgensGraph, is it necessary to change it?

2. Some of the results are for modules that handles the connection to the
database. It looks like this is from when the source code was originally
donated to Apache from Bitnine. These modules probably need to be renamed
to something generic.

3. Since AGE Viewer originally connected to AgensGraph and extended to
support AGE there are some hardcoded values that need to be altered.

For example:
frontend/src/components/frame/presentations/ServerStatusFrame.jsx:86
if (status === 'disconnected') {
  return (
...
  Connection Status
  You are currently not connected to AgensGraph
...

This code displays a message to the user when there is a connection error.
Personally, I think this needs a conditional expression for the type of
database the user is connecting to, but if all references to Agensgraph
need to be removed it could instead display: You are currently not
connected for all database connection types.

4. Many of the results come from the file
frontend/src/documents/tutorial/northwind.jsx. This file is a tutorial that
shows how to use AGE Viewer with AgensGraph. Should this file be removed?

On Wed, Feb 2, 2022 at 3:39 AM Juan Pan  wrote:

> I also have no idea about this vote.
>
>
> I tracked the whole thread and found others raised some issues, but some
> have had no feedback so far. Could anyone sync me this vote is still in the
> process and double check the issue I mentioned?
>
>
> It is the first time for the community to release AGE-view. It is
> efficient to solve all the potential issues internally and definitely will
> cost our lots of efforts and patients.
>
>
> My check list,
>
>
> [x] Download links are valid.
> [x] Checksums and PGP signatures are valid.
> [ ] LICENSE, NOTICE and DISCLAIMER files are correct. (Need double check)
> [x] All files have license headers if necessary.
>
>
> Most of the files are fine, but it still has some bits around AgensGraph
> or bitnine.
>
>
> Run
> ```
> grep bitnine . -R -n
> grep AgensGraph  . -R -n
> ```
> It will show you, like
> ```
> ./frontend/src/components/frame/presentations/ServerStatusFrame.jsx:92:
>   You are currently not connected to AgensGraph
> ./frontend/src/components/frame/presentations/ServerDisconnectFrame.jsx:32:
> disconnectToAgensGraph,
> ```
>
>
> Please keep in mind Apache AGE totally has nothing to do with AgensGraph
> or bitnine business currently and in the future. (Maybe AgensGraph is in
> consideration to rename?)
>
>
>
>
> --
> Juan Pan(Trista), Twitter: @tristaZero
>
>
> On 02/1/2022 02:10，John Gemignani wrote：
> 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 a

Re: [DISCUSS and VOTE] AGEViewer dockerhub presence

[Josh Innis]

The community should have a discussion about the need for a docker image of
AGE Viewer before we vote on it.

A docker image of AGE Viewer will ease the adoption of AGE for graph
related problems. It makes it so that a user of AGE Viewer does not have to
have intimate knowledge of: Postgres, AGE, NodeJs and React before they can
get all the components to work together. I think having a docker image of
AGE-Viewer is a great idea.

In reference to the links: Docker is not a replacement for Apache releases,
and should not be considered as such.

What support model do you think is going to be needed for this? Giving
people a method of visualizing their data in the most convenient way
possible seems to be a good idea, but what do you think are the drawbacks
of this decision?

On Mon, Jan 31, 2022 at 10:32 AM Felix Cheung 
wrote:

> I’d suggest the community to have a discussion of the need. What support
> model that will be etc.
>
> Mentor “vote” is more a proxy of having a clear understanding in the
> community.
>
>
> 
> From: Joe Fagan 
> Sent: Monday, January 24, 2022 10:14:42 PM
> To: dev@age.apache.org 
> Subject: Re: [DISCUSS and VOTE] AGEViewer dockerhub presence
>
> Hi all, please vote to utilise dockerhub as a distribution method for
> Viewer as it is for AGE
>
> @Felix
>
> The direction from Infra team on the incubator AGE dockerhub request was...
> "Neither of these threads expressly confirm the project's desire to adopt
> DockerHub distribution, they are just discussions about issues related to
> it. Please have your project mentors evaluate and approve the requested
> distribution method."
>
> Can I ask you to either vote, or evaluate and approve the
> dockerhub distribution method for Viewer too, whichever is most
> appropriate, or give further specific advice.
>
> Thanks
> Joe
>
> On Tue, 25 Jan 2022 at 05:59, Felix Cheung 
> wrote:
>
> > I guess I’m linking to myself. I see infra asks for mentor, but as a
> > community you should just have a vote. You can explicitly ask a mentor to
> > vote too
> >
> > https://lists.apache.org/thread/oxzo04gxxkqvmtw7rmzkw8t2d8cf3nwo
> > 
> > From: Felix Cheung 
> > Sent: Monday, January 24, 2022 9:51:05 PM
> > To: dev@age.apache.org 
> > Subject: Re: [DISCUSS] AGEViewer dockerhub presence
> >
> > Shouldn’t this be a vote?
> >
> > Please see
> > https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-22356
> > 
> > From: Joe Fagan 
> > Sent: Monday, January 24, 2022 7:34:36 AM
> > To: dev@age.apache.org 
> > Subject: [DISCUSS] AGEViewer dockerhub presence
> >
> > Dear mentors,
> >
> > We would like to have an image for Incubator AGE Viewer at
> hub.docker.com.
> > Is it possible to approve the creation of
> > https://hub.docker.com/r/apache/age-viewer
> > 
> >
> > We will not require push access to this and can instead use automated
> build
> > based on tags in the https://github.com/apache/incubator-age-viewer
> > repository.
> >
> > Once we have your approval we will raise a ticket on JIRA to the Infra
> Team
> > with the relevant details.
> >
> > Thank you
> > Joe
> >
>

Re: [VOTE] Apache AGE 0.7.0 Release

[Josh Innis]

I feel that we should ask this question: are we judging copyright claims at
high level or low levels of programming. Or rather: compiled or
non-compiled code. Take: src/include/parser/cypher_expr.h, this is a file
in incubator-Apache AGE. The name of the function call declared in that
function: transform_cypher_expr is unique. The idea: pass a parsestate
object, a pointer value representing an object that is the expression that
represents the node and an enum representing where the expression came from
as a function that will pass back a transformation phase object that
represents the same thing: is not.

The binary code that will be executed in run-time is a combination of
Postgres and unique executable code that Postgres consciously allows and
designed into their system via static variables. Is the binary code
copyright protected and an issue? Even though it is not bundled with the
code and will not coexist with the code until compile time? Please let us
know.


We have tried to isolate Postgres code from Apace AGE code, but we need
mentorship on whether that means compiled or non-compiled code. There are
no further plans to do so, because we believe there is no reason to do so.
Please help us if we are wrong.


On Mon, Jan 24, 2022 at 9:27 PM Juan Pan  wrote:

> Thanks, then +1 based on my checking
>
>
>
>
> --
> Juan Pan(Trista), Twitter: @tristaZero
>
>
> On 01/24/2022 02:03，Josh Innis wrote：
> 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/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/

Re: [DISCUSS] Ambiguity in the MERGE Specification

[Josh Innis]

Personally I think long term: Alex brings up a good point with the GUC
configuration. Let the database owner decide the behavior.

On Mon, Jan 24, 2022 at 6:15 PM Josh Innis  wrote:

> A directed graph and undirected graph both excel at modeling different
> problems and are used by an overlapping (though neither is a subset of the
> other) set of algorithms. AGE, Neo4J and cypher are all directed models
> that have some undirected features, which are  inherently designed to be
> ambiguous (such as MATCH with no direction given). The AGE edge datatype is
> not designed to handle true undirected edges, and can only emulate them
> using two directed edges. Which mathematically speaking and from an
> algorithm design point of view have some subtle differences.
>
> On Mon, Jan 24, 2022 at 6:07 PM Jasper Blues 
> wrote:
>
>> Sounds reasonable 👍
>>
>> Officially the docs say undefined, so please don’t rely upon it.
>> But the defacto standard is consistent.
>>
>> The model is a directed graph, but when direction does not matter, CYPHER
>> allows to ignore it.
>>
>> Are there some cases where adding support for true undirected edges adds
>> value over the above approach?
>>
>> > On Jan 25, 2022, at 10:01 AM, Josh Innis  wrote:
>> >
>> > I have spent some time on the Neo4J console. I was running this set of
>> > commands:
>> >
>> > 1. MERGE ({side: 'left'})-[:edge]-({side:'right'})
>> > 2. MATCH (l{side: 'left'})-[:edge]->(r{side:'right'}) RETURN l, r
>> > 3. MATCH (l{side: 'left'})<-[:edge]-(r{side:'right'}) RETURN l, r
>> > 4. MATCH (n) DETACH DELETE n
>> >
>> > No matter how many times I deleted the nodes and ran the merge command:
>> > Line 2 returns 1 row and line 3 returns 0 rows. Even though the
>> > documentation says it is ambiguous, for the version freely
>> > available for what is the defacto standard: this ambiguous query will
>> > always create relationships going left to right.
>> >
>> > 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 <
>> john.gemign...@bitnine.net
>> >>>
>> >> 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 <
>> jas...@liberation-data.com
>> >>>
>> >>> 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”. Howeve

Re: [DISCUSS] Ambiguity in the MERGE Specification

[Josh Innis]

A directed graph and undirected graph both excel at modeling different
problems and are used by an overlapping (though neither is a subset of the
other) set of algorithms. AGE, Neo4J and cypher are all directed models
that have some undirected features, which are  inherently designed to be
ambiguous (such as MATCH with no direction given). The AGE edge datatype is
not designed to handle true undirected edges, and can only emulate them
using two directed edges. Which mathematically speaking and from an
algorithm design point of view have some subtle differences.

On Mon, Jan 24, 2022 at 6:07 PM Jasper Blues 
wrote:

> Sounds reasonable 👍
>
> Officially the docs say undefined, so please don’t rely upon it.
> But the defacto standard is consistent.
>
> The model is a directed graph, but when direction does not matter, CYPHER
> allows to ignore it.
>
> Are there some cases where adding support for true undirected edges adds
> value over the above approach?
>
> > On Jan 25, 2022, at 10:01 AM, Josh Innis  wrote:
> >
> > I have spent some time on the Neo4J console. I was running this set of
> > commands:
> >
> > 1. MERGE ({side: 'left'})-[:edge]-({side:'right'})
> > 2. MATCH (l{side: 'left'})-[:edge]->(r{side:'right'}) RETURN l, r
> > 3. MATCH (l{side: 'left'})<-[:edge]-(r{side:'right'}) RETURN l, r
> > 4. MATCH (n) DETACH DELETE n
> >
> > No matter how many times I deleted the nodes and ran the merge command:
> > Line 2 returns 1 row and line 3 returns 0 rows. Even though the
> > documentation says it is ambiguous, for the version freely
> > available for what is the defacto standard: this ambiguous query will
> > always create relationships going left to right.
> >
> > 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 <
> john.gemign...@bitnine.net
> >>>
> >> 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 <
> jas...@liberation-data.com
> >>>
> >>> 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
> >>>>

Re: [DISCUSS] Ambiguity in the MERGE Specification

[Josh Innis]

I have spent some time on the Neo4J console. I was running this set of
commands:

1. MERGE ({side: 'left'})-[:edge]-({side:'right'})
2. MATCH (l{side: 'left'})-[:edge]->(r{side:'right'}) RETURN l, r
3. MATCH (l{side: 'left'})<-[:edge]-(r{side:'right'}) RETURN l, r
4. MATCH (n) DETACH DELETE n

No matter how many times I deleted the nodes and ran the merge command:
Line 2 returns 1 row and line 3 returns 0 rows. Even though the
documentation says it is ambiguous, for the version freely
available for what is the defacto standard: this ambiguous query will
always create relationships going left to right.

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: [DISCUSS] Ambiguity in the MERGE Specification

[Josh Innis]

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.
> >
> >
>

[DISCUSS] Ambiguity in the MERGE Specification

[Josh Innis]

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] Apache AGE 0.7.0 Release

[Josh Innis]

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/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
> >
> > *
>

Re: [VOTE] Apache AGE 0.7.0 Release

[Josh Innis]

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

[Josh Innis]

+1

On Tue, Jan 18, 2022 at 5:41 PM Alex Kwak  wrote:

> +1
>
> On 2022/01/18 23:37:59 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: [DISCUSS] Apache AGE 0.7.0 Release

[Josh Innis]

+1

All links are valid
verified the signature
verified the hash

On Tue, Jan 18, 2022 at 9:56 AM John Gemignani 
wrote:

> +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: [DISCUSS] Committer Requirements

[Josh Innis]

For example Kokou Afidegnon https://github.com/afidegnum has not made a
code commit yet, but has been very helpful in error finding and building
out processes.


On Thu, Jan 6, 2022 at 12:40 PM Josh Innis  wrote:

> I think the user needs to show base competency in a specific area that is
> beneficial to the project: error testing, technical writing, programming,
> feature building, etc.
>
> On Thu, Jan 6, 2022 at 12:38 PM John Gemignani 
> wrote:
>
>> 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] Committer Requirements

[Josh Innis]

I think the user needs to show base competency in a specific area that is
beneficial to the project: error testing, technical writing, programming,
feature building, etc.

On Thu, Jan 6, 2022 at 12:38 PM John Gemignani 
wrote:

> 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: [VOTE] Release Apache AGE Viewer (incubating) 1.0.0-rc0

[Josh Innis]

The northwind.jsx is an example on how to use AGE Viewer with AgensGraph.
Currently, AGE Viewer is compatible with both AgensGraph and Apache AGE, so
the file does not involve AGE, but it is helpful in how to use AGE Viewer
in general.

SIL dictates the License must be included
https://tldrlegal.com/license/open-font-license-(ofl)-explained#fulltext.
We must include the SIL license in the header.

The Cytoscape lib must be noted as such in the LICENSE.

References to Bitnine need to be removed, so the logo needs to change, the
same is true for the lines in the About sidebar.


On Mon, Jan 3, 2022 at 4:50 PM Nicholas Sorrell  wrote:

> I have a few questions:
>
>
>   *   Should this file be included in the repo? It seems to be specific to
> Agensgraph.
> https://github.com/apache/incubator-age-viewer/blob/main/frontend/src/documents/tutorial/northwind.jsx
>   *   The SVGs referenced in this file (
> https://github.com/apache/incubator-age-viewer/blame/main/frontend/src/static/icons/font/fontello.svg)
> seem to possibly be under the SIL license? I'm not entirely sure how
> fontello packages/licenses.
>   *   This Cytoscape lib seems to be bundled and under a different
> license:
> https://github.com/apache/incubator-age-viewer/blob/main/frontend/src/lib/cytoscape-cxtmenu-bitnine/LICENSE
> - should it be noted as such?
>   *   Are there any possible issues from using the Bitnine logos for AGE
> Viewer in the frontend/public folder? Here is an example:
> https://github.com/apache/incubator-age-viewer/blob/main/frontend/public/safari-pinned-tab.svg
>   *   Should the following references to "AGViewer" be changed to "AGE
> Viewer" or "Apache AGE Viewer"?
>  *
> https://github.com/apache/incubator-age-viewer/blob/839ce463543e8472fcbfd30784c4d46a441be1d6/frontend/public/site.webmanifest#L2
>  *
> https://github.com/apache/incubator-age-viewer/blob/839ce463543e8472fcbfd30784c4d46a441be1d6/frontend/public/site.webmanifest#L3
>  *
> https://github.com/apache/incubator-age-viewer/blob/839ce463543e8472fcbfd30784c4d46a441be1d6/frontend/public/index.html#L29
>  *
> https://github.com/apache/incubator-age-viewer/blob/839ce463543e8472fcbfd30784c4d46a441be1d6/frontend/public/index.html#L38
>  *
> https://github.com/apache/incubator-age-viewer/blob/main/frontend/src/components/sidebar/presentations/SidebarAbout.jsx
> lines 27, 44, 49
>   *   SidebarAbout.jsx -
> https://github.com/apache/incubator-age-viewer/blob/main/frontend/src/components/sidebar/presentations/SidebarAbout.jsx
>  *   Should line 31 say "Made by Bitnine"?
>  *   Should line 71 reference the Apache repo instead of the Bitnine
> repo?
>
> --
> Nick Sorrell
> 513.288.1084
> https://cint.io
>
>
> 
> From: Josh Innis 
> Sent: Monday, January 3, 2022 4:08 PM
> To: dev@age.apache.org 
> Subject: Re: [VOTE] Release Apache AGE Viewer (incubating) 1.0.0-rc0
>
> Hi Felix,
>
> I believe that dependencies that are not bundled in the release are not
> required. Which would be all the dependencies listed in the two
> package.json files.
>
> https://infra.apache.org/licensing-howto.html#bundled-vs-non-bundled
>
> For agensGraphRepository.js, the project AgensGraph is distributed under
> the Apache 2.0 license
> https://github.com/bitnine-oss/agensgraph/blob/master/LICENSE. No bundled
> bits are included in the release. A scan of the United Statement Patent and
> Trademark database yields no relevant results.
>
> We should remove the reference to bitnine/agviewer and either remove the
> section or construct a docker image under the apache name.
>
>
>
>
> On Thu, Dec 30, 2021 at 7:29 PM Felix Cheung 
> wrote:
>
> > lots of dependencies - are these licenses reviewed and handled in the
> > LICENSE file?
> >
> >
> https://github.com/apache/incubator-age-viewer/blob/main/backend/package.json
> >
> >
> https://github.com/apache/incubator-age-viewer/blob/main/frontend/package.jso\
> >
> > this requires a component - again could be a LICENSE check, if it is
> > required for execution (at runtime) we should check license of that too.
> > Also what is the trademark on the “AgensGraph” name?
> >
> >
> https://github.com/apache/incubator-age-viewer/blob/main/backend/src/models/agensgraph/agensGraphRepository.js
> > '@bitnine-oss/ag-driver');
> >
> > The
> > https://github.com/apache/incubator-age-viewer/blob/main/README.md
> > references  to bitnine/agviewer
> > 
> > From: Eya Badal 
> > Sent: Thursday, December 30, 2021 6:44:11 AM
> > To: dev@age.apache.org 
> > Subject: Re: [VOTE] Rele

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

[Josh Innis]

Correction: AgensGraph is trademarked.

https://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=1&f=G&l=50&co1=AND&d=PTXT&s1=AgensGraph&OS=AgensGraph&RS=AgensGraph

On 2022/01/03 21:08:14 Josh Innis wrote:
> Hi Felix,
> 
> I believe that dependencies that are not bundled in the release are not
> required. Which would be all the dependencies listed in the two
> package.json files.
> 
> https://infra.apache.org/licensing-howto.html#bundled-vs-non-bundled
> 
> For agensGraphRepository.js, the project AgensGraph is distributed under
> the Apache 2.0 license
> https://github.com/bitnine-oss/agensgraph/blob/master/LICENSE. No bundled
> bits are included in the release. A scan of the United Statement Patent and
> Trademark database yields no relevant results.
> 
> We should remove the reference to bitnine/agviewer and either remove the
> section or construct a docker image under the apache name.
> 
> 
> 
> 
> On Thu, Dec 30, 2021 at 7:29 PM Felix Cheung 
> wrote:
> 
> > lots of dependencies - are these licenses reviewed and handled in the
> > LICENSE file?
> >
> > https://github.com/apache/incubator-age-viewer/blob/main/backend/package.json
> >
> > https://github.com/apache/incubator-age-viewer/blob/main/frontend/package.jso\
> >
> > this requires a component - again could be a LICENSE check, if it is
> > required for execution (at runtime) we should check license of that too.
> > Also what is the trademark on the “AgensGraph” name?
> >
> > https://github.com/apache/incubator-age-viewer/blob/main/backend/src/models/agensgraph/agensGraphRepository.js
> > '@bitnine-oss/ag-driver');
> >
> > The
> > https://github.com/apache/incubator-age-viewer/blob/main/README.md
> > references  to bitnine/agviewer
> > 
> > From: Eya Badal 
> > Sent: Thursday, December 30, 2021 6:44:11 AM
> > To: dev@age.apache.org 
> > Subject: Re: [VOTE] Release Apache AGE Viewer (incubating) 1.0.0-rc0
> >
> > Looks good to me
> > +1
> >
> > I checked the following:
> >
> > - Signature and hash - check.
> > - DISCLAIMER - check.
> > - LICENSE and NOTICE - check.
> > - No unexpected binary files - check.
> > - incubating in name - check.
> >
> > Best,
> > Eya
> >
> > On 2021/12/23 00:58:26 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: [VOTE] Release Apache AGE Viewer (incubating) 1.0.0-rc0

[Josh Innis]

Hi Felix,

I believe that dependencies that are not bundled in the release are not
required. Which would be all the dependencies listed in the two
package.json files.

https://infra.apache.org/licensing-howto.html#bundled-vs-non-bundled

For agensGraphRepository.js, the project AgensGraph is distributed under
the Apache 2.0 license
https://github.com/bitnine-oss/agensgraph/blob/master/LICENSE. No bundled
bits are included in the release. A scan of the United Statement Patent and
Trademark database yields no relevant results.

We should remove the reference to bitnine/agviewer and either remove the
section or construct a docker image under the apache name.




On Thu, Dec 30, 2021 at 7:29 PM Felix Cheung 
wrote:

> lots of dependencies - are these licenses reviewed and handled in the
> LICENSE file?
>
> https://github.com/apache/incubator-age-viewer/blob/main/backend/package.json
>
> https://github.com/apache/incubator-age-viewer/blob/main/frontend/package.jso\
>
> this requires a component - again could be a LICENSE check, if it is
> required for execution (at runtime) we should check license of that too.
> Also what is the trademark on the “AgensGraph” name?
>
> https://github.com/apache/incubator-age-viewer/blob/main/backend/src/models/agensgraph/agensGraphRepository.js
> '@bitnine-oss/ag-driver');
>
> The
> https://github.com/apache/incubator-age-viewer/blob/main/README.md
> references  to bitnine/agviewer
> 
> From: Eya Badal 
> Sent: Thursday, December 30, 2021 6:44:11 AM
> To: dev@age.apache.org 
> Subject: Re: [VOTE] Release Apache AGE Viewer (incubating) 1.0.0-rc0
>
> Looks good to me
> +1
>
> I checked the following:
>
> - Signature and hash - check.
> - DISCLAIMER - check.
> - LICENSE and NOTICE - check.
> - No unexpected binary files - check.
> - incubating in name - check.
>
> Best,
> Eya
>
> On 2021/12/23 00:58:26 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

[Josh Innis]

+1

On Thu, Dec 23, 2021 at 10:27 AM Joe Fagan  wrote:

> +1
>
> On Thu, 23 Dec 2021 at 16:58, John Gemignani 
> wrote:
>
> > +1
> >
> > john
> >
> > On Mon, Dec 20, 2021 at 2:33 AM Muhammad Shoaib <
> muhemmed.sho...@gmail.com
> > >
> > 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
> > >
> >
> --
>
> 
>
> 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: Apache AGE (Incubating) - Community Graduation Vote

[Josh Innis]

lol, forgot to vote.

+1

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
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On 2021/11/09 04:31:33 Eya Badal wrote:
> > > Hi AGE community and Mentors,
> > > 
> > > Since entering incubation 18 months ago in April 2020 and with five
> > > versions of AGE released, and 0.6.0 imminent, it's fair to say the AGE
>

Re: Apache AGE (Incubating) - Community Graduation Vote

[Josh Innis]

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
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On 2021/11/09 04:31:33 Eya Badal wrote:
> > Hi AGE community and Mentors,
> > 
> > Since entering incubation 18 months ago in April 2020 and with five
> > versions of AGE released, and 0.6.0 imminent, it's fair to say the AGE
> > community has demonstrated its ability to build software releases the
> > Apache Way.
> > 
> > We have prepared an assessment of the Apache AGE podling’s maturity, meant
> > to help inform the decision (of the mentors, community, Incubator PMC, and
> > ASF Board of Directors) to graduate it as a top-level Apache project. We
> > used the ASF project maturity model
> > <https://community.apache.org/apache-way/apache-project-maturity-model.html>
> > to evaluate the Apache AGE project and assess itself as having no major
> > areas for concern. The assessment can be found at the Apache AGE website
&

[RESULT][VOTE] Apache AGE (incubating) 0.6.0 Release

[Josh Innis]

Hi all,

Thanks for your review and vote for Apache AGE version 0.6.0.
I'm happy to announce the vote has passed:

Many thanks to our mentors for helping us with the release and IPMC voters
that reviewed and approved this version. We will go to the next round of voting.

3 +1 Bindings
Kevin Ratnasekera
Felix Cheung
Juan Pan

5 +1 Non Bindings
Nick Sorrell
Alex Kwak
John Gemignani
Joe Fagan
Mohammad Shaobib

Thank You,
Josh Innis

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

[Josh Innis]

Hello Community,

We are closing the vote. Results will be sent shortly.

On 2021/11/23 11:33:12 Nicholas Sorrell wrote:
> +1
> 
> > On Nov 23, 2021, at 06:31, Kevin Ratnasekera  
> > wrote:
> > 
> > +1
> > 
> >> On Tue, Nov 23, 2021 at 4:57 PM Juan Pan  wrote:
> >> 
> >> +1, looks like DISCLAIMER-WIP was fixed this time.
> >> 
> >> 
> >> 
> >> [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.
> >> 
> >> 
> >> 
> >> This is new vote, please give a notice to the last one [1] in
> >> incubator.a.o.
> >> 
> >> 
> >> [1] https://lists.apache.org/thread/tf34o3ovg2p7clyznbj5sh4wsbxfrqjb
> >> 
> >> 
> >> --
> >> Juan Pan(Trista), Twitter: @tristaZero
> >> 
> >> 
> >> On 11/22/2021 05:33，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
> >> 
> 

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

[Josh Innis]

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

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

[Josh Innis]

We are closing this vote to make the necessary changes and will open a new
VOTE thread with the updated NOTICE shortly.
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 Sun, Nov 21, 2021 at 12:04 PM Eya Badal  wrote:

> Sorry but -1
>
> As Justin mentioned and advised:
> ""
> The NOICE file has this:
> *Apache AGE (incubating)
> *Copyright 2019-2020 Bitnine Co., Ltd.
> *Copyright 2020-2021 The Apache Software Foundation
>
> It would be more accurate to say something like:
>
> Portions of Apache AGE were originally developed by Bitnine Co., Ltd. and
> were
> donated to the Apache Software Foundation. Copyright 2019-2020 Bitnine
> Co., Ltd.
>
> or something like this:
>
> Portions of Apache Age were originally based on 
> copyright 2019-2020 Bitnine Co., Ltd.
> ""
>
> So we should follow the above recommendation and revote again after fixing
> the NOTICE file.
>
> Best regards,
> Eya
>
>
> On 2021/11/19 22:26:27 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 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 9262a877d0108e114e29a9f3b42e4af5ef5ed011
> >
> > *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
> >
>

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

[Josh Innis]

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 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 9262a877d0108e114e29a9f3b42e4af5ef5ed011

*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

[Josh Innis]

Hi,

We are cancelling this vote. We intended to release this version with the
non-WIP Disclaimer. Since the file is in Github, we need to modify this
release's commit hash and tag.
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, Nov 18, 2021 at 10:08 PM Juan Pan  wrote:

> +1 binding, I checked
>
>
>
> [x] Download links are valid.
>
> [x] Checksums and PGP signatures are valid.
>
> [x] LICENSE, NOTICE and DISCLAIMER-WIP files are correct.
>
> [x] All files have license headers if necessary.
>
>
>
>
> BTW, issues in DISCLAIMER-WIP need to be resolved before graduation.
>
>
> --
> Juan Pan(Trista), Twitter: @tristaZero
>
>
> On 11/19/2021 01: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
>

[VOTE] Apache AGE (incubating) Release 0.6.0

[Josh Innis]

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: [DISCUSS] Apache AGE (incubating) Release 0.6.0

[Josh Innis]

Dear everyone,

I am closing this discussion, and I will open a vote thread for Apache AGE
v0.6.0 Release shortly.
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 Mon, Nov 15, 2021 at 9:04 PM Muhammad Shoaib  wrote:

> +1
>
> Looks fine to me now.
>
> On Tue, Nov 16, 2021 at 12:06 AM Josh Innis  wrote:
>
> > +1. The Postgres license has been removed from the Notice file, and
> > Bitnine's copyright info has been added for the source code that was made
> > before the project was donated to ASF. The following list of files have
> had
> > their licenses updated from the ASF liscense to the Postgres license:
> >   src/include/parser/cypher_expr.h
> >   src/backend/utils/ag_func.c
> >src/include/parser/ag_scanner.h
> > src/backend/parser/cypher_item.c
> > src/backend/executor/cypher_utils.c
> > src/backend/utils/adt/agtype.c
> > src/backend/parser/cypher_expr.c
> > src/backend/parser/cypher_clause.c
> > src/backend/parser/cypher_parse_agg.c
> > src/include/parser/cypher_parse_agg.h
> > src/include/utils/agtype.h
> > src/backend/utils/adt/agtype_util.c
> > src/include/utils/agtype_parser.h
> > src/include/utils/ag_float8_supp.h
> > src/backend/utils/adt/ag_float8_supp.c
> > src/include/utils/ag_func.h
> > src/backend/parser/cypher_keywords.c
> > src/backend/parser/cypher_parse_node.c
> > src/backend/utils/adt/agtype_parser.c
> >
> > On 2021/11/15 22:55:48 John Gemignani wrote:
> > > +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: [DISCUSS] Apache AGE (incubating) Release 0.6.0

[Josh Innis]

+1. The Postgres license has been removed from the Notice file, and Bitnine's 
copyright info has been added for the source code that was made before the 
project was donated to ASF. The following list of files have had their licenses 
updated from the ASF liscense to the Postgres license:
  src/include/parser/cypher_expr.h
  src/backend/utils/ag_func.c
   src/include/parser/ag_scanner.h
src/backend/parser/cypher_item.c
src/backend/executor/cypher_utils.c
src/backend/utils/adt/agtype.c
src/backend/parser/cypher_expr.c
src/backend/parser/cypher_clause.c
src/backend/parser/cypher_parse_agg.c
src/include/parser/cypher_parse_agg.h
src/include/utils/agtype.h
src/backend/utils/adt/agtype_util.c
src/include/utils/agtype_parser.h
src/include/utils/ag_float8_supp.h
src/backend/utils/adt/ag_float8_supp.c
src/include/utils/ag_func.h
src/backend/parser/cypher_keywords.c
src/backend/parser/cypher_parse_node.c
src/backend/utils/adt/agtype_parser.c

On 2021/11/15 22:55:48 John Gemignani wrote:
> +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
> > >
> > >
> >
> >
> 

[DISCUSS] Apache AGE (incubating) Release 0.6.0

[Josh Innis]

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

[RESULT] [VOTE] Apache AGE (Incubating) 0.6.0 Release

[Josh Innis]

Dear AGE Community,



I'm closing this vote and happy to announce the results of the vote for

Apache AGE 0.6.0 Incubating



This vote passes with 7 +1 votes (2 bindings and 5 non bindings) and no 0

or -1 votes.



+1 (Binding)

--

* Juan Pan

* Kevin Ratnasekera





There were no 0 or -1 votes. Thank you to all who helped make this happen.





Vote thread can be found here [1].



I'll continue with the next round of the voting process and update the

community as progress is

made.





[1]

https://lists.apache.org/thread.html/r7152a52ca973bc72282ff9a1591e49ec1662e69914aa2c9784c256a6%40%3Cdev.age.apache.org%3E



Best regards,

Josh Innis

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

[Josh Innis]

Hi All,

I am closing this vote. We will announce the results shortly.
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 Mon, Oct 18, 2021 at 2:32 PM Josh Innis  wrote:

>
> What would be the definition of minor modification? AGE in general tries
> to conform to the ideas in Postgres as much as possible. Which means we are
> constantly calling Postgres functions to do work and at runtime queries
> will switch between Postgres source code and AGE source code often. When we
> cannot use a Postgres function but want to emulate similar behavior, we use
> that function as a template. For example, the Agtype data type that we use
> is heavily influenced by the JsonB data type in Postgres and the way we
> transform expressions is very close to Postgres. A function might have the
> same logical flow to it, but we need to pass in a different data structure,
> or we might have some special cases that must be handled differently, but
> otherwise is very similar to something in postgres.
>
> On Sun, Oct 17, 2021 at 2:17 PM Felix Cheung 
> wrote:
>
>> In such case, the inclusion of the license is required.
>>
>> Also, ideally, the 3rd party source code should be retained as separate
>> source files so we could keep the license header on each file. If they are
>> code snippet, then it is a bit of a grey area and we should attribute the
>> source in license (a practice I've seen in other projects)
>>
>> See
>> https://www.apache.org/legal/src-headers.html#3party
>> https://www.apache.org/legal/resolved.html#category-a
>> "
>> 4. Minor modifications/additions to third-party source files should
>> typically be licensed under the same terms as the rest of the third-party
>> source for convenience.
>>
>> 5. The project's PMC should deal with major modifications/additions to
>> third-party source files on a case-by-case basis."
>>
>>
>>
>>
>> On 2021/10/13 20:44:15 Josh Innis wrote:
>> > We resigned the files using an @apache.org account. There is source
>> code
>> > from Postgres in AGE. There are no files but there are some snippets.
>> > 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 Sun, Oct 10, 2021 at 5:28 PM Felix Cheung  wrote:
>> >
>> > > There bundle also applies to the source release. However, if you are
>> > > certain none of the source code file or snippet is from the Postgres
>> code
>> > > base, then, correct, you don’t need to include Postgres license info.
>> > >
>> > > You might want to amend the license and notice, and re-sign with a key
>> with
>> > > @apache.org address from my comments earlier.
>> > >
>> > > I’m not sure if it will be flagged at IPMC, but it is best since you
>> have
>> > > changed the disclaimer in this release.
>> > >
>> > >
>> > > On 2021/10/05 16:54:29 Josh Innis wrote:
>> > > > Hi Felix,
>> > > >
>> > > > We do not have any binary code from Postgres. The key phrase I saw
>> was "
>> > > > LICENSE and NOTICE need only be modified to accommodate them *only
>> if
>> > > their
>> > > > bits are bundled*." The Apache AGE repository does not have any
>> binary
>> > > > source files in it. After reading the links you sent, it appears we
>> do
>> > > not
>> > > > have to keep the Postgres license info in NOTICE and LICENSE.
>> > > >
>> > > >
>> > > > On Sun, Oct 3, 2021 at 12:11 PM Felix Cheung 
>> wrote:
>> > > >
>> > > > > Checking this release, not a blocker but a question:
>> > > > >
>> > > > >
>> > > > > - incubating in name
>> > > > >
>> > > > > - signature and hash fine
>> > > > >
>> > > > > KEYS file - you should try to sign files with @apache.org issuer
>> email
>> > >

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

[Josh Innis]

What would be the definition of minor modification? AGE in general tries to
conform to the ideas in Postgres as much as possible. Which means we are
constantly calling Postgres functions to do work and at runtime queries
will switch between Postgres source code and AGE source code often. When we
cannot use a Postgres function but want to emulate similar behavior, we use
that function as a template. For example, the Agtype data type that we use
is heavily influenced by the JsonB data type in Postgres and the way we
transform expressions is very close to Postgres. A function might have the
same logical flow to it, but we need to pass in a different data structure,
or we might have some special cases that must be handled differently, but
otherwise is very similar to something in postgres.

On Sun, Oct 17, 2021 at 2:17 PM Felix Cheung  wrote:

> In such case, the inclusion of the license is required.
>
> Also, ideally, the 3rd party source code should be retained as separate
> source files so we could keep the license header on each file. If they are
> code snippet, then it is a bit of a grey area and we should attribute the
> source in license (a practice I've seen in other projects)
>
> See
> https://www.apache.org/legal/src-headers.html#3party
> https://www.apache.org/legal/resolved.html#category-a
> "
> 4. Minor modifications/additions to third-party source files should
> typically be licensed under the same terms as the rest of the third-party
> source for convenience.
>
> 5. The project's PMC should deal with major modifications/additions to
> third-party source files on a case-by-case basis."
>
>
>
>
> On 2021/10/13 20:44:15 Josh Innis wrote:
> > We resigned the files using an @apache.org account. There is source code
> > from Postgres in AGE. There are no files but there are some snippets.
> > 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 Sun, Oct 10, 2021 at 5:28 PM Felix Cheung  wrote:
> >
> > > There bundle also applies to the source release. However, if you are
> > > certain none of the source code file or snippet is from the Postgres
> code
> > > base, then, correct, you don’t need to include Postgres license info.
> > >
> > > You might want to amend the license and notice, and re-sign with a key
> with
> > > @apache.org address from my comments earlier.
> > >
> > > I’m not sure if it will be flagged at IPMC, but it is best since you
> have
> > > changed the disclaimer in this release.
> > >
> > >
> > > On 2021/10/05 16:54:29 Josh Innis wrote:
> > > > Hi Felix,
> > > >
> > > > We do not have any binary code from Postgres. The key phrase I saw
> was "
> > > > LICENSE and NOTICE need only be modified to accommodate them *only if
> > > their
> > > > bits are bundled*." The Apache AGE repository does not have any
> binary
> > > > source files in it. After reading the links you sent, it appears we
> do
> > > not
> > > > have to keep the Postgres license info in NOTICE and LICENSE.
> > > >
> > > >
> > > > On Sun, Oct 3, 2021 at 12:11 PM Felix Cheung 
> wrote:
> > > >
> > > > > Checking this release, not a blocker but a question:
> > > > >
> > > > >
> > > > > - incubating in name
> > > > >
> > > > > - signature and hash fine
> > > > >
> > > > > KEYS file - you should try to sign files with @apache.org issuer
> email
> > > > >
> > > > > - DISCLAIMER is fine
> > > > >
> > > > > - LICENSE and NOTICE
> > > > >
> > > > > The PostgreSQL license - is it because of code file taken from the
> > > project
> > > > > (and then is there license header for these files?)
> > > > >
> > > > > If it is not coming from code file, then is it because of a binary
> > > > > dependency? If so, it should be in a separate LICENSE-binary file
> like
> > > > > https://github.com/apache/iotdb/blob/master/LICENSE-binary
> > > > >
> > > > > And potentially the license should be separately stored like
> > > > > https://github.com/apache/iotdb/tree/

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

[Josh Innis]

We resigned the files using an @apache.org account. There is source code
from Postgres in AGE. There are no files but there are some snippets.
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 Sun, Oct 10, 2021 at 5:28 PM Felix Cheung  wrote:

> There bundle also applies to the source release. However, if you are
> certain none of the source code file or snippet is from the Postgres code
> base, then, correct, you don’t need to include Postgres license info.
>
> You might want to amend the license and notice, and re-sign with a key with
> @apache.org address from my comments earlier.
>
> I’m not sure if it will be flagged at IPMC, but it is best since you have
> changed the disclaimer in this release.
>
>
> On 2021/10/05 16:54:29 Josh Innis wrote:
> > Hi Felix,
> >
> > We do not have any binary code from Postgres. The key phrase I saw was "
> > LICENSE and NOTICE need only be modified to accommodate them *only if
> their
> > bits are bundled*." The Apache AGE repository does not have any binary
> > source files in it. After reading the links you sent, it appears we do
> not
> > have to keep the Postgres license info in NOTICE and LICENSE.
> >
> >
> > On Sun, Oct 3, 2021 at 12:11 PM Felix Cheung  wrote:
> >
> > > Checking this release, not a blocker but a question:
> > >
> > >
> > > - incubating in name
> > >
> > > - signature and hash fine
> > >
> > > KEYS file - you should try to sign files with @apache.org issuer email
> > >
> > > - DISCLAIMER is fine
> > >
> > > - LICENSE and NOTICE
> > >
> > > The PostgreSQL license - is it because of code file taken from the
> project
> > > (and then is there license header for these files?)
> > >
> > > If it is not coming from code file, then is it because of a binary
> > > dependency? If so, it should be in a separate LICENSE-binary file like
> > > https://github.com/apache/iotdb/blob/master/LICENSE-binary
> > >
> > > And potentially the license should be separately stored like
> > > https://github.com/apache/iotdb/tree/master/licenses
> > >
> > > more info:
> > > https://infra.apache.org/licensing-howto.html#bundled-vs-non-bundled
> > >
> > > - No unexpected binary files
> > > - All source files have ASF headers
> > >
> > >
> > >
> > > On 2021/09/24 11:34:24 Kevin Ratnasekera wrote:
> > > > +1
> > > >
> > > > I checked the following.
> > > >
> > > > - Incubating in name.
> > > >
> > > > - PGP Signatures.
> > > >
> > > > - SHA512 Checksums.
> > > >
> > > > - DISCLAIMER exists.
> > > >
> > > > - LICENSE and NOTICE are fine.
> > > >
> > > > - ASF headers on source files.
> > > >
> > > >
> > > >
> > > > Regards
> > > >
> > > > Kevin
> > > >
> > > > On Tue, Sep 21, 2021 at 8:52 PM Eya Badal  wrote:
> > > >
> > > > > +1, I checked the follwoing:
> > > > >
> > > > >
> > > > > 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,
> > > > > Eya Badal Abdisho
> > > > >
> > > > > On 2021/09/15 16:11:47, 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 

Re: New committer: Andrew Ko

[Josh Innis]

+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: Re: [VOTE] Release Apache AGE (incubating) version 0.6.0

[Josh Innis]

Hi Felix,

We do not have any binary code from Postgres. The key phrase I saw was "
LICENSE and NOTICE need only be modified to accommodate them *only if their
bits are bundled*." The Apache AGE repository does not have any binary
source files in it. After reading the links you sent, it appears we do not
have to keep the Postgres license info in NOTICE and LICENSE.


On Sun, Oct 3, 2021 at 12:11 PM Felix Cheung  wrote:

> Checking this release, not a blocker but a question:
>
>
> - incubating in name
>
> - signature and hash fine
>
> KEYS file - you should try to sign files with @apache.org issuer email
>
> - DISCLAIMER is fine
>
> - LICENSE and NOTICE
>
> The PostgreSQL license - is it because of code file taken from the project
> (and then is there license header for these files?)
>
> If it is not coming from code file, then is it because of a binary
> dependency? If so, it should be in a separate LICENSE-binary file like
> https://github.com/apache/iotdb/blob/master/LICENSE-binary
>
> And potentially the license should be separately stored like
> https://github.com/apache/iotdb/tree/master/licenses
>
> more info:
> https://infra.apache.org/licensing-howto.html#bundled-vs-non-bundled
>
> - No unexpected binary files
> - All source files have ASF headers
>
>
>
> On 2021/09/24 11:34:24 Kevin Ratnasekera wrote:
> > +1
> >
> > I checked the following.
> >
> > - Incubating in name.
> >
> > - PGP Signatures.
> >
> > - SHA512 Checksums.
> >
> > - DISCLAIMER exists.
> >
> > - LICENSE and NOTICE are fine.
> >
> > - ASF headers on source files.
> >
> >
> >
> > Regards
> >
> > Kevin
> >
> > On Tue, Sep 21, 2021 at 8:52 PM Eya Badal  wrote:
> >
> > > +1, I checked the follwoing:
> > >
> > >
> > > 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,
> > > Eya Badal Abdisho
> > >
> > > On 2021/09/15 16:11:47, 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
> > > >
> > >
> >
>

[VOTE] Release Apache AGE (incubating) version 0.6.0

[Josh Innis]

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

[DISCUSS] Apache AGE 0.6.0 Release

[Josh Innis]

Dear everyone, 

I am closing this discussion, and I will open a vote thread for Apache AGE 
v0.6.0 Release shortly.

On 2021/09/13 14:14:06 Eya Badal wrote:
> +1, looking forward to this release!!! 
> 
> On 2021/09/10 16:52:03, 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: combining multiple cypher queries into one query

[Josh Innis]

I should have reread my response twice, lol. I rewrote the last sentence to
make sense.

Yes, without a RETURN clause the function we are trying to benchmark will
not be called, and naming all the variables in a CREATE clause with a
significant amount of vertices created to measure performance would not be
the most accurate test to how cypher would be used for most people.

Did you run the query I provided once or multiple times? Looking at the
original results, there were cases where the original version ran faster.
We saw an improvement over average time. Either way, don't worry about the
performance of the query I sent. The query I provided that dynamically runs
the query in a function may have some issues affecting the results.

Consult the thread titled "Benchmarking results' for a better way.

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 Mon, Sep 13, 2021 at 1:03 PM Josh Innis  wrote:

> Hi Viet,
>
> Yes, without a RETURN clause the function we are trying to benchmark will
> not be called, and naming all the variables in a CREATE clause with a
> significant amount of vertices created to measure performance would not be
> the most accurate test to how cypher would be used for most people.
>
> Did you run the query I provided once or multiple times? Looking at the
> original results, there were cases where the original version ran faster.
> We saw an improvement over average time. Either way, don't worry about the
> performance of the query I sent. The query I provided may also have an
> issue where dynamically running the query in a function may have some
> issues affecting the results.
>
> Consult the thread titled "Benchmarking results' for a better way.
>
> On Mon, Sep 13, 2021 at 7:31 AM VUONG QUOC Viet 
> wrote:
>
>> Hi guys,
>> I've followed John's suggestion on Friday, which was to combined multiple
>> cypher queries into 1 long query, like this:
>> SELECT *
>> FROM cypher('test_graph', $$
>> CREATE(:Person{id: 123, name: 'Andres', title: 'Developer', city:
>> 'Seattle'})
>> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
>> 'Munich'})
>> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
>> 'Munich'})
>> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
>> 'Munich'})
>> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
>> 'Munich'})
>> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
>> 'Munich'})
>> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
>> 'Munich'})
>> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
>> 'Munich'})
>> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
>> 'Munich'})
>> CREATE(:Person{id: 123, name: 'Viet', title: 'Dev', city: 'Hanoi'})
>> $$) as (a agtype);
>> The problem is, if there's no RETURN clause, the function
>> _agtype_build_vertex will not be invoked. I checked this with the
>> debugger.
>> However, if we want to have a RETURN clause, we have to name each vertex,
>> like a, b, c, d, whatever..., which seems impossible when we want to run
>> 100, 1000 and 1 queries or even more.
>> Also, I followed Josh's suggestions on how to use the loop. I made a new
>> script for it and ran 100, 1000, 1, 10 queries and extracted the
>> execution time automatically. The result, however, shocked me because the
>> time for optimized code is actually larger than that of the original code.
>>
>> Original Optimized
>> 100 queries 38.10308 40.473135
>> 1000 queries 268.219235 284.259025
>> 1 queries 2354.88069 2436.623295
>> 10 queries 21843.64663 22750.658105
>> I'm gonna need to find a ultimate solution for this and make sure about
>> the
>> repeatability as well.
>> Best regards,
>>
>> Viet.
>>
>

Re: combining multiple cypher queries into one query

[Josh Innis]

Hi Viet,

Yes, without a RETURN clause the function we are trying to benchmark will
not be called, and naming all the variables in a CREATE clause with a
significant amount of vertices created to measure performance would not be
the most accurate test to how cypher would be used for most people.

Did you run the query I provided once or multiple times? Looking at the
original results, there were cases where the original version ran faster.
We saw an improvement over average time. Either way, don't worry about the
performance of the query I sent. The query I provided may also have an
issue where dynamically running the query in a function may have some
issues affecting the results.

Consult the thread titled "Benchmarking results' for a better way.

On Mon, Sep 13, 2021 at 7:31 AM VUONG QUOC Viet  wrote:

> Hi guys,
> I've followed John's suggestion on Friday, which was to combined multiple
> cypher queries into 1 long query, like this:
> SELECT *
> FROM cypher('test_graph', $$
> CREATE(:Person{id: 123, name: 'Andres', title: 'Developer', city:
> 'Seattle'})
> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
> 'Munich'})
> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
> 'Munich'})
> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
> 'Munich'})
> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
> 'Munich'})
> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
> 'Munich'})
> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
> 'Munich'})
> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
> 'Munich'})
> CREATE(:Person{id: 123, name: 'Brian', title: 'Researcher', city:
> 'Munich'})
> CREATE(:Person{id: 123, name: 'Viet', title: 'Dev', city: 'Hanoi'})
> $$) as (a agtype);
> The problem is, if there's no RETURN clause, the function
> _agtype_build_vertex will not be invoked. I checked this with the debugger.
> However, if we want to have a RETURN clause, we have to name each vertex,
> like a, b, c, d, whatever..., which seems impossible when we want to run
> 100, 1000 and 1 queries or even more.
> Also, I followed Josh's suggestions on how to use the loop. I made a new
> script for it and ran 100, 1000, 1, 10 queries and extracted the
> execution time automatically. The result, however, shocked me because the
> time for optimized code is actually larger than that of the original code.
>
> Original Optimized
> 100 queries 38.10308 40.473135
> 1000 queries 268.219235 284.259025
> 1 queries 2354.88069 2436.623295
> 10 queries 21843.64663 22750.658105
> I'm gonna need to find a ultimate solution for this and make sure about the
> repeatability as well.
> Best regards,
>
> Viet.
>

Re: Benchmarking result

[Josh Innis]

Runtime performance of any query in SQL is dictated by the execution tree
structure. AGE translates cypher commands into SQL as much as possible.
Some exceptions are: variable length edges, the merge clause, and the
CREATE/REMOVE/SET/DELETE clauses. (Sidenote: we do try to use Postgres
functionality in the exceptions, however by definition, they must deviate
from functionality allowed in the SQL standard in a notable way). The patch
that we are benchmarking here does not affect the execution tree. Instead
what it does is affect the time it takes to create the vertex agtype after
Postgres has scanned the table the vertex is stored in and given the rest
of the execution tree a tuple.

A vertex is a map with very specific keys (id, label, and properties). This
patch optimizes constructing that data type, because Agtype maps are
ordered. The current version of agtype_build_vertex is anticipating to
receive it's keys in an unordered way, which is unnecessary. This patch
will bypass that check.

There is no way to make this patch's performance statistically significant.
We have reduced the execution tree to almost as little as possible. There
is a way to simplify it more, which I have added below. However, it is not
necessary. What we are seeing is exactly what I personally expected: a
small but not significant improvement. We can continue to work on this, but
we are improving our performance benchmarking tools at this point.

SQL:

SET search_path TO ag_catalog;
LOAD 'age';
SELECT create_graph('test_graph');

SELECT *
FROM f_test( 100, $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$);

EXPLAIN ANALYZE SELECT _agtype_build_vertex(P.id, 'Person'::cstring,
P.properties) from test_graph."Person" as P;

I think this isolates the test to exactly what is needed and nothing more.
Given the other performance benchmarks, I anticipate about a 2% average
improvement to runtime.

There are some changes that Viet needs to make to the patch in the Slack
channel (https://app.slack.com/client/TAET0CD3L/C0102328XEJ). I will add
instructions there shortly and a tutorial on the 'amend' option for the
commit command in git. If anyone reading this does not have access to the
Slack channel, create an email in the dev mailing list and we will include
you.

Note: Also f_test needs to get renamed if we wanna add it to the repository
in any way. Given the functionality, a verbose name would be:
run_dynamic_sql_n_times

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 Mon, Sep 13, 2021 at 7:34 AM Joe Fagan  wrote:

> [image: image.png]
>
> Viet,
>
> For the results of last week's test unfortunately the optimised code is
> not statistically significantly different from the non-optimised.
>
> When you send the new test results I can run it again (should take only a
> few minutes now I have it set up) and re-run the test. I can also explain
> the results if you're interested.
>
> Briefly the test 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 a

Re: Benchmarking result

[Josh Innis]

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 
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.
>>
>>

[DISCUSS] Apache AGE 0.6.0 Release

[Josh Innis]

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: Creating Nodes in Bulk,

[Josh Innis]

Hi all,

Upon thinking about this more I realized there is an underlying issue that
needs to be discussed that directly affects the approach needed on this
feature. To do so: I need to talk about an early design mistake that was
made on this project.

Back in 2019 when this project was still called Agensgraph-Extension and
there was no consideration to donate to Apache, the project ignored a basic
rule of programming: don't use deprecated features. In particular: the use
of OIDs by non pg_catalog tables. OID stands for Object Id. In short,
Postgres uses OIDs to assign a unique value to a row that no other system
table row has. In earlier versions of Postgres they gave the right of the
user to mark rows in other tables as "system" tables and give them an oid
(An oid that no POSTGRES system table had either).

This feature was deprecated in version Postgres 8.5. We started development
of AGE on Postgres 11. To try and summarize a decision that was made in the
first 3 months of a project. Some of the people involved (but not all) are
no longer working on the project thought: "The reason why they did this is
because they don't want systems built on top of Postgres to consider
themselves system tables. We are not technically a 'system built on top of
Postgres.' We are an extension of Postgres. Therefore our metadata tables
are technically system tables. Therefore our unique identifiers should be
unique in all of Postgres. Therefore we should use OIDs... Oh, it's
deprecated. We should still use them. Why not, what's the worst that could
happen?"

The worst that could happen is Postgres removes the functionality of adding
Oids to users tables (which we are) in Postgres 12. They removed the
functionality of 'WITH OIDS' from their SQL grammar implementation and they
removed Oid from being returned on certain Postgres internal C functions
that they used to give us. This is why AGE is incompatible with Postgres
12+ (NOTE: possibly other things too but this is definitely THE issue
causing us problems).

Our goal since that point has been to implement as much of the openCypher
spec as possible. Which is why we have not dealt with this problem yet. The
good news is: none of the features implemented since the point we realized
this mistake have made the job of changing AGE to fix this take more time.

The reason why I am bringing this up now in this email is: Option #1 is
clearly the superior option. We should funnel as much functionality that we
can through the ANSI SQL and the openCypher specification that we can. The
internal C functions of Postgres are not part of those standards.
Therefore, this bulk import tool needs to create dynamic sql queries on a
row per row basis, rather than use the internal Postgres functions to
bypass some of those standards. Even though it is slower.

With all of that said: we need to deal with this issue soon. In other
orders: soon == 2021.

TLDR: Option #1 is better.
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 Wed, Sep 1, 2021 at 10:16 AM Josh Innis  wrote:

> Muhammed,
>
> Directly calling the functions that insert data into the vertex and edge
> tables might not be the best way. They are tightly integrated with the
> Postgres stages of execution (Parse, Transform, Optimize, and Execution).
> There are two options I would recommend:
>
>
>1. Dynamically create either a Cypher CREATE query or create an SQL
>insert query.
>2. Take a look at how we insert data into our ag_catalog tables
>ag_graph and ag_label. Both are located in src/backend/catalog. This would
>decouple a great amount of our insertion logic from the Postgres (Though
>obviously not completely). If you take a look at agtype_build_map in
>src/backend/utils/adt/agtype.c that would give you an idea on how to create
>the property map from the spreadsheet.
>
> Both solutions have potential drawbacks. Dynamically creating a cypher/sql
> query will be slower however, you are using the standard interface provided
> by both us and Postgres (via the SQL and openCypher language
> specifications). Which would not be the case in the 2nd option, however
> that option could decouple some logic that might be useful for later
> features.
>
> 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 Wed, Sep 1, 2021 at 9:42 AM Muhammad Shoaib  wrote:
>
>>

Upgrading AGE

[Josh Innis]

Hi All,

Incubating Apache Age is starting to get to the point where people
(internally and in the community) want to update their existing version of
AGE without having to drop and recreate the extension. In order to use the
newer features.

https://github.com/apache/incubator-age/issues/110

Using Docker can handle some of this concern, but not everyone uses Docker.

The versioning system that Postgres uses for extensions is to partly track
what has been added/modified/deleted in the age--*.sql between versions. To
do this we need to have some .sql scripts that can be used by people when
changing from one version of age to another.

https://www.postgresql.org/docs/11/extend-extensions.html#id-1.8.3.19.15
https://www.postgresql.org/docs/11/sql-alterextension.html

We have not built these scripts, but as the team and the community is
growing right now: it would be good to start building these upgrade scripts.

For some examples, go to the contrib/ folder in the Postgres code. Many of
the extensions contain these scripts.

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: Creating Nodes in Bulk,

[Josh Innis]

Muhammed,

Directly calling the functions that insert data into the vertex and edge
tables might not be the best way. They are tightly integrated with the
Postgres stages of execution (Parse, Transform, Optimize, and Execution).
There are two options I would recommend:


   1. Dynamically create either a Cypher CREATE query or create an SQL
   insert query.
   2. Take a look at how we insert data into our ag_catalog tables ag_graph
   and ag_label. Both are located in src/backend/catalog. This would decouple
   a great amount of our insertion logic from the Postgres (Though obviously
   not completely). If you take a look at agtype_build_map in
   src/backend/utils/adt/agtype.c that would give you an idea on how to create
   the property map from the spreadsheet.

Both solutions have potential drawbacks. Dynamically creating a cypher/sql
query will be slower however, you are using the standard interface provided
by both us and Postgres (via the SQL and openCypher language
specifications). Which would not be the case in the 2nd option, however
that option could decouple some logic that might be useful for later
features.

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 Wed, Sep 1, 2021 at 9:42 AM Muhammad Shoaib  wrote:

> Hi Folks,
>
> I am trying to write a function to load nodes from CSV into AGE. I have
> data into C data structure but don't know how to proceed further. The
> particular questions are
>
> Which AGE data structure I need to use
> which function I need to call in order to insert data into PG Tables.
>
> Looking forward to hearing from you.
>
> Kind regards
> Shoaib
>

Re: [VOTE] Accepting Code Contribution for Visualization tool

[Josh Innis]

+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 Sat, Jul 31, 2021 at 11:40 AM Andrew Ko  wrote:

> +1
> This will help getting more people become interested in the AGE project
> since visualization is one of key functional requirements for graph
> databases.
>
> 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: [VOTE] Release Apache AGE (incubating) version 0.5.0

[Josh Innis]

Hi all, Thank You Myeongseok (Alex Kwak) for the pull request that updates
the copyright information. We will review the pull request and all issues
raised by mentors and community and address them in the next release.

On Sun, Aug 1, 2021 at 9:29 PM Myeongseok Kwak  wrote:

> Hi, Trista.
>
> I checked the projects that you mentioned using gradle such as calcite and
> bigtop. and, confirmed that the projects included gradle-wrapper.jar in the
> git, but are not included in the source code release.
> so, I created Pull requests to fix the Copyright issue and Jar file issue
> mentioned above.
> ( https://github.com/apache/incubator-age/pull/99 )
>
> There will be no such issue in the next release. Thank you for pointing
> out.
> I'd like to leave my opinion to other community users about when to
> release it.
>
>
> Best regards,
> Myeongseok
>
> On 2021/08/02 02:18:15, "Juan Pan"  wrote:
> > H Myeongseoki,
> >
> >
> > The point here is that this is source-code release, right? Do we have to
> include this jar file in a source code release? I found Apache calcite is
> using gradle, which could be an example for us. [1]
> > Besides, it is an issue that some files do not include headers.
> > But as I said before, we can move this one forward and fix them in next
> release, as a new release round will generally take us half a month.
> >
> >
> > Best,
> > Trista
> >
> >
> > [1] https://github.com/apache/calcite
> >
> >
> >
> >
> --
> > Juan Pan(Trista), Apache member, Apache ShardingSphere PMC, Apache brpc
> (Incubator) & Apache AGE (Incubator) mentor
> > Twitter, @trista86934690
> >
> >
> >
> > On 08/1/2021 21:12，Myeongseok Kwak wrote：
> > Hi
> >
> > gradle-wrapper.jar is just a dependency of the project management tool,
> Gradle (like maven).
> >
> > the source code is part of the Gradle project.
> > https://docs.gradle.org/current/userguide/gradle_wrapper.html
> >
> > this will only help you run in an environment where `gradle` is not
> installed.
> > therefore, this is not an essential dependency.
> >
> > However, if it's important, it can be removed.
> >
> > Best regards
> >
> > On 2021/08/01 06:27:38, "Juan Pan"  wrote:
> > Hi,
> >
> >
> > I am Juan Pan, the new mentor of AGE community if it is expected?
> >
> >
> > Currently, Justin and I cast +1 binding for this release on Incubator
> ml, if we had another IPMC binding vote on our dev ml. In principle, it is
> bound to release.
> >
> >
> > It is barely OK with me to move this release forward if we are urgent.
> On the premise, we fix these issues in the next release. But perfectly,
> It’s expected to resolve these issues in this release, especially, the
> source code release contains gradle-wrapper.jar.
> >
> >
> > That’s my view on this release, I’d like to listen to other’s voice in
> the community.
> >
> >
> > Best,
> > Trista
> >
> --
> > Juan Pan(Trista), Apache member, Apache ShardingSphere PMC, Apache brpc
> (Incubator)
> > Twitter, @trista86934690
> >
> >
> >
> > On 07/31/2021 22:45，Eya Badal wrote：
> > Hi, Vongosling and all @mentors,
> >
> > Yes, for sure. Apologies, I was under impression that the mentioned
> issues need to be fixed for the next release and that we are good for this
> release. Thank you very much for pointing that out, we will for sure take
> care of the issues and make some clarifications soon.
> >
> > Would you like us to fix the issues for this release 0.5.0 or just take
> care of it for the next release?
> >
> > As always thank you all for the support and help.
> >
> > Best regards,
> > Eya
> >
> > On 2021/07/31 00:39:38, vongosling  wrote:
> > Hi Eya,
> >
> > I hope that the community will pay attention to the issues that we raised
> > after +1. No clarification is a very bad sign :-(
> >
> > Eya Badal  于2021年7月31日周六 上午12:11写道：
> >
> > Dear AGE Community,
> >
> > I'm closing this vote and happy to announce the results of the vote for
> > Apache AGE 0.5.0 Incubating
> >
> > This vote passes with 9 +1 votes (3 bindings and 6 non bindings) and no 0
> > or -1 votes.
> >
> > +1 (Binding)
> > --
> > * Felix Cheung
> > * vongosling
> > * Kevin Ratnasekera
> >
> >
> > There were no 0 or -1 votes. Thank you to all who helped make this
> happen.
> >
> >
> > Vote thread can be found here [1].
> >
> > I'll continue with the next round of the voting process and update the
> > community as progress is
> > made.
> >
> >
> > [1]
> >
> https://lists.apache.org/thread.html/r0f291fd923bd0217da1935811b4276699aac28715c1936d713e99002%40%3Cdev.age.apache.org%3E
> >
> > Best regards,
> > Eya Badal
> >
> >
> > 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 ca

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

[Josh Innis]

+1 Looks Good
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 Mon, Jul 26, 2021 at 8:52 AM John Gemignani 
wrote:

> +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: [DISCUSS] Apache AGE Sub Project - Visualization Tool

[Josh Innis]

I agree that adding a visualization tool would help build our community.
Moreover, this is a visualization tool that is linked with
incubating-Apache AGE already. If it becomes an official part of the Apache
community it wouldn't open up the project more? Plus it would qualify two
people to be considered as contributors.

On Fri, Jun 18, 2021 at 9:17 AM John Gemignani 
wrote:

> 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: [DISCUSS] Apache AGE Coding standard adjustment

[Josh Innis]

Hi,

I think all these suggestions make sense. Please note this is for the AGE
extension itself and is not currently related to the projects in the
'drivers' directory. Which probably warrants its own discussion.

On Wed, Mar 10, 2021 at 10:40 AM John Gemignani 
wrote:

> 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
>

[DISCUSS] AGE Support for an HTTP API

[Josh Innis]

Hi All

The AGE community is requesting support for an API, in particular they are
asking for us to mimic Neo4J's API.

Github Issue
https://github.com/apache/incubator-age/issues/26

Neo4J API documentations
https://neo4j.com/docs/http-api/3.5/

It does not appear that Postgres officially supports an API. Meaning we
would have to build an API for Postgres, before having an API that supports
AGE. There are some open source github projects that we may be able to use,
but we would have to confirm licensing wouldn't be an issue, if we wanted
to use those. Also, some of the community is asking for driver support, so
this could potentially divide development focus going forward. What does
the group think? Is building an API for AGE a worthy endeavor? And is it a
better option than focusing on driver support for different languages?

Thanks.

[DISCUSS] AGE Container Support

[Josh Innis]

Hi All,

The AGE community is asking us to support more containers than just Docker,
see https://github.com/apache/incubator-age/issues/24. Additionally, upon
review of our Docker images they are in need of being updated.

The Docker images still refer to AgensGraph-Extension. This is due to these
images being set up before our official acceptance to the Apache incubator
and the official name change to Apache AGE (A Graph Extension).
Furthermore, these images refer to the master branch of AGE, so these are
pointing to development work instead of any official release. Personally, I
believe that should be altered, but please let us know what you think.

Moving on to the github issue: Some of our community is unable to use
Docker and is requesting us to support LXC/Snap and/or Kata. For a brief
summary of all these technologies, please refer to the links below.

LXC:
https://linuxcontainers.org/lxc/introduction/

Snap:
https://snapcraft.io/about

A forum discussing Snap:
https://askubuntu.com/questions/808524/whats-the-main-difference-between-docker-and-snap

Kata Official Site:
https://katacontainers.io/

A Good Discussion on Kata:
https://platform9.com/blog/kata-containers-docker-and-kubernetes-how-they-all-fit-together/

Personally, some of the questions I have on the subject before going
forward on providing support for this is: AGE is an extension of Postgres,
so should our containers include Postgres in them to avoid dependencies.
Furthermore, would that affect users' ability to use other extensions, such
as TimeScaleDB, in these environments?

Thanks.

Re: Incubator-AGE code repository in Github was replaced

[Josh Innis]

Hi All,

We have resolved the issue. A committer was attempting to push code to the
wrong repository and used the force option when running git push. We
managed to restore the repository, with one commit lost. The commit updated
the copyright date in the licenses and we will create a new commit. Also
one pull request was auto closed when we implemented the fix. We will reach
out to that individual shortly for a resolution. We will construct a more
detailed root cause report for this shortly.

On Tue, Feb 9, 2021 at 10:07 PM Josh Innis  wrote:

> Hi All,
>
> Please see the initial email for the background. I believe a local branch
> of the AGE website was merged into the AGE master source code. I reached
> out to the necessary parties to help with confirmation. Assistance into
> looking into this would be appreciated.
> 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 Tue, Feb 9, 2021 at 8:21 PM Josh Innis  wrote:
>
> > Hi All,
> >
> > The source code for AGE was replaced with the AGE website code, with all
> > the history too. I am looking into a fix. We have the 0.3.0 Source code
> and
> > all patches since then, so we can recover. If anyone knows how to fix
> this
> > and recover commit history it would be greatly appreciated.
> >
>

Re: Incubator-AGE code repository in Github was replaced

[Josh Innis]

Hi All,

Please see the initial email for the background. I believe a local branch
of the AGE website was merged into the AGE master source code. I reached
out to the necessary parties to help with confirmation. Assistance into
looking into this would be appreciated.
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 Tue, Feb 9, 2021 at 8:21 PM Josh Innis  wrote:

> Hi All,
>
> The source code for AGE was replaced with the AGE website code, with all
> the history too. I am looking into a fix. We have the 0.3.0 Source code and
> all patches since then, so we can recover. If anyone knows how to fix this
> and recover commit history it would be greatly appreciated.
>

Incubator-AGE code repository in Github was replaced

[Josh Innis]

Hi All,

The source code for AGE was replaced with the AGE website code, with all
the history too. I am looking into a fix. We have the 0.3.0 Source code and
all patches since then, so we can recover. If anyone knows how to fix this
and recover commit history it would be greatly appreciated.

Re: Request for First AGE Apache Release Review - VOTE

[Josh Innis]

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 the feedback.
> > > > >Where should I post the thread vote? Should I post it in AGE Dev
> list and ask everyone to vote?
> > > >
> > > >
> > > > On 2021/01/15 02:20:01, Felix Cheung 
> wrote:
> > > > > Did you have a vote thread? Anyone and everyone can vote, it
> shouldn’t be just the mentor.
> > > > >
> > > > > A good vote thread might be like:
> > > > >
> http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Release-Spark-3-1-0-RC1-td30524.html
> > > > >
> > > > > 1. md5 - should not include
> > > > >I will remove this file.
> > > > >
> > > > > 2. apache-age-0.3.0-incubating-src.tar.gz unpack into a
> apache-age-0.3.0-incubating-src.zip
> > > > >  and that unpack into __MACOSX/apache-age-0.3.0-incubating-src/
> > > > > This is very strange. please check the tar.gz file.
> > > > >
> > > > >I am not sure why this happened but I will take care of it and make
> sure it is consistent.
> > > > >
> > > > > 3.
> > > > > I'd suggest use DISCLAIMER-WIP
> > > > >
> https://incubator.apache.org/guides/releasemanagement.html#choice_of_disclaimers
> > > > >Any specific reason why not using Standard Disclaimer?
> > > > >
> > > > > 4.
> > > > > openCypher/openCypher9.pdf
> > > > > maybe don't include this in the source? where is the file from? is
> there a possible licensing issue?
> > > > >
> > > > >It won't be any licensing issue since OpenCypher is based on Apache
> License as well which is included in the licensing file.
> > > > > 5,
> > > > > KEYS.txt
> > > > > don't include inside the source distribution - this should not be
> in git repo
> > > > > I w

Re: Podling Age Report Reminder - October 2020

[Josh Innis]

Hi Eya,

I'll do this upcoming report.

On Sun, Sep 20, 2020 at 1:39 PM Eya Badal  wrote:

> >Hello all,
> >Anyone would like to volunteer for the next upcoming report due on (Wed,
> October 07) ?
>
>

Re: Hi

[Josh Innis]

Guten Morgen

On Wed, Sep 2, 2020 at 9:56 AM John Gemignani  wrote:

> Hi
>

Re: Hi

[Josh Innis]

Howdy

On Wed, Sep 2, 2020 at 9:55 AM John Gemignani  wrote:

> Hi
>