-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature/224 post partitioning #258
Conversation
# Conflicts: # server/src/main/scala/za/co/absa/atum/server/api/controller/PartitioningControllerImpl.scala # server/src/main/scala/za/co/absa/atum/server/api/http/Routes.scala # server/src/main/scala/za/co/absa/atum/server/api/repository/PartitioningRepositoryImpl.scala # server/src/main/scala/za/co/absa/atum/server/api/service/PartitioningServiceImpl.scala
Release notes
|
JaCoCo model module code coverage report - scala 2.13.11
|
JaCoCo agent module code coverage report - scala 2.13.11
|
JaCoCo reader module code coverage report - scala 2.13.11
|
JaCoCo server module code coverage report - scala 2.13.11
|
database/src/main/postgres/runs/V1.9.7__create_partitioning.sql
Outdated
Show resolved
Hide resolved
_status BIGINT; | ||
BEGIN | ||
|
||
id_partitioning := runs._get_id_partitioning(i_partitioning, true); |
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.
the alignment of the fnc body needs to be shifted by 1 tab or something to the right
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.
done
status := 11; | ||
status_text := 'Partitioning created'; | ||
ELSE | ||
status := 31; |
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.
what, is this the only difference, the status code for situation when partitioning is already present? In comparison to runs.create_partitioning_if_not_exists
function. Otherwise I think this is 1:1 copy almost
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.
so I think we shouldn't have same implementation twice..possibly just call runs.create_partitioning_if_not_exists
from this function and change the status code in select / case when statement, if this is really needed
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.
There is a difference in that the new function does register parent partitioning only when the child partitioning does not exist. Anyway I think we should have a call maybe about the create partitioning operation in general ...
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.
Let's find a spot tomorrow. I think/hope it won't be long.
Co-authored-by: Ladislav Sulak <[email protected]>
database/src/main/postgres/runs/V1.9.7__create_partitioning.sql
Outdated
Show resolved
Hide resolved
database/src/main/postgres/runs/V1.9.7__create_partitioning.sql
Outdated
Show resolved
Hide resolved
database/src/main/postgres/runs/V1.9.7__create_partitioning.sql
Outdated
Show resolved
Hide resolved
database/src/main/postgres/runs/V1.9.7__create_partitioning.sql
Outdated
Show resolved
Hide resolved
database/src/main/postgres/runs/V1.9.7__create_partitioning.sql
Outdated
Show resolved
Hide resolved
database/src/main/postgres/runs/V1.9.7__create_partitioning.sql
Outdated
Show resolved
Hide resolved
database/src/main/postgres/runs/V1.9.7__create_partitioning.sql
Outdated
Show resolved
Hide resolved
server/src/main/scala/za/co/absa/atum/server/api/controller/PartitioningControllerImpl.scala
Show resolved
Hide resolved
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.
- code reviewed
- pulled
- built
- run
|
||
INSERT INTO runs.partitionings (partitioning, created_by) | ||
VALUES (i_partitioning, i_by_user) | ||
RETURNING partitionings.id_partitioning INTO create_partitioning.id_partitioning; |
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.
I didn't know that these were possible :)
-- Parameters: | ||
-- i_partitioning - partitioning to create or which existence to check | ||
-- i_by_user - user behind the change | ||
-- i_parent_partitioning_id - (optional) parent partitioning id |
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.
-- i_parent_partitioning_id - (optional) parent partitioning id | |
-- i_parent_partitioning_id - (optional) parent partitioning id, must already exist if specified |
or something like that
Introduces POST endpoint for partitioning creation
Closes #224
Release notes: