{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":681341608,"defaultBranch":"main","name":"GPTCache","ownerLogin":"gauthamchandra","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2023-08-21T19:56:51.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/5430280?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1698766317.0","currentOid":""},"activityList":{"items":[{"before":"35d87040428c8a3e6e743a3dc50eacda55578ecb","after":null,"ref":"refs/heads/dev","pushedAt":"2023-10-31T15:31:57.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"}},{"before":"0ccdb2e044efbc848d45ba4b472c97f01f6de392","after":"35d87040428c8a3e6e743a3dc50eacda55578ecb","ref":"refs/heads/dev","pushedAt":"2023-09-02T15:17:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"feat: Add scalar storage support for DynamoDB\n\nThis change allows GPTCache to use DynamoDB as the underlying scalar\nstorage for the cache.\n\nThe underlying implementation uses 2 tables:\n\n- `gptcache_questions` - which holds all questions and session\n  information.\n- `gptcache_reports` - which holds the reporting information.\n\nNormally, we would do a single table design and rollup\n`gptcache_reports` into the same table as `gptcache_questions`. However,\nthis was not done for one key reason: billing.\n\nIn the event a lot of analytics data is being created, then table scans\nfor operations like `count()` and `get_ids()` would also involve reading\nthese reporting rows before filtering them out, resulting in higher\nread costs for end users of GPTCache.\n\nSigned-off-by: Gautham Chandra <gautham.chandra@live.com>","shortMessageHtmlLink":"feat: Add scalar storage support for DynamoDB"}},{"before":"1587ffb2c20cd296ee7d8900d0b02eb5f72b3ed7","after":"0ccdb2e044efbc848d45ba4b472c97f01f6de392","ref":"refs/heads/dev","pushedAt":"2023-09-02T14:16:50.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"feat: Add scalar storage support for DynamoDB\n\nThis change allows GPTCache to use DynamoDB as the underlying scalar\nstorage for the cache.\n\nThe underlying implementation uses 2 tables:\n\n- `gptcache_questions` - which holds all questions and session\n  information.\n- `gptcache_reports` - which holds the reporting information.\n\nNormally, we would do a single table design and rollup\n`gptcache_reports` into the same table as `gptcache_questions`. However,\nthis was not done for one key reason: billing.\n\nIn the event a lot of analytics data is being created, then table scans\nfor operations like `count()` and `get_ids()` would also involve reading\nthese reporting rows before filtering them out, resulting in higher\nread costs for end users of GPTCache.\n\nSigned-off-by: Gautham Chandra <gautham.chandra@live.com>","shortMessageHtmlLink":"feat: Add scalar storage support for DynamoDB"}},{"before":"5eb52a50c3197666c7aa58389e96c12941cf3252","after":"1587ffb2c20cd296ee7d8900d0b02eb5f72b3ed7","ref":"refs/heads/dev","pushedAt":"2023-09-02T13:29:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"feat: Add scalar storage support for DynamoDB\n\nThis change allows GPTCache to use DynamoDB as the underlying scalar\nstorage for the cache.\n\nThe underlying implementation uses 2 tables:\n\n- `gptcache_questions` - which holds all questions and session\n  information.\n- `gptcache_reports` - which holds the reporting information.\n\nNormally, we would do a single table design and rollup\n`gptcache_reports` into the same table as `gptcache_questions`. However,\nthis was not done for one key reason: billing.\n\nIn the event a lot of analytics data is being created, then table scans\nfor operations like `count()` and `get_ids()` would also involve reading\nthese reporting rows before filtering them out, resulting in higher\nread costs for end users of GPTCache.\n\nSigned-off-by: Gautham Chandra <gautham.chandra@live.com>","shortMessageHtmlLink":"feat: Add scalar storage support for DynamoDB"}},{"before":"86f46e7ffc0963a8a0b914040185f575889fb335","after":"5eb52a50c3197666c7aa58389e96c12941cf3252","ref":"refs/heads/dev","pushedAt":"2023-09-01T16:29:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"feat: Add scalar storage support for DynamoDB\n\nThis change allows GPTCache to use DynamoDB as the underlying scalar\nstorage for the cache.\n\nThe underlying implementation uses 2 tables:\n\n- `gptcache_questions` - which holds all questions and session\n  information.\n- `gptcache_reports` - which holds the reporting information.\n\nNormally, we would do a single table design and rollup\n`gptcache_reports` into the same table as `gptcache_questions`. However,\nthis was not done for one key reason: billing.\n\nIn the event a lot of analytics data is being created, then table scans\nfor operations like `count()` and `get_ids()` would also involve reading\nthese reporting rows before filtering them out, resulting in higher\nread costs for end users of GPTCache.\n\nSigned-off-by: Gautham Chandra <gautham.chandra@live.com>","shortMessageHtmlLink":"feat: Add scalar storage support for DynamoDB"}},{"before":"18b9a94d48eb3c2436a12b04bae8fec553c27e96","after":"86f46e7ffc0963a8a0b914040185f575889fb335","ref":"refs/heads/dev","pushedAt":"2023-08-31T17:26:33.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"feat: Add scalar storage support for DynamoDB\n\nThis change allows GPTCache to use DynamoDB as the underlying scalar\nstorage for the cache.\n\nThe underlying implementation uses 2 tables:\n\n- `gptcache_questions` - which holds all questions and session\n  information.\n- `gptcache_reports` - which holds the reporting information.\n\nNormally, we would do a single table design and rollup\n`gptcache_reports` into the same table as `gptcache_questions`. However,\nthis was not done for one key reason: billing.\n\nIn the event a lot of analytics data is being created, then table scans\nfor operations like `count()` and `get_ids()` would also involve reading\nthese reporting rows before filtering them out, resulting in higher\nread costs for end users of GPTCache.\n\nSigned-off-by: Gautham Chandra <gautham.chandra@live.com>","shortMessageHtmlLink":"feat: Add scalar storage support for DynamoDB"}},{"before":"d55593b4d499fbafb489e1df7b63d495bb3bdba4","after":"18b9a94d48eb3c2436a12b04bae8fec553c27e96","ref":"refs/heads/dev","pushedAt":"2023-08-31T17:18:52.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"feat: Add scalar storage support for DynamoDB\n\nThis change allows GPTCache to use DynamoDB as the underlying scalar\nstorage for the cache.\n\nThe underlying implementation uses 2 tables:\n\n- `gptcache_questions` - which holds all questions and session\n  information.\n- `gptcache_reports` - which holds the reporting information.\n\nNormally, we would do a single table design and rollup\n`gptcache_reports` into the same table as `gptcache_questions`. However,\nthis was not done for one key reason: billing.\n\nIn the event a lot of analytics data is being created, then table scans\nfor operations like `count()` and `get_ids()` would also involve reading\nthese reporting rows before filtering them out, resulting in higher\nread costs for end users of GPTCache.","shortMessageHtmlLink":"feat: Add scalar storage support for DynamoDB"}},{"before":"2497564d68cdb9e5b142b1e7aa2892e2ff6f474d","after":"d55593b4d499fbafb489e1df7b63d495bb3bdba4","ref":"refs/heads/dev","pushedAt":"2023-08-31T15:05:48.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"feat: Add scalar storage support for DynamoDB\n\nThis change allows GPTCache to use DynamoDB as the underlying scalar\nstorage for the cache.\n\nThe underlying implementation uses 2 tables:\n\n- `gptcache_questions` - which holds all questions and session\n  information.\n- `gptcache_reports` - which holds the reporting information.\n\nNormally, we would do a single table design and rollup\n`gptcache_reports` into the same table as `gptcache_questions`. However,\nthis was not done for one key reason: billing.\n\nIn the event a lot of analytics data was being created, then table scans\nfor operations like `count()` and `get_ids()` would also involve reading\nthese reporting rows before filtering them out, resulting in higher\nread costs for end users of GPTCache.","shortMessageHtmlLink":"feat: Add scalar storage support for DynamoDB"}},{"before":"b25dd190876663965f2b261aec51a2d59a22d709","after":"2497564d68cdb9e5b142b1e7aa2892e2ff6f474d","ref":"refs/heads/dev","pushedAt":"2023-08-29T20:49:46.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"wip","shortMessageHtmlLink":"wip"}},{"before":"790e9f4211929a0b06b640f9c77b54e842b183af","after":"b25dd190876663965f2b261aec51a2d59a22d709","ref":"refs/heads/dev","pushedAt":"2023-08-29T13:16:26.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"wip","shortMessageHtmlLink":"wip"}},{"before":"564efafdb87bb05616fc939db6d48ff16120b4db","after":"790e9f4211929a0b06b640f9c77b54e842b183af","ref":"refs/heads/dev","pushedAt":"2023-08-25T22:10:19.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"Update the version to `0.1.40`\n\nSigned-off-by: SimFG <bang.fu@zilliz.com>","shortMessageHtmlLink":"Update the version to <code>0.1.40</code>"}},{"before":"d6d484d6bdc3969f9728444e0dbc9f09736b3411","after":"790e9f4211929a0b06b640f9c77b54e842b183af","ref":"refs/heads/main","pushedAt":"2023-08-25T22:09:37.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"Update the version to `0.1.40`\n\nSigned-off-by: SimFG <bang.fu@zilliz.com>","shortMessageHtmlLink":"Update the version to <code>0.1.40</code>"}},{"before":"c2deaec9608bd05c2b551536f6d31e0e7132c444","after":"564efafdb87bb05616fc939db6d48ff16120b4db","ref":"refs/heads/dev","pushedAt":"2023-08-25T22:09:11.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"gauthamchandra","name":"Gautham Chandra","path":"/gauthamchandra","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5430280?s=80&v=4"},"commit":{"message":"wip","shortMessageHtmlLink":"wip"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyMy0xMC0zMVQxNTozMTo1Ny4wMDAwMDBazwAAAAOkKReE","startCursor":"Y3Vyc29yOnYyOpK7MjAyMy0xMC0zMVQxNTozMTo1Ny4wMDAwMDBazwAAAAOkKReE","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wOC0yNVQyMjowOToxMS4wMDAwMDBazwAAAANy1k6N"}},"title":"Activity · gauthamchandra/GPTCache"}