Skip to content
Snippets Groups Projects

Repository graph

You can move around the graph by using the arrow keys.
Select Git revision
  • #103-publish-v2-events-to-v1-topic
  • 47-pipeline
  • 47-pipeline-master
  • GONRG-11166-acceptance-tests
  • IBM_integration_test_fix protected
  • M24_storage_backup_branch
  • Stanislav_Riabokon-master-patch-83930
  • acceptance-test
  • acceptance-test-new-module
  • acl_fixes_m22
  • acl_fixes_m22_log
  • acl_issue protected
  • aws-helm-poc
  • aws-helm-poc-update protected
  • aws-m24-rel-test
  • aws-security-disclaimer
  • aws/acceptance-tests protected
  • aws/arm protected
  • aws/feat/replay protected
  • aysriva/fix-404 protected
  • v0.27.2 protected
  • v0.28.2 protected
  • v0.28.1 protected
  • v0.28.0 protected
  • v0.27.1-aws.3 protected
  • v0.27.1-aws.2 protected
  • v0.27.1 protected
  • v0.27.0 protected
  • v0.26.0 protected
  • v0.25.0 protected
  • v0.24.0 protected
  • v0.23.0 protected
  • v0.22.0-gc.1 protected
  • v0.22.0 protected
  • v0.21.0 protected
  • v0.20.0 protected
  • v0.18.2 protected
  • v0.19.2 protected
  • v0.19.1 protected
  • v0.19.0 protected
40 results
Created with Raphaël 2.2.09Apr876432131Mar282726252420191813121110654328Feb27252421201413126531Jan302927201615141310987623Dec2019175328Nov26252120181413121187631Oct3028252423221716151198743130Sep26252423201913121110965329Aug28272621201613872131Jul302927262423151110985124Jun20181714131211631May302423222116131072130Apr29272624231816151211108543128Mar27262522201917141211109865432129Feb2827fix: typo in search url resulting in failed requestfix: fix assertion not matching response structurefix: using getActiveRecordsCountForKinds which is more performant than getActiveRecordsfix: fixing validation and errors to match expected integration test behaviordocs: updating AWS README and implementation guide with latest replay changeschore: enabling and adding integration tests for replay featurechore: simplifying pub-sub pattern to use a single replay topic (removing reindex topic) since there is no significant difference in functionality that is worth the added complexityrevert refactor to do for v2 anywaymajor refactor for complexity fix sonarsonar buigsround 2sonar complexity score loweringchore: updating unit tests to accomodate new query by GSI changessonar fixesfix: creating GSI for kind and replayId for status lookup and fixing GET status endpointfix: issue where replay status is QUEUED for fully processed kindsfix: issue where all records for all partitions regardless of status were being counted in totalRecords. Using existing getAllRecordsFromKind class to handle totalRecords count to ensure consistencyfix: passing headers to replay queue message attributes so they are consumable by replay message processorMerge branch 'handle-cosmosdb-413' into 'master'chore: updating unit tests with async batch processing changesfeat: handling replay requests in an async parallel batch process to avoid request timeoutsfix: unable to reolve unused routing propety variableschore: removing routing properties from class fields as they are no longer neededfix: sns topic arn naming conventiondocs: updating AWS implementation guide with latest changeschore: updating unit tests to reflect latest changesfix: adding record metadata to SNS record to fix indexer not knowing kind; adding all metadata that would be included with a normal storage update requestfix: removing circular dependency with replay service and replay message handler after replay service split. Now overriding default replay service behavior so individual items for each kind are created in the dynamo table for better traceability and performancechore: splitting AWS replay service into two separate classes; one to handle HTTP requests and one to handle SQS messages to follow single responsibility principal and to avoid circular dependencies in future refactoring to override parent replay service. Also fixed a bug where user id is not set but required when publishing storage SNS messagesthrow original app exception from core lib azure as suggestedtrusted-handle-…trusted-handle-cosmosdb-413fix: several issues with handling of collaboration context, publishing record change messages, and handling of messages from SQS queue. Still having an issue with REPLAY ALL operation always trying to retrieve all kinds despite each SQS message containing the kind; this is controlled in common code and need to find an elegant solution to thisfix: wrapping scheduled poll in a request scope to handle replay messages from SQSfix: enabling scheduling annotation by creating AWS main applicationfix: returning id instead of entity type as kindfix: changing implementation to use Schema service to retrieve unique kinds since there is no efficient way of querying the record metadata table to retrieve unique kindschange the app exception throwing logic to capture error code and cover all cases not just 413add dedicated catch clause for 413 as suggestedMerge branch 'cimpl-storage' into 'master'fix: using record metadata to retrieve all kinds instead of empty schema repository table which has long been deprecatedupdate the logic to rethrow the error reason and message from exception as suggested