update logging library to latest, update core common library to add client option to rediscache construction
- update logging library so that correlation id and dependency logs would be included
- update core common library to the latest, and add client option to redis cache construction where we set connection timeout as 15sec, following the best practice of Azure Redis for Cache
Merge request reports
![Hema Vishnu Pola [Microsoft]](https://secure.gravatar.com/avatar/8d4e0c93fe89e2f85e29b72e87f8168cded34a9b5457c63b103dcefdd73b88b7?s=80&d=identicon){kind=avatar}
Activity
added 1 commit
- a8413c4c - add clientOprtions to redis cache construction
added 4 commits
-
a8413c4c...b3e74933 - 2 commits from branch
master - 11adbe15 - Merge branch 'master' into update-library
- 9ba81c9d - rebase
-
a8413c4c...b3e74933 - 2 commits from branch
@krveduru - Please take a look at this MR.
@nthakur @KellyZhou - Seems like because of bringing the latest core-lib azure library, it already has the Partition Service Client, which seems to be looking for the PARTITION_API and the startup is failing.
added 84 commits
-
5d54bb55...3188028c - 83 commits from branch
master - 14cd1d6c - Merge branch 'master' into update-library
-
5d54bb55...3188028c - 83 commits from branch
added 1 commit
- d6d10d82 - lazy load factory change from core-lib-azure
Thanks @polavishnu, I have updated the MR. There is related change in core-lib-azure that needs to go in first. Can you please take a look at that as well?
added 1 commit
- e318a239 - update NOTICE and fix the gcp int test failures
added 1 commit
- 424ffc31 - config connection timeout in the application.properties
@krveduru @polavishnu I resolved all your comments and rebased the code to the latest merge. Could you please review again and approve?
- Resolved by Mingyang Zhu
@Oleksandr_Kosse @aliaksandr_ramanovich @aliaksandr_lubouski I have met the osdu-gcp-containerized-gitlab step failure in multiple MRs, sometimes it is autoresolved after retry, sometimes not. For this one, I have retried 3 times, still the same, based on the message, seems it can't connect to the docker daemon. I don't think this is related to the code change in this MR, could you please take a look and confirm?
- Last reply by Mingyang Zhu
added 6 commits
-
7a9ab23d...50676bf6 - 4 commits from branch
master - 5d11b96e - Merge remote-tracking branch 'origin/master' into update-library
- 01d6f5e2 - remove extra property
-
7a9ab23d...50676bf6 - 4 commits from branch
- Resolved by Mingyang Zhu
@mzhu9 - Can we rebase to have latest changes from master? MR looks good to me.
- Last reply by Mingyang Zhu
- Resolved by Mingyang Zhu
Some how I still see that this branch is behind master branch commits.
- Last reply by Mingyang Zhu
added 21 commits
-
779761e8...3672fc12 - 13 commits from branch
master - 213326fd - add clientOprtions to redis cache construction
- b84ef030 - update NOTICE and fix the gcp int test failures
- 1901df19 - fix the int test failures
- 5806afc4 - consume updated core-lib-azure
- 362c331c - config connection timeout in the application.properties
- 6f00abcd - IT tests
- d6931e7e - Merge branch 'update-library' of...
- a753241c - remove PARTITION_API
Toggle commit list-
779761e8...3672fc12 - 13 commits from branch
- Resolved by Mingyang Zhu
@wsmatth aws int tests failed in the pipeline. This is an azure only change, it should not be caused by the code change. I saw the same failure on the master: https://community.opengroup.org/osdu/platform/system/partition/-/pipelines/40474. Could you please confirm this is the case?
- Last reply by Mingyang Zhu
mentioned in commit 009ea359
added Azure label
changed milestone to %M6 - Release 0.9
