[GitHub] [age] humzakt commented on issue #971: Is there any Good documentation how age load works
humzakt commented on issue #971: URL: https://github.com/apache/age/issues/971#issuecomment-1588547831 I would refer you to the detailed [documentation](https://age.apache.org/age-manual/master/intro/agload.html) for deeper insights on the function -- 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
[GitHub] [age] rafsun42 closed issue #981: Analyse MATCH clause performance (basic node finding)
rafsun42 closed issue #981: Analyse MATCH clause performance (basic node finding) URL: https://github.com/apache/age/issues/981 -- 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
[GitHub] [age] Zeesh-an commented on issue #971: Is there any Good documentation how age load works
Zeesh-an commented on issue #971: URL: https://github.com/apache/age/issues/971#issuecomment-1588200899 You can find the documentation [here](https://age.apache.org/age-manual/master/intro/agload.html). However, the link only explains usage of tool, you can refer the AGE manual for explanation of working of algorithm -- 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
[GitHub] [age] dehowef commented on issue #966: How to export graph data for Giraph analysis?
dehowef commented on issue #966: URL: https://github.com/apache/age/issues/966#issuecomment-1588141636 @bigplaice Hi Steven, any update if you were able to get this to work? -- 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
[GitHub] [age] Zeesh-an commented on issue #978: The count number does not match on UPDATE and DELETE.
Zeesh-an commented on issue #978:
URL: https://github.com/apache/age/issues/978#issuecomment-1588063850
It appears there may be some confusion. Only the rows returned from a Cypher
query are displayed in the table. To accurately observe the changes made to
graph entities, RETURN clause in your queries can be used as mentioned by
@AbdulSamad4068 . Here's an alternative explanation along with modified
examples to demonstrate how you can adjust your UPDATE and DELETE queries to
view the affected rows:
```
SELECT * FROM cypher ('tmp', $$
MATCH (a:Part)
WHERE a.part_num =~ '3+'
SET a.part_num = '333'
RETURN a
$$) AS (a agtype);
```
In this query, the 'part_num' property of nodes labeled as 'Part' is
modified, specifically updating it to '333'. By including the RETURN clause and
specifying 'a', the modified rows will be returned and displayed as part of the
query result.
--
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
Απ: Offset and out of bounds
Yes of course.
When we run the basic select * from cypher
('test', $$ create (u) return u) as (u agtype), fill_agtype_value() is being
called multiple times.
There are times when its called with the base_addr having the value
"idlabelproperties" and the offset
helps breaking down this string to fill correctly the json object that will be
return to the client. But there
are cases that when the fill_agtype_value() is called, for example when the
node we are creating has
no label, that the offset is 32, which is larger than the length of the
base_addr. Running gdb with
fill_agtype_value() as a breaking point would make it easier to understand what
im trying to say.
Από: John Gemignani
Στάλθηκε: Δευτέρα, 12 Ιουνίου 2023 10:03 μμ
Προς: dev@age.apache.org
Θέμα: Re: Offset and out of bounds
Could you give some example cases?
john
On Mon, Jun 12, 2023 at 11:12 AM Panagiotis Foliadis
wrote:
> Hey all,
>
> I'm having a hard time understanding the offset functionality in
> fill_agtype_value().
> There are many times when this function is called that the offset is
> greater than the
> length of the base_addr resulting in fetching a value from out of bounds.
> How do the
> out-of-bounds values get initialized and what are we trying to achieve by
> having the offset
> reach for the out-of-bounds values?
>
Re: Offset and out of bounds
Could you give some example cases? john On Mon, Jun 12, 2023 at 11:12 AM Panagiotis Foliadis wrote: > Hey all, > > I'm having a hard time understanding the offset functionality in > fill_agtype_value(). > There are many times when this function is called that the offset is > greater than the > length of the base_addr resulting in fetching a value from out of bounds. > How do the > out-of-bounds values get initialized and what are we trying to achieve by > having the offset > reach for the out-of-bounds values? >
Offset and out of bounds
Hey all, I'm having a hard time understanding the offset functionality in fill_agtype_value(). There are many times when this function is called that the offset is greater than the length of the base_addr resulting in fetching a value from out of bounds. How do the out-of-bounds values get initialized and what are we trying to achieve by having the offset reach for the out-of-bounds values?
[GitHub] [age] dukeofhazardz commented on issue #971: Is there any Good documentation how age load works
dukeofhazardz commented on issue #971: URL: https://github.com/apache/age/issues/971#issuecomment-1587769980 @Munmud for a detailed documentation on the `age load` function and its usage, I recommend referring to the AGE manual. It provides comprehensive information on how the algorithm works. You can find the relevant documentation at the following link: [AGE Docs - Importing graph from files](https://age.apache.org/age-manual/master/intro/agload.html). It should provide you with the insights you're looking for. -- 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
[GitHub] [age] AbdulSamad4068 commented on issue #978: The count number does not match on UPDATE and DELETE.
AbdulSamad4068 commented on issue #978:
URL: https://github.com/apache/age/issues/978#issuecomment-1587244769
The issue you're encountering is not a bug but a misunderstanding of how to
view the updated or deleted rows in Apache AgeDB. In AgeDB, only the rows
returned from the Cypher query will be displayed in the table. To see the
changes made to the graph entities, you need to use the RETURN clause in your
queries. Here's how you can modify your UPDATE and DELETE queries to view the
affected rows:
UPDATE query:
```
SELECT * FROM cypher ('tmp', $$
MATCH (a:Part) WHERE a.part_num =~ '3+' SET a.part_num = '333' RETURN a
$$) AS (a agtype);
```
DELETE query:
```
SELECT * FROM cypher ('tmp', $$
MATCH (a:Part) WHERE a.part_num =~ '3+' DELETE a RETURN a
$$) AS (a agtype);
```
without the RETURN clause, only the rows returned from the query will be
displayed, which might not include the modified rows.
--
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
[GitHub] [age] TalhaMunir-JD commented on issue #971: Is there any Good documentation how age load works
TalhaMunir-JD commented on issue #971: URL: https://github.com/apache/age/issues/971#issuecomment-1587237960 As shoaib and mrrcxs said you can view this [link](https://age.apache.org/age-manual/master/intro/agload.html) for detailed documentation of load_labels_from_file() and load_edges_from_file(). -- 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
