fix(interactive): Support elementMap() for a path entry in GOpt #3992
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
A related issue should be addressed #3991. Currently, a temporally solution is to ignore the exception and further parse the result value. |
longbinlai
reviewed
Jul 4, 2024
| It is important to note that the specific elements targeted for property projection are determined by the `RESULT_OPT` setting. | ||
| For instance, if you configure `RESULT_OPT` as `ALL_V`, `values()` or `valueMap()` will then project the properties of all vertices present in the path. | ||
| For instance, if you configure `RESULT_OPT` as `ALL_V`, `values()`, `valueMap()`, or `elementMap()` will then project the properties of all vertices present in the path. |
There was a problem hiding this comment.
Add doc for explaining when certain attributes does not exist.
longbinlai
previously approved these changes
Jul 5, 2024
BingqingLyu
added a commit
to shirly121/GraphScope
that referenced
this pull request
Jul 24, 2024
…aba#3992) As titled. Now we support elementMap() for a path entry in GOpt, an example is as below: ``` gremlin> g.V().hasLabel("person").both("1..3","knows").with('RESULT_OPT', 'ALL_V').elementMap("name","age") ==>[{age=27, name=vadas, ~id=2, ~label=0}, {age=29, name=marko, ~id=1, ~label=0}] ==>[{age=32, name=josh, ~id=4, ~label=0}, {age=29, name=marko, ~id=1, ~label=0}] ==>[{age=29, name=marko, ~id=1, ~label=0}, {age=27, name=vadas, ~id=2, ~label=0}] ==>[{age=29, name=marko, ~id=1, ~label=0}, {age=32, name=josh, ~id=4, ~label=0}] ==>[{age=27, name=vadas, ~id=2, ~label=0}, {age=29, name=marko, ~id=1, ~label=0}, {age=27, name=vadas, ~id=2, ~label=0}] ==>[{age=27, name=vadas, ~id=2, ~label=0}, {age=29, name=marko, ~id=1, ~label=0}, {age=32, name=josh, ~id=4, ~label=0}] ==>[{age=32, name=josh, ~id=4, ~label=0}, {age=29, name=marko, ~id=1, ~label=0}, {age=27, name=vadas, ~id=2, ~label=0}] ==>[{age=32, name=josh, ~id=4, ~label=0}, {age=29, name=marko, ~id=1, ~label=0}, {age=32, name=josh, ~id=4, ~label=0}] ==>[{age=29, name=marko, ~id=1, ~label=0}, {age=27, name=vadas, ~id=2, ~label=0}, {age=29, name=marko, ~id=1, ~label=0}] ==>[{age=29, name=marko, ~id=1, ~label=0}, {age=32, name=josh, ~id=4, ~label=0}, {age=29, name=marko, ~id=1, ~label=0}] ``` Fixes alibaba#3988 --------- Co-authored-by: Longbin Lai <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
As titled. Now we support elementMap() for a path entry in GOpt, an example is as below:
Related issue number
Fixes #3988