Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug/GIE] gs.interactive() in python SDK reports error #3100

Closed
longbinlai opened this issue Aug 11, 2023 · 2 comments
Closed

[Bug/GIE] gs.interactive() in python SDK reports error #3100

longbinlai opened this issue Aug 11, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@longbinlai
Copy link
Collaborator

longbinlai commented Aug 11, 2023

Describe the bug
Following the instruction,
while calling g = gs.interactive(graph), there reports error of 'module' object is not callable.

Screenshots
Screenshot 2023-08-11 at 16 32 45

The above error turns out to be an inconsistency between the latest release and the doc.
The doc has included the changes in pr #2952, which however, has not been encompassed in the latest release of graphscope (0.23.0). Using preview version (pip3 install graphscope --pre) may resolve the ''module not callable'' issue, but new issue prompts:
Screenshot 2023-08-14 at 11 31 18

Screenshot 2023-08-14 at 11 32 31

Furthermore, the result printing is wrong in the doc as well, should be print(q1.all()) instead of print(q1.all().result())

Screenshot 2023-08-11 at 16 34 44

Environment (please complete the following information):

  • GraphScope version: 0.23.0
  • OS: MaxOS
  • Version 13.3.1
@longbinlai longbinlai added the bug Something isn't working label Aug 11, 2023
@longbinlai longbinlai changed the title [Bug/GIE] gs.interactive() in python SKD reports error [Bug/GIE] gs.interactive() in python SDK reports error Aug 14, 2023
@shirly121
Copy link
Collaborator

I successfully go through the process in the Dev Container environment.

>>> q1 = g.execute('g.V().count()')
>>> print(q1.all().result())
[6]
>>> q2 = g.execute('g.V().hasLabel(\'person\')')
>>> print(q2.all().result())
[v[2], v[3], v[0], v[1]]
>>> from neo4j import GraphDatabase, RoutingControl
>>> q3 = g.execute("MATCH (n:person) RETURN count(n)", lang="cypher", routing_=RoutingControl.READ)
>>> print(q3.records[0][0])
4
>>> q3 = g.execute("MATCH (n) RETURN count(n)", lang="cypher", routing_=RoutingControl.READ)
>>> print(q3.records[0][0])
6

longbinlai added a commit that referenced this issue Aug 22, 2023
Committed-by: longbinlai from Dev container

Fix issue #3100
@longbinlai
Copy link
Collaborator Author

Issue caused by inconsistencies between graphscope release version and docs. The doc reflects a change that is not included in the 0.23.0 release. Adding a --pre option to install a preview version of graphscope can resolve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants