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

how to describe the user? #2574

Closed
yixinglu opened this issue Aug 25, 2021 · 3 comments · Fixed by #3300
Closed

how to describe the user? #2574

yixinglu opened this issue Aug 25, 2021 · 3 comments · Fixed by #3300
Assignees
Labels
type/feature req Type: feature request
Milestone

Comments

@yixinglu
Copy link
Contributor

Now i can lookup all users in a space, but i could not find a way to describe a user like this:

describe user root;

| user | roles in spaces |
+:----+----------------+
| root | root in nba, admin in sp2 |
@yixinglu yixinglu added the type/feature req Type: feature request label Aug 25, 2021
@bright-starry-sky
Copy link
Contributor

as below ?
query = 'SHOW ROLES IN space'
expected_result = [['guest', 'GUEST'],
['user', 'USER'],
['dba', 'DBA'],
['admin', 'ADMIN']]

@yixinglu
Copy link
Contributor Author

as below ?
query = 'SHOW ROLES IN space'
expected_result = [['guest', 'GUEST'],
['user', 'USER'],
['dba', 'DBA'],
['admin', 'ADMIN']]

I know the show roles in space usage. Now SHOW users only give the name of user. I don't know how to get more information if i am interest in a special user.

@critical27
Copy link
Contributor

critical27 commented Aug 31, 2021

Could consider later if necessary, not so important. Set to v2.7 temporally

@Sophie-Xie Sophie-Xie added this to To Do in Nebula Graph Core v2.6.0 via automation Sep 22, 2021
@Sophie-Xie Sophie-Xie removed this from To Do in Nebula Graph Core v2.6.0 Sep 22, 2021
@Sophie-Xie Sophie-Xie modified the milestones: v2.7.0, v3.0.0 Oct 15, 2021
This was referenced Nov 10, 2021
@heroicNeZha heroicNeZha linked a pull request Nov 24, 2021 that will close this issue
7 tasks
yixinglu pushed a commit to yixinglu/nebula that referenced this issue Sep 14, 2023
<!--
Thanks for your contribution!
In order to review PR more efficiently, please add information according to the template.
-->

## What type of PR is this?
- [ ] bug
- [ ] feature
- [x] enhancement

## What problem(s) does this PR solve?
Split the optimizer rule `PushFilterDownTraverseRule` to `PushFilterThroughAppendVerticesRule` and `PushFilterDownTraverseRule`.

This pr is for refactoring purposes but also introduces some optimizations, such as non-endpoint predicates that can be pushed down before AppendVertices.

The purpose of refactoring is that the previous implementation was too ad-hoc for further optimization, and there were some conflicts between rules, so we should try to avoid similar code implementation from a more common perspective, especially for the development of optimizer.

## Checklist:
Tests:
- [ ] Unit test(positive and negative cases)
- [ ] Function test
- [ ] Performance test
- [ ] N/A

Affects:
- [ ] Documentation affected (Please add the label if documentation needs to be modified.)
- [ ] Incompatibility (If it breaks the compatibility, please describe it and add the label.)
- [ ] If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
- [ ] Performance impacted: Consumes more CPU/Memory



Migrated from vesoft-inc#5470

Co-authored-by: kyle.cao <kyle.cao@vesoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature req Type: feature request
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants