-
Notifications
You must be signed in to change notification settings - Fork 1
#247 Implement basics of FlowReader #306
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
Conversation
* created new module Info * the new modul added to JaCoco and CI routines
* JaCoCo exclusion for model
* created Provider to query the data from server * support for Future, IO, and ZIO based providers * work in progress
* fixed license headers
…endpoints-from-info-module
…endpoints-from-info-module
reader/src/test/scala/za/co/absa/atum/reader/implicits/PaginatedResponseImplicitsTest.scala
Outdated
Show resolved
Hide resolved
reader/src/test/scala/za/co/absa/atum/reader/implicits/PaginatedResponseImplicitsTest.scala
Outdated
Show resolved
Hide resolved
reader/src/test/scala/za/co/absa/atum/reader/FlowReaderUnitTests.scala
Outdated
Show resolved
Hide resolved
reader/src/test/scala/za/co/absa/atum/reader/implicits/PaginatedResponseImplicitsTest.scala
Outdated
Show resolved
Hide resolved
* addressed PR comments
reader/src/main/scala/za/co/absa/atum/reader/core/PartitioningIdProvider.scala
Outdated
Show resolved
Hide resolved
reader/src/main/scala/za/co/absa/atum/reader/exceptions/RequestException.scala
Show resolved
Hide resolved
| package za.co.absa.atum.reader.requests | ||
|
|
||
| object QueryParamNames { | ||
| val limit = "limit" |
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 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.
Yes, and also why not making them final?
lsulak
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.
Review finished, just few very very minor Qs / notes
| * @param offset - offset of the page (starting position) | ||
| * @return - a page of checkpoints | ||
| */ | ||
| def getCheckpointsOfNamePage(checkpointName: String, pageSize: Int = 10, offset: Long = 0): F[RequestResult[PaginatedResponse[CheckpointWithPartitioningDTO]]] = { |
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 not to have just 1 function with checkpointName being Option[String] ?
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 see it as inconvenient call.
And this way it clearly differentiate in the function name when only name-filtered entries are requested,
But can be unifies if seen as preferential.
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 see it as: little convenience for users, little duplicity for developers. Less # of APIs & less code: better :D
But I don't mind, it's a matter of style, if you want to keep it I'm definitely okay with it
FlowReadeis now a simple class to just retrieve checkpoints of the identified flow.ApiPathsmoved from_Server_ to Modelbasic->coreCloses #247
Release notes:
FlowReaderimplemented to return the flow's checkpoints (requested and returned in a paginated form)