Skip to content
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

Bug fixes and dependency updates for version 3.6.0 #265

Merged
merged 7 commits into from
Jun 24, 2024

Conversation

barrycaceres
Copy link
Contributor

  • Changed entity ID bound type to String to allow max
  • Changed entity ID bound default value to be conditional on bound type
  • Changed relation key to allow max, max:<num> and <num>:max
  • Changed relation key bound default value to be conditional on bound type
  • Fixed relation query to use DESC clause on ORDER BY of both entity ID's
  • Updated spec to version 3.6.0 in accordance with type changes
  • Updated dependencies:
    • Updated senzing-commons from version 3.2.0 to 3.3.0
    • Updated senzing-api-server from version 3.5.10 to 3.5.12
    • Updated senzing-listener from version 0.5.7 to 0.5.9
    • Updated data-mart-replicator from version 1.1.2 to 1.1.3
    • Updated jersey-xxxx dependencies from version 2.41 to 2.43
    • Updated jackson-xxxx dependencies from version 2.16.1 to 2.17.1
    • Updated commons-csv from version 1.10.0 to 1.11.0
    • Updated icu4j from version 74.2 to 75.1
    • Updated Amazon sqs from version 2.24.12 to 2.26.4
    • Updated amqp-client from version 5.20.0 to 5.21.0
    • Updated maven-surefire-plugin from version 3.2.5 to 3.3.0
    • Updated maven-compiler-plugin from version 3.12.1 to 3.13.0
    • Updated maven-shade-plugin from version 3.5.2 to 3.6.0

…ver implemented

- Fixed SQL syntax error for relations page retrieval
- Changed entity ID bound default value to be conditional on bound type
- Changed relation key to allow "max", "max:[num]" and "[num]:max"
- Changed relation key bound default value to be conditional on bound type
- Fixed relation query to use "DESC" clause on "ORDER BY" of both entity ID's
- Updated spec to version 3.6.0 in accordance with type changes
- Updated senzing-api-server submodule
@barrycaceres barrycaceres requested a review from a team as a code owner June 24, 2024 21:19
@barrycaceres barrycaceres self-assigned this Jun 24, 2024
@barrycaceres barrycaceres merged commit 1ff99c4 into main Jun 24, 2024
7 checks passed
@barrycaceres barrycaceres deleted the caceres.version-3.6.0 branch June 24, 2024 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants