Re: [I] The Go driver becomes "undefined: parser", and the application cannot be built. [age]

2024-01-17 Thread via GitHub


jrgemignani commented on issue #1455:
URL: https://github.com/apache/age/issues/1455#issuecomment-1897584117

   Both the README and install.sh files aren't very good. If you look at the 
install file, you will basically need to -
   
   1. Make sure that you have installed and selected the latest version of JAVA.
   2. Make sure that you have installed the latest version of ANTLR **and** it 
is in the `CLASSPATH`. 
   3. You need to build the files in the parser directory using generate.sh. 
This is not in the `install.sh` file.
   4. You will need to run that last command in install.sh for Age.g4 and give 
it the correct location parser/Age.g4
   5. You will then need to modify the DSN information to reflect your database 
connect information.
   
   After that you should be good to go.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] The Go driver becomes "undefined: parser", and the application cannot be built. [age]

2024-01-17 Thread via GitHub


jrgemignani commented on issue #1455:
URL: https://github.com/apache/age/issues/1455#issuecomment-1897560429

   @maehara-n You need to build those files by executing generate.sh -
   
   ```
   [jgemignani@cent7nuc7i5bnk age]$ ll ../parser/
   total 100
   -rw-rw-r--. 1 jgemignani jgemignani  2732 Jan 17 16:34 age_base_listener.go
   -rw-rw-r--. 1 jgemignani jgemignani  1064 Jan 17 16:34 age_base_visitor.go
   -rw-rw-r--. 1 jgemignani jgemignani  2193 Sep 20 17:44 Age.g4
   -rw-rw-r--. 1 jgemignani jgemignani  2887 Jan 17 16:34 Age.interp
   -rw-rw-r--. 1 jgemignani jgemignani 10646 Jan 17 16:34 age_lexer.go
   -rw-rw-r--. 1 jgemignani jgemignani  7366 Jan 17 16:34 AgeLexer.interp
   -rw-rw-r--. 1 jgemignani jgemignani   251 Jan 17 16:34 AgeLexer.tokens
   -rw-rw-r--. 1 jgemignani jgemignani  1774 Jan 17 16:34 age_listener.go
   -rw-rw-r--. 1 jgemignani jgemignani 37680 Jan 17 16:34 age_parser.go
   -rw-rw-r--. 1 jgemignani jgemignani   251 Jan 17 16:34 Age.tokens
   -rw-rw-r--. 1 jgemignani jgemignani  1082 Jan 17 16:34 age_visitor.go
   -rw-rw-r--. 1 jgemignani jgemignani44 Nov 28 16:50 generate.go
   -rwxrwxr-x. 1 jgemignani jgemignani   400 Jan 17 16:02 generate.sh
   [jgemignani@cent7nuc7i5bnk age]$
   ```
   


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



[VOTE] Apache AGE 1.5.0 Release for PostgreSQL 16

2024-01-17 Thread John Gemignani
Dear Apache Community,

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

This is an official vote for Apache AGE release 1.5.0 for PostgreSQL 16.

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

Functionalities included and addressed in this release are:

*
Release Notes for Apache AGE release 1.5.0 for PostgreSQL version 16

Apache AGE 1.5.0 - Release Notes

NOTE: This is an initial release of Apache AGE for PostgreSQL version
16. There are no upgrade scripts to this release.

Add additional index support and performance enhancements (#1232)
Add an additional way to find a previous variable ref (#1450)
Add auto apply labeler workflow for PRs (#1161)
Add checks for array functions to recognize and decode VPC (#1064)
Add concat || operator to agtype (#1198)
Add exist(?, ?|, ?&) operators for agtype (#1218)
Add missing dependency in cypher_expr.c (#1256)
Add path extraction(#>, #>>)operators to agtype (#1224)
Add support for chained expressions in CASE (#1431)
Clean up agtype_to_int8, agtype_to_int4, & agtype_to_int2 (#1354)
Clean up #included files in parser directory (#1465)
Converted SQL main file into multiple files. (#1401)
docs: Add to Docker setup (#1204)
Extend access(->, ->>), addition and subtraction operators (#1258)
Extend agtype containment operators (@>, <@) (#1285)
Extend EXPLAIN and add config param to switch transformation of property
filter (#1262)
Fix ambiguous conditions (#1373)
Fix Docker file to reflect PostgreSQL version 15 (#1449)
Fix DockerHub warning messages for latest (#1380)
Fix issue #1045 - error using path var in WHERE (#1295)
Fix Issue #1159 - Server terminates for SET plus-equal (#1160)
Fix issue #1219 - MERGE not seeing previous clause var (#1441)
Fix issue #1302 - crash on NULL input to UNWIND (#1304)
Fix issue #1303: Server crashes on executing SELECT * FROM agtype(null);
(#1317)
Fix Issue #1305 - drop_label NULL cases (#1306)
Fix Issue #1329 - agtype_to_int4 crash (#1339)
Fix issue #1347 - unknow type of agtype container 0 (#1349)
Fix issue #1389 - Server crash on using null operand for access operators
(#1390)
Fix issue #1393 - previous clause variables not seen with EXISTS (#1426)
Fix issue #1398 - SET followed by DELETE does not delete (#1412)
Fix issue #1399 EXISTS doesn't handle non-existent labels (#1400)
Fix Issue #945 - incorrect count(*) return values (#1288)
Fix typo in agtype_raw.h header guard (#1368)
Implement chained expression order of operations (#1402)
Implemented age_tail function (#1283)
Implemented the toBooleanList() function (#1014)
Implement EXISTS subquery for CASE (#1345)
Master to PostgreSQL version 16 (#1451)
Minor fix in agtype_volatile_wrapper function (#1172)
Modify COUNT() to output agtype (#1311)
Optimize performance of detach delete (#1271)
Optimize vertex and edge builder functions (#1252)
py_driver : optimised Antlr4ResultHandler to improve time (#1107)
Refactor Regression Tests for CASE statement (#1268)
Refactor the IN operator to use '= ANY()' syntax (#1236)
Removed unnecessary assignment (#1185)
Remove redundant job from CIs (#1473)
Remove unnecessary #include in src/backend/utils
Updated age.control.
Updated files, format, and version information.
Updated Makefile.
Updated RELEASE.
Update Discord channel in README.md (#1253)
Update README.md file for PostgreSQL version 16 support (#1463)
Update the Python Driver (#1246)

*

!!! PLEASE VERIFY ALL of the below tags, hash, links, signatures, and keys
!!!

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

The git commit hash:
commit 0048900f372d4dfd5c236f78b8a8453bcdbb458e

The release files for 1.5.0, can be found at:
https://dist.apache.org/repos/dist/dev/age/PG16/1.5.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/PG16/v1.5.0-rc0

*

!!! IMPORTANT PLEASE READ !!!

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

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

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

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

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

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

Re: [DISCUSS] Apache AGE 1.5.0 Release for PostgreSQL 16

2024-01-17 Thread John Gemignani
Dear Apache Community,

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

Thank you for your time,

John Gemignani

On Wed, Jan 10, 2024 at 8:56 AM Dehowe Feng  wrote:

> Updating to Postgres 16 would bring AGE into the most up-to-date version of
> Postgres. Looking forward to the release.
>
> I’ve checked:
>
> - Signature and hash
> - License and notice
> - Links and tags
> - No unexpected binary files
>
> Best,
>
> Dehowe
>
>
>
>
>
> On Jan 10, 2024, at 6:41 AM, Muhammad Shoaib 
> wrote:
>
> Hi,
>
> I have checked the following aspects:
>
>
>   - Links
>   - Files
>   - Signature
>   - Commit hash
>   - Git tags
>   - Release contents
>
> All the elements seem to be in order,
>
> Kind Regards
> Shoaib
>
> On Tue, Jan 9, 2024 at 8:06 PM Rafsun Masud  wrote:
>
> Looks good!
>
>
> Checked:
>
>  - Links
>
>  - Files
>
>  - Signature
>
>  - Commit hash
>
>  - Git tags
>
>  - Release contents
>
>
> --
>
> *Rafsun Masud*
>
> rafsu...@bitnine.net
>
>
>
> On Mon, Jan 8, 2024 at 4:33 PM John Gemignani 
>
> wrote:
>
>
> Dear Apache Community,
>
>
> We would like to open a discussion for the Apache AGE release 1.5.0 for
>
> PostgreSQL 16.
>
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
>
> Functionalities included and addressed in this release are:
>
>
> *
>
> Release Notes for Apache AGE release 1.5.0 for PostgreSQL version 16
>
>
> Apache AGE 1.5.0 - Release Notes
>
>
> NOTE: This is an initial release of Apache AGE for PostgreSQL version
>
>16. There are no upgrade scripts to this release.
>
>
> Add additional index support and performance enhancements (#1232)
>
> Add an additional way to find a previous variable ref (#1450)
>
> Add auto apply labeler workflow for PRs (#1161)
>
> Add checks for array functions to recognize and decode VPC (#1064)
>
> Add concat || operator to agtype (#1198)
>
> Add exist(?, ?|, ?&) operators for agtype (#1218)
>
> Add missing dependency in cypher_expr.c (#1256)
>
> Add path extraction(#>, #>>)operators to agtype (#1224)
>
> Add support for chained expressions in CASE (#1431)
>
> Clean up agtype_to_int8, agtype_to_int4, & agtype_to_int2 (#1354)
>
> Clean up #included files in parser directory (#1465)
>
> Converted SQL main file into multiple files. (#1401)
>
> docs: Add to Docker setup (#1204)
>
> Extend access(->, ->>), addition and subtraction operators (#1258)
>
> Extend agtype containment operators (@>, <@) (#1285)
>
> Extend EXPLAIN and add config param to switch transformation of property
>
> filter (#1262)
>
> Fix ambiguous conditions (#1373)
>
> Fix Docker file to reflect PostgreSQL version 15 (#1449)
>
> Fix DockerHub warning messages for latest (#1380)
>
> Fix issue #1045 - error using path var in WHERE (#1295)
>
> Fix Issue #1159 - Server terminates for SET plus-equal (#1160)
>
> Fix issue #1219 - MERGE not seeing previous clause var (#1441)
>
> Fix issue #1302 - crash on NULL input to UNWIND (#1304)
>
> Fix issue #1303: Server crashes on executing SELECT * FROM agtype(null);
>
> (#1317)
>
> Fix Issue #1305 - drop_label NULL cases (#1306)
>
> Fix Issue #1329 - agtype_to_int4 crash (#1339)
>
> Fix issue #1347 - unknow type of agtype container 0 (#1349)
>
> Fix issue #1389 - Server crash on using null operand for access operators
>
> (#1390)
>
> Fix issue #1393 - previous clause variables not seen with EXISTS (#1426)
>
> Fix issue #1398 - SET followed by DELETE does not delete (#1412)
>
> Fix issue #1399 EXISTS doesn't handle non-existent labels (#1400)
>
> Fix Issue #945 - incorrect count(*) return values (#1288)
>
> Fix typo in agtype_raw.h header guard (#1368)
>
> Implement chained expression order of operations (#1402)
>
> Implemented age_tail function (#1283)
>
> Implemented the toBooleanList() function (#1014)
>
> Implement EXISTS subquery for CASE (#1345)
>
> Master to PostgreSQL version 16 (#1451)
>
> Minor fix in agtype_volatile_wrapper function (#1172)
>
> Modify COUNT() to output agtype (#1311)
>
> Optimize performance of detach delete (#1271)
>
> Optimize vertex and edge builder functions (#1252)
>
> py_driver : optimised Antlr4ResultHandler to improve time (#1107)
>
> Refactor Regression Tests for CASE statement (#1268)
>
> Refactor the IN operator to use '= ANY()' syntax (#1236)
>
> Removed unnecessary assignment (#1185)
>
> Remove redundant job from CIs (#1473)
>
> Remove unnecessary #include in src/backend/utils
>
> Updated age.control.
>
> Updated files, format, and version information.
>
> Updated Makefile.
>
> Updated RELEASE.
>
> Update Discord channel in README.md (#1253)
>
> Update README.md file for PostgreSQL version 16 support (#1463)
>
> Update the Python Driver (#1246)
>
>
> *
>
>
> The git tag to be discussed and voted on:
>
> 

Re: [I] Invalid reuse of previous clause variable in succeeding CREATE clause [age]

2024-01-17 Thread via GitHub


rafsun42 commented on issue #1513:
URL: https://github.com/apache/age/issues/1513#issuecomment-1896431742

   This can be a project. The other executors may have similar issues. #1446 is 
a related one. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] No update path to 1.5.0 [age]

2024-01-17 Thread via GitHub


jrgemignani commented on issue #1508:
URL: https://github.com/apache/age/issues/1508#issuecomment-1896336367

   @guruguruguru Not a problem, it happens. 
   
   There is no way, **currently**, to upgrade from one version of AGE in say, 
PostgreSQL version 12 to the same version of AGE in PostgreSQL version 16. 
Meaning that upgrading across PostgreSQL versions is not an option 
**currently**. This is something we plan to look into when we have the time and 
resources. However, at this moment, it isn't available.
   
   As for upgrading AGE within a PostgreSQL version, we try to make it 
possible. However, sometimes changes are made such that you just can't. As AGE 
1.5.0 for PG 16 is brand new, unfortunately, you have to start from scratch. 
Sorry about that.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Invalid reuse of previous clause variable in succeeding CREATE clause [age]

2024-01-17 Thread via GitHub


jrgemignani commented on issue #1513:
URL: https://github.com/apache/age/issues/1513#issuecomment-1896292602

   @Zainab-Saad If you are planning on creating a PR to fix this, please note 
it here :) 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Invalid reuse of previous clause variable in succeeding CREATE clause [age]

2024-01-17 Thread via GitHub


jrgemignani commented on issue #1513:
URL: https://github.com/apache/age/issues/1513#issuecomment-1896291094

   @Zainab-Saad Good catch!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Error when trying to run with "npm run start" [age-viewer]

2024-01-17 Thread via GitHub


tsmanuelanton commented on issue #166:
URL: https://github.com/apache/age-viewer/issues/166#issuecomment-1896181898

   you can fix this executing before `export 
NODE_OPTIONS=--openssl-legacy-provider`


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



[I] Invalid reuse of previous clause variable in succeeding CREATE clause [age]

2024-01-17 Thread via GitHub


Zainab-Saad opened a new issue, #1513:
URL: https://github.com/apache/age/issues/1513

   **Describe the bug**
   The succeeding CREATE clause is letting the reuse of variable of the 
previous CREATE.
   
   **How are you accessing AGE (Command line, driver, etc.)?**
   psql
   
   **What is the command that caused the error?**
   ```pgsql
   SELECT * FROM cypher('graph', $$ CREATE(n) CREATE(n)  RETURN n $$) AS 
(result agtype);
   ```
   creates one vertex
   ```
result 
   
{"id": 281474976710657, "label": "", "properties": {}}::vertex
   (1 row)
   ```
   
   **Environment (please complete the following information):**
   AGE master - PG16
   
   **Expected behavior**
   The second CREATE clause should give a `duplicate variable` error. Neo4j 
errors out as:
   ```
   Variable `n` already declared (line 1, column 18 (offset: 17))
   "CREATE(n) CREATE(n)  RETURN n"
 ^
   ```
   


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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Happy new years [age-website]

2024-01-17 Thread via GitHub


itsdheerajdp commented on issue #245:
URL: https://github.com/apache/age-website/issues/245#issuecomment-1895518044

   Can you please clearly explain me what you want me to do as i am confused 
because PR is already merged so what to do now??


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