Re: [I] SQL Error [22023]: ERROR: label_id must be 1 .. 65535 [age]
devcode100 commented on issue #1837: URL: https://github.com/apache/age/issues/1837#issuecomment-2099800078 @jrgemignani , appreciate your effort to replicate. The current postgres server setup have is a single node one and I haven't encountered any issues with DB so far. I would suggest to keep the issue open(at least till ~2 releases ) as its critical for us to monitor the AGE extension as we are planning to move to production with the same. -- 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] Happy new years [age-website]
dehowef closed issue #245: Happy new years URL: https://github.com/apache/age-website/issues/245 -- 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] File \src\backend\commands\label_commands.c lines 270-282 repeated needlessly, only one copy of if block should remain [age]
MironAtHome commented on issue #1839: URL: https://github.com/apache/age/issues/1839#issuecomment-2099669093 Branch or fork, please? -- 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: [PR] Update blog page [age-website]
eyab merged PR #319: URL: https://github.com/apache/age-website/pull/319 -- 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] Please work around limitation of 100 or 50 fields for the function parameters such as agtype_build_map and internally invoked CREATE [age]
jrgemignani commented on issue #1840: URL: https://github.com/apache/age/issues/1840#issuecomment-2099527204 @MironAtHome It looks like `transform_cypher_map` function could use an update. -- 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] Please work around limitation of 100 or 50 fields for the function parameters such as agtype_build_map and internally invoked CREATE [age]
jrgemignani commented on issue #1840: URL: https://github.com/apache/age/issues/1840#issuecomment-2099520105 @MironAtHome I can try to look into this tomorrow, time permitting. I recall something, somewhere, about this limit and creating a workaround. But, it's been a while. -- 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] Please work around limitation of 100 or 50 fields for the function parameters such as agtype_build_map and internally invoked CREATE [age]
MironAtHome opened a new issue, #1840:
URL: https://github.com/apache/age/issues/1840
**Is your feature request related to a problem? Please describe.**
When working with data having vertice property count in excess of 100
Postgres functions exhibit build - in limit of 100 arguments.
Examples:
function agtype_build_map treats each parameter as separate, map field name
and map field value, hence, it limits input to 50 fields / call. To scale
number of fields it can handle one has to continuously invoke constructs such
as
agtype_add(
CypherInputParam_Var
, agtype_build_map(
/* 54 */ field_name_54, field_value_54
/* 55 */ field_name_55, field_value_55
similarly when CREATE invoked subsequently in the context of call to cypher
function and CypherInputParam_Var as an input parameter to overcome per call
limit of parameters/properties requires to initially create subset of 50 fields
and subsequently call constructs such as
CREATE (v:
{... properties 1,2,3 ...
})
SET v += { properties 51... 100}
SET v += { properties 101... 150}
This limitation is grandfathered from functions servicing postgresql
function check when using default build, as per [Appendix K. PostgreSQL
Limits](https://www.postgresql.org/docs/current/limits.html#:~:text=100%20can%20be%20increased%20by,recompiling%20PostgreSQL%20query%20parameters%2065%2C535)
document:
However, I am not 100% convinced that custom compilation of Postgres is the
right approach in this case.
In an ideal world it would be nice if Age used under the hood an limit
compatible with limit of Age, which I believe is 65,535 properties per vertice
( please correct me if I am wrong ).
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features
you've considered.
**Additional context**
Add any other context or screenshots about the feature request 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] SQL Error [22023]: ERROR: label_id must be 1 .. 65535 [age]
jrgemignani commented on issue #1837:
URL: https://github.com/apache/age/issues/1837#issuecomment-2099514050
@devcode100 I should note that, for each of my tests, I used fresh installs
of PostgreSQL version 16.1 and Apache AGE **master** and release 1.5.0. I'm not
sure what specific version of 16 you are using, though.
Here I have created over 13M nodes without issue -
```
psql-16.1-5432-pgsql=# select * from cypher('test', $$ match (u) return
count(u) $$) as (result agtype);
result
--
1360
(1 row)
psql-16.1-5432-pgsql=#
```
--
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] SQL Error [22023]: ERROR: label_id must be 1 .. 65535 [age]
jrgemignani commented on issue #1837:
URL: https://github.com/apache/age/issues/1837#issuecomment-2099496759
@devcode100 I have not been able to reproduce this and I created 120,000
nodes as shown below, in both the latest and PG16 release 1.5.0. It could be
that your install got messed up?
```
psql-16.1-5432-pgsql=# DO
$do$
BEGIN
FOR i in 1..10 LOOP
PERFORM * FROM cypher('test', $$ CREATE (:Category {name:
'CategoryTest1'}) CREATE (:Category {name: 'CategoryTest2'}) CREATE (:Category2
{name: 'CategoryTest1'}) CREATE (:Category2 {name: 'CategoryTest2'}) $$) AS (n
agtype);
end LOOP;
end
$do$;
DO
psql-16.1-5432-pgsql=# DO
$do$
BEGIN
FOR i in 1..10 LOOP
PERFORM * FROM cypher('test', $$ CREATE (:Category {name:
'CategoryTest1'}) CREATE (:Category {name: 'CategoryTest2'}) CREATE (:Category2
{name: 'CategoryTest1'}) CREATE (:Category2 {name: 'CategoryTest2'}) $$) AS (n
agtype);
end LOOP;
end
$do$;
DO
psql-16.1-5432-pgsql=# DO
$do$
BEGIN
FOR i in 1..10 LOOP
PERFORM * FROM cypher('test', $$ CREATE (:Category {name:
'CategoryTest1'}) CREATE (:Category {name: 'CategoryTest2'}) CREATE (:Category2
{name: 'CategoryTest1'}) CREATE (:Category2 {name: 'CategoryTest2'}) $$) AS (n
agtype);
end LOOP;
end
$do$;
DO
psql-16.1-5432-pgsql=# select * from cypher('test', $$ match (u) return
count(u) $$) as (result agtype);
result
-
120
(1 row)
psql-16.1-5432-pgsql=#
```
--
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] SQL Error [22023]: ERROR: label_id must be 1 .. 65535 [age]
devcode100 commented on issue #1837: URL: https://github.com/apache/age/issues/1837#issuecomment-2098831499 @jrgemignani , Both through **psql** cli and **DBearver**(SQL GUI Client), getting the issue. -- 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] Publish to docker hub [age-viewer]
jrgemignani commented on issue #118: URL: https://github.com/apache/age-viewer/issues/118#issuecomment-2098765096 @eyab Thoughts? -- 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] SQL Error [22023]: ERROR: label_id must be 1 .. 65535 [age]
jrgemignani commented on issue #1837: URL: https://github.com/apache/age/issues/1837#issuecomment-2098712393 @devcode100 This is happening when using the command line in PostgreSQL? -- 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: Releases on Docker Hub
Hi Justin, Are you saying that we need to remove the Docker hub link in the download page? Or, am I missing something? Thanks! John On Mon, May 6, 2024 at 11:34 PM Justin Mclean wrote: > HI, > > I was looking at [1], and you are pushing non-released versions there, > which are linked to your download page. ASF release policy does not allow > this [2], so it would be great if you could fix this. > > Kind Regards, > Justin > > 1. https://hub.docker.com/r/apache/age/tags > 2. https://www.apache.org/legal/release-policy.html#publication >
