Re: [I] How do I add explicit type casts? [age]
CapnSpek commented on issue #1279:
URL: https://github.com/apache/age/issues/1279#issuecomment-1763534739
Use either
```
SELECT * FROM ag_catalog.create_graph('graph_name');
```
Or
```
SET search_path = ag_catalog, "$user", public;
SELECT * FROM create_graph('graph_name');
```
The issue is actually `No function matches the given name and argument
types.` because AGE is not able to find the function like 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] Analyse MATCH clause performance (relationship basics) [age]
CapnSpek commented on issue #982: URL: https://github.com/apache/age/issues/982#issuecomment-1763533689 Upon checking for folder size based on the two versions. For 10 vertices and 5 edges, the difference appears minimal. One was 94.7 mb, while the other was 96.1 -- 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] Support for PIPE operator for apache-age-python client [age]
pawankukreja01 commented on issue #865: URL: https://github.com/apache/age/issues/865#issuecomment-1763489346 The PIPE operator is a feature of the Nebula Graph Query Language (nGQL) and is not part of OpenCypher. It allows multiple queries to be combined using pipe operators in nGQL. The PIPE operator applies to native nGQL only and is not compatible with OpenCypher -- 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] ImportError in age.models [age]
pawankukreja01 commented on issue #890: URL: https://github.com/apache/age/issues/890#issuecomment-1763488374 **Check for circular imports**: Circular imports can cause issues with importing modules in Python. Ensure that there are no circular imports between your modules. **Check for version compatibility issues**: Ensure that you are using a compatible version of Apache AGE with your version of Python. **Check that the module exists**: Verify that the ‘age.models’ module exists in the correct location and contains the ‘Model’ class. You can do this by opening a Python shell and running `import age.models` followed by `dir(age.models)` to see a list of all objects in the module. -- 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] How do I add explicit type cast types? [age]
cmucheru opened a new issue, #1279:
URL: https://github.com/apache/age/issues/1279
I am working with the age through the psql terminal. I am trying to create a
graph but then I am getting an issue.
```
psql (14.9)
Type "help" for help.
postgres=# CREATE EXTENSION age;
CREATE EXTENSION
postgres=# LOAD 'age';
LOAD
postgres=# SELECT create_graph('new_graph');
2023-10-15 20:18:02.928 EAT [15166] ERROR: function create_graph(unknown)
does not exist at character 8
2023-10-15 20:18:02.928 EAT [15166] HINT: No function matches the given
name and argument types. You might need to add explicit type casts.
2023-10-15 20:18:02.928 EAT [15166] STATEMENT: SELECT
create_graph('new_graph');
ERROR: function create_graph(unknown) does not exist
LINE 1: SELECT create_graph('new_graph');
^
HINT: No function matches the given name and argument types. You might need
to add explicit type casts.
postgres=#
```
How do I add these explicit type casts?
--
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] `SET` and `DETACH DELETE` do not work when `VERBOSE` is added to `EXPLAIN ANALYZE` [age]
CapnSpek commented on issue #1278:
URL: https://github.com/apache/age/issues/1278#issuecomment-1763406919
More information:
The query executes successfully if the labels of the supposed query do not
actually exist in the graph:
(The graph still contains only the above mentioned 2 labels and 1 edge)
```
SELECT * FROM cypher('xyz', $$ EXPLAIN ANALYZE VERBOSE MATCH (n:Pers) SET
n.age=25 $$) AS (x agtype);
QUERY PLAN
--
Custom Scan (Cypher Set) (cost=0.00..0.00 rows=0 width=0) (actual
time=0.003..0.004 rows=0 loops=1)
Output: cypher.x
-> Result (cost=0.00..0.00 rows=0 width=0) (actual time=0.002..0.002
rows=0 loops=1)
Output: cypher.x
One-Time Filter: false
Planning Time: 0.210 ms
Execution Time: 0.043 ms
(7 rows)
```
```
SELECT * FROM cypher('xyz', $$ EXPLAIN ANALYZE VERBOSE MATCH (n:Pers) DETACH
DELETE n $$) AS (x agtype);
QUERY PLAN
-
Custom Scan (Cypher Delete) (cost=0.00..0.00 rows=0 width=0) (actual
time=0.008..0.010 rows=0 loops=1)
Output: cypher.x
-> Result (cost=0.00..0.00 rows=0 width=0) (actual time=0.005..0.005
rows=0 loops=1)
Output: cypher.x
One-Time Filter: false
Planning Time: 0.303 ms
Execution Time: 8.880 ms
(7 rows)
```
It is unrelated to the fact whether vertices were actually found or not as
these queries still fail.
```
SELECT * FROM cypher('xyz', $$ EXPLAIN ANALYZE VERBOSE MATCH (n:Person
{name:'x') SET n.name='U' $$) AS (x agtype);
2023-10-15 17:27:51.906 EEST [161353] ERROR: syntax error at or near ")" at
character 81
2023-10-15 17:27:51.906 EEST [161353] STATEMENT: SELECT * FROM
cypher('xyz', $$ EXPLAIN ANALYZE VERBOSE MATCH (n:Person {name:'x') SET
n.name='U' $$) AS (x agtype);
ERROR: syntax error at or near ")"
LINE 1: ... EXPLAIN ANALYZE VERBOSE MATCH (n:Person {name:'x') SET n.na...
```
```
SELECT * FROM cypher('xyz', $$ EXPLAIN ANALYZE VERBOSE MATCH (n:Person
{name:'x') DETACH DELETE n $$) AS (x agtype);
2023-10-15 17:28:15.647 EEST [161353] ERROR: syntax error at or near ")" at
character 81
2023-10-15 17:28:15.647 EEST [161353] STATEMENT: SELECT * FROM
cypher('xyz', $$ EXPLAIN ANALYZE VERBOSE MATCH (n:Person {name:'x') DETACH
DELETE n $$) AS (x agtype);
ERROR: syntax error at or near ")"
LINE 1: ... EXPLAIN ANALYZE VERBOSE MATCH (n:Person {name:'x') DETACH D...
```
--
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] `SET` and `DETACH DELETE` do not work when `VERBOSE` is added to `EXPLAIN ANALYZE` [age]
CapnSpek opened a new issue, #1278:
URL: https://github.com/apache/age/issues/1278
**Describe the bug**
`EXPLAIN ANALYZE VERBOSE` query will not work with `DETACH DELETE` and `SET`
queries.
Error message
```
2023-10-15 17:16:43.423 EEST [161353] ERROR: cannot display a value of type
internal
2023-10-15 17:16:43.423 EEST [161353] STATEMENT: SELECT * FROM
cypher('xyz', $$ EXPLAIN ANALYZE VERBOSE MATCH (n:Person {age:24}) SET n.age=25
$$) AS (x agtype);
ERROR: cannot display a value of type internal
```
**How are you accessing AGE (Command line, driver, etc.)?**
Accessing AGE through command line.
**What data setup do we need to do?**
Apache AGE (master branch) with PGSQL15.
**What is the necessary configuration info needed?**
Create a graph and a pair of vertices.
```
SELECT * FROM cypher('xyz', $$ CREATE (n:Person
{age:24})-[e:Knows]->(m:Person {age:25}) $$) AS (x agtype);
```
**What is the command that caused the error?**
```
SELECT * FROM cypher('xyz', $$ EXPLAIN ANALYZE VERBOSE MATCH (n:Person
{age:24}) SET n.age=25 $$) AS (x agtype);
```
**ERROR**
```
2023-10-15 17:21:10.744 EEST [161353] ERROR: cannot display a value of type
internal
2023-10-15 17:21:10.744 EEST [161353] STATEMENT: SELECT * FROM
cypher('xyz', $$ EXPLAIN ANALYZE VERBOSE MATCH (n:Person {age:24}) SET n.age=25
$$) AS (x agtype);
ERROR: cannot display a value of type internal
```
**Expected behavior**
Expected the query to execute successfully.
**Environment (please complete the following information):**
- Version: [e.g. 0.4.0]
**Additional context**
Add any other context about the problem 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.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [I] Using a label assigned to another graph will crash the database [age]
CapnSpek commented on issue #1257: URL: https://github.com/apache/age/issues/1257#issuecomment-1763398200 I also tried switching the order of commands such as: Creating graph 1 first, then vertex, then graph 2, then vertex. Creating graph 1 first, then graph 2, then vertex 1, then vertex 2. Both having mixed up labels (graph2 first labels in graph1, and graph1 labels in graph2). The database did not crash @dehowef Can you provide more information about the bug? I'm using the master branch age with pg15. -- 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] Using a label assigned to another graph will crash the database [age]
CapnSpek commented on issue #1257:
URL: https://github.com/apache/age/issues/1257#issuecomment-1763396324
So far, I tried setting up the database through the commands mentioned in
the issue using both JDBC and Postgres.
Other than that, I tried
Manually creating a vertex with a label for 1 graph, creating vertex using
the same label for other graph, then `DROP SCHEMA graph2 CASCADE;`
That also does not crash the database but only gives an error.
```
test=# SELECT * FROM ag_catalog.create_graph('graph1');
NOTICE: graph "graph1" has been created
create_graph
--
```
```
test=# SELECT * FROM ag_catalog.create_graph('graph2');
NOTICE: graph "graph2" has been created
create_graph
--
(1 row)
```
```
test=# SELECT * FROM cypher('graph1', $$ CREATE (x:Person {name:'X'}) RETURN
x $$) AS (x agtype);
x
-
{"id": 844424930131969, "label": "Person", "properties": {"name":
"X"}}::vertex
(1 row)
```
```
test=# SELECT * FROM cypher('graph2', $$ CREATE (x:Person {name:'Y'}) RETURN
x $$) AS (x agtype);
x
-
{"id": 844424930131969, "label": "Person", "properties": {"name":
"Y"}}::vertex
(1 row)
```
```
test=# DROP SCHEMA graph2 CASCADE;
NOTICE: drop cascades to 4 other objects
DETAIL: drop cascades to sequence graph2._label_id_seq
drop cascades to table graph2._ag_label_vertex
drop cascades to table graph2._ag_label_edge
drop cascades to table graph2."Person"
2023-10-15 16:51:24.432 EEST [160811] ERROR: table "Person" is for label
"Person"
2023-10-15 16:51:24.432 EEST [160811] STATEMENT: DROP SCHEMA graph2 CASCADE;
ERROR: table "Person" is for label "Person"
```
--
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.4.0 Release for PostgreSQL 12
+1 (binding) Checked high level: - Signature and Hash - Tags and Links - LICENSE and NOTICE - No unexpected binary files - No unexpected files between git repo/apache release and all file checksums match Performed smoke test which includes: - Build Dockerfile (which builds project) - Run Docker image - Runs commands (create graph/node) via psql verifying basic functionality - Create new system user to run test suite - Verify tests pass (24 passed) Automated checks available to review here: https://github.com/sorrell/apache_age_release_verification/actions/runs/6498131618 From: John Gemignani Date: Thursday, October 12, 2023 at 12:05 PM To: dev@age.apache.org Subject: [VOTE] Apache AGE 1.4.0 Release for PostgreSQL 12 Dear Apache Community, Please carefully read all instructions as they may have changed since the last vote thread. This is an official vote for Apache AGE release 1.4.0 for PostgreSQL 12. To learn more about Apache AGE, please see http://age.apache.org/ Functionalities included and issues addressed in this release are: * Release Notes for Apache AGE release v1.4.0 for PostgreSQL 12 NOTE: Some of these reference the master branch PR that was either applied to lower versions via a separate PR or merged into a newly created branch. Added license in Python driver README.md (#956) Added the toStringList() function (#1128) Added toBooleanList() (#1165) Added toFloatList() function (#1016) Added toIntegerList() function (#1025) Added regression tests for MATCH clause using labels only (#1019) Added REGTYPEOID to toString function (#1036) Added Dockerfile.dev & move docker-related files to "docker/" (#943) Fixed complex MERGE causes crash (#897) (#961) Fixed docker build files (#1104) Fixed case sensitivity on label usage of reserved keyword (#1040) Fixed issue 1000: Indexes created on WHERE (#1133) Fixed issue 1002: Invalid reuse of variables in MATCH clause (#1003) Fixed issue 1033: access operator on vle edge lists (#1037) Fixed issue 1043: ERROR: container must be an array or object (#1046) Fixed issue 1124: Segmentation fault when using specific tables (#1125) Fixed issue 395: ERROR: container is not an agtype array (#1039) Fixed issue 870: regarding orderability and added regression tests (#994) Fixed issue 876: column reference "_age_default_alias_0" is ambiguous (#931) Fixed issue 975: Invalid reuse of variables in CREATE clause (#977) Fixed issue 989: Impossible to create array with > 100 items (#1001) Fixed memory leak issues with age_load (#1142) Fixed memory leaks in MERGE (merge_edge & merge_vertex) (#958) Fixed MERGE crashes due to incorrect label type (#957) Fixed MERGE variable reuse (#997) Fixed misspellings in many AGE files (#985) Fixed warning messages in DockerHub builds. (#1075) Modified test_agtypes to view useful testing message (#992) Optimised Antlr4ResultHandler initialization (#1169) Updated CIs to pull correct image based on branch (#1105) Updated files, format, and version information (#1063) Updated README. * !!! PLEASE VERIFY ALL of the below tags, hash, links, signatures, & keys !!! The git tag to be discussed and voted on: https://github.com/apache/age/releases/tag/PG12/v1.4.0-rc0 The git commit hash: commit 8c9554214acdc76db7d1e4e836ccf6f48e2e782d The release files for 1.4.0, can be found at: https://dist.apache.org/repos/dist/dev/age/PG12/1.4.0.rc0/ Signatures used for AGE RCs can be found in this file: https://downloads.apache.org/age/KEYS The fingerprint of key to sign release artifacts: 4293 0603 8E35 AC05 4DBB 4B58 26B6 CD9D CD5B 0045 For information about the contents of this release see: https://github.com/apache/age/releases/tag/PG12/v1.4.0-rc0 * !!! IMPORTANT PLEASE READ !!! Please note that Apache REQUIRES the following information to be in your response to the vote, in order for it to be valid - - If you are a binding vote, a PMC, then you MUST state it in your response. Otherwise, leave it out. Do not mention it if you are not a PMC. - You MUST state what you checked to support your vote. See the samples given below for guidance. - You MUST, at a minimum, check the above tags, hash, links, and signatures for validity. - You CANNOT just say, +1 or 0. You need to state what items you checked. If your vote DOES NOT follow the above guidelines or samples below, it may be thrown out. !!! IMPORTANT PLEASE READ !!! Please vote as follows - +1, Release this package as Apache AGE 1.4.0 for PostgreSQL 12. 0, I won't get in the way of the vote. -1, Do not release this package because !!! Followed by what you checked !!! Sample responses, two for PMCs (binding) and two for regular committers. These are only
