-
Notifications
You must be signed in to change notification settings - Fork 81
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
Add visibility for shared tables and folder consumption #283
Labels
status: in-progress
This issue has been picked and is being implemented
type: enhancement
Feature enhacement
Milestone
Comments
dlpzx
changed the title
Add visibility for shared tables and folder consumption
Add visibility for shared tables and folder consumption and refresh UI
Jan 27, 2023
dlpzx
changed the title
Add visibility for shared tables and folder consumption and refresh UI
Add visibility for shared tables and folder consumption
Jan 31, 2023
dlpzx
added
the
status: in-progress
This issue has been picked and is being implemented
label
Feb 1, 2023
dlpzx
added a commit
that referenced
this issue
Feb 1, 2023
### Feature or Bugfix - Feature ### Detail - Added "shared" db name and access point names in the UI - Added "shared" db name and access point names as part of the shareObject graphQL schema The result is that users can view relevant information to consume data that has been shared with them directly from the shares view. They can copy to their clipboards a command to list the objects inside a shared folders using the AWS CLI or they can copy an SQL statement to use in Athena and query shared tables. ![image](https://user-images.githubusercontent.com/71252798/216063148-dabb0834-a1bd-45e6-8446-916540efc871.png) ### Relates - #283 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
dlpzx
added a commit
that referenced
this issue
Feb 3, 2023
### Feature or Bugfix - Feature ### Detail - Added "shared" db name and access point names in the UI - Added "shared" db name and access point names as part of the shareObject graphQL schema The result is that users can view relevant information to consume data that has been shared with them directly from the shares view. They can copy to their clipboards a command to list the objects inside a shared folders using the AWS CLI or they can copy an SQL statement to use in Athena and query shared tables. ![image](https://user-images.githubusercontent.com/71252798/216063148-dabb0834-a1bd-45e6-8446-916540efc871.png) ### Relates - #283 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
good to close this out @dlpzx ? |
noah-paige
pushed a commit
to noah-paige/aws-dataall
that referenced
this issue
Mar 2, 2023
### Feature or Bugfix - Feature ### Detail - Added "shared" db name and access point names in the UI - Added "shared" db name and access point names as part of the shareObject graphQL schema The result is that users can view relevant information to consume data that has been shared with them directly from the shares view. They can copy to their clipboards a command to list the objects inside a shared folders using the AWS CLI or they can copy an SQL statement to use in Athena and query shared tables. ![image](https://user-images.githubusercontent.com/71252798/216063148-dabb0834-a1bd-45e6-8446-916540efc871.png) ### Relates - data-dot-all#283 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
status: in-progress
This issue has been picked and is being implemented
type: enhancement
Feature enhacement
Is your idea related to a problem? Please describe.
It is difficult to know how to consume data once I have requested access to tables and folders
Describe the solution you'd like
I would like a copy/paste command to the access points of the shared folders and the clear information of the shared database that I can use to query shared tables.
The text was updated successfully, but these errors were encountered: