-
Notifications
You must be signed in to change notification settings - Fork 4
Rira 13.managing datasets #176
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
base: stage
Are you sure you want to change the base?
Conversation
We need to finish tests for dataset router and dataset service. The rest of the tests works.
Rira 17.unit tests
Created ADD,PUT and DELETE functionalities for arrangements and measure names
- deleted unnecessary prints and comments - add dataset methods to GriseraAPI - fixed get_datasets - create_dataset and delete_dataset need to be fixed
grisera api communicates with graph api to create a dataset of given name
there is an error with indexes (hope to fix it on Monday): File "/app/database_service.py", line 89, in check_if_database_exists grisera-framework-graph_api-1 | for db in response['results'][0]['data']: grisera-framework-graph_api-1 | IndexError: list index out of range
Before the creation of the dataset, the system checks if the database with this name already exists. If so, the database is not created and the user receives an error with the error cause
Auto creation during creating new dataset
Hash_name will be used as an identifier for the dataset by user
…ed in correct dataset When the dataset is created, inside it 4 types of nodes are created (35 nodes in total): - Alias - Channel - Life Activity - Modality
…Activity Added POST,DELETE and PUT for Activity
…rrangements-and-measure_names RIRA-25/26
…into RIRA-13.Managing-datasets
…into RIRA-13.Managing-datasets
…A/grisera-framework into RIRA-13.Managing-datasets
theNIGHTMAR3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A lot of work, finally done, great job!
theNIGHTMAR3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job!
mrwrob
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems fine, although it is not a big PR to analyze it deeply. Please address the comments.
graph_api/dataset/dataset_router.py
Outdated
| @router.get("/datasets", tags=["datasets"], response_model=DatasetsOut) | ||
| async def get_datasets(self, response: Response): | ||
| """ | ||
| Get all datasets by name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it gettin datasets by name?
graph_api/dataset/dataset_service.py
Outdated
| # found = self.db.dataset_exists(name_hash) | ||
| # | ||
| # if not found: | ||
| # return DatasetOut(errors="Dataset not found") | ||
| # | ||
| # # get the alias from the DB | ||
| # get_aliases_response = self.db.get_aliases_from_database(name_hash) | ||
| # name_by_user = "" | ||
| # for row in get_aliases_response["results"][0]["data"]: | ||
| # if "row" in row: | ||
| # if "name_by_user" in row['row'][0]: | ||
| # name_by_user = row['row'][0]['name_by_user'] | ||
| # return DatasetOut(name_hash=name_hash, name_by_user=name_by_user) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this commented out? Please provide explanation in comments.
graph_api/database_service.py
Outdated
| Result of request | ||
| """ | ||
|
|
||
| # self.database_url = replace_db_name(self.database_url, database_name) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this commented out? Please provide explanation in comments.
|
You should add dataset_name parameter in appropriate functions in each abstract class ..._service. Not only in the implementations of these classes for graphdb. |
mrwrob
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Next time, please respond to comments (e.g. corrected or done)
During working on this branch my team was able to accomplish several goals: