Added KapuaQuery.defaultSortCriteria #3287
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an API method which enforces the implementation of the queries to define a default sorting which will be used if kapuaQuery.sortCriteria is not defined.
Not this is achieved by the definition on the
AbstractKapuaQuery
constructor and can happen that if someone does not uses the default constructor withsuper()
the sorting is not set.Related Issue
None
Description of the solution adopted
Added
getDefaultSortCriteria
toKapuaQuery
API and a default implementation which defaults to sortingKapuaEntity.id
.Added also a new extendsion of
AbstractKapuaQuery
forKapuaNamedEntity
es to default the sorting of theKapuaNamedEntities
toname
which is the most common sorting for those entities (i.e. User, Account, ...).Added indexes on
scopeId, name
fields on Account, User and Job table to improve performances when searching and sorting by name from the console.Screenshots
None
Any side note on the changes made
FIxed javadoc for classes