{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":105944401,"defaultBranch":"master","name":"yugabyte-db","ownerLogin":"yugabyte","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2017-10-05T21:56:00.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/17074854?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1718080647.0","currentOid":""},"activityList":{"items":[{"before":"43f64aa4e716d3807c01f0ba5eeb93a9e86d66bc","after":"8ab2c1ee443d5b84990be97a1292b8e6d16efadc","ref":"refs/heads/2024.1","pushedAt":"2024-06-11T06:00:29.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"vipul-yb","name":"Vipul Bansal","path":"/vipul-yb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/86227026?s=80&v=4"},"commit":{"message":"[BACKPORT 2024.1][PLAT-11850]: Add support to removed dropped index/table from xcluster/dr\n\nSummary:\nAdded support to remove dropped index_table/table from xclyuster/dr.\nAs part of this change, we will avoid fetching index tables for already dropped tables, and customers will have to remove tables and index tables separately.\nOn the newer DB version, it does not require any additional ignore error flags, but since the old DB version requires it, we will pass the ignore error flag while removing dropped tableIDs from replication for both the old and newer versions.\n\nOriginal diff/commit: D34407/D34407\n\nTest Plan:\n - Create universe and setup xcluster/dr having tables and indexes\n - drop tables and indexes from source\n - remove tables and indexes from xcluster/dr\n - verify that tables does not exists anymore in the xcluster_config available in master UI and YBA DB.\n - verified on old YBDB version, where DB errors out while altering replication, and on newer DB version which ignore the errors without any flag.\n\nAdditional test case:\n\n - Removed tables form 2 database where removed 1 table from DB_1 which is not dropped and removed 2 table where one is dropped nad another is not from DB_2 in a single edit replication request.\n\nReviewers: hzare, cwang, sanketh\n\nReviewed By: hzare\n\nSubscribers: yugaware, hsunder, jmak\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35722","shortMessageHtmlLink":"[BACKPORT 2024.1][PLAT-11850]: Add support to removed dropped index/t…"}},{"before":"5abefa0c77a52e57ed1a31149c5045d1e2c54dbf","after":"78ec382ced491bd75971fe94e1413773a6113585","ref":"refs/heads/2.20","pushedAt":"2024-06-11T05:58:59.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"vipul-yb","name":"Vipul Bansal","path":"/vipul-yb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/86227026?s=80&v=4"},"commit":{"message":"[BACKPORT 2.20][PLAT-11850]: Add support to removed dropped index/table from xcluster/dr\n\nSummary:\nAdded support to remove dropped index_table/table from xclyuster/dr.\nAs part of this change, we will avoid fetching index tables for already dropped tables, and customers will have to remove tables and index tables separately.\nOn the newer DB version, it does not require any additional ignore error flags, but since the old DB version requires it, we will pass the ignore error flag while removing dropped tableIDs from replication for both the old and newer versions.\n\nOriginal diff/commit: D34407/D34407\n\nTest Plan:\n - Create universe and setup xcluster/dr having tables and indexes\n - drop tables and indexes from source\n - remove tables and indexes from xcluster/dr\n - verify that tables does not exists anymore in the xcluster_config available in master UI and YBA DB.\n - verified on old YBDB version, where DB errors out while altering replication, and on newer DB version which ignore the errors without any flag.\n\nAdditional test case:\n\n - Removed tables form 2 database where removed 1 table from DB_1 which is not dropped and removed 2 table where one is dropped nad another is not from DB_2 in a single edit replication request.\n\nReviewers: hzare, cwang, sanketh\n\nReviewed By: hzare\n\nSubscribers: yugaware, hsunder, jmak\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35721","shortMessageHtmlLink":"[BACKPORT 2.20][PLAT-11850]: Add support to removed dropped index/tab…"}},{"before":"d1bc2d8c41df7fa862ee33f0044801c9eecdf1e9","after":"29b46566b077a1dd146f8a80627c180741a94f33","ref":"refs/heads/pg15","pushedAt":"2024-06-11T05:15:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"devansh-ism","name":null,"path":"/devansh-ism","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/52438272?s=80&v=4"},"commit":{"message":"[pg15] test: fix yb_create_index\n\nSummary:\nupstreams:\nReject trailing junk after numeric literals : 2549f0661bd28571d7200d6f82f752a7ee5d47e1\nSimplify psql \\d's rule for ordering the indexes of a table: 4d6603f28dfc4a1cab0d7d317855d935e314297a\n\nRemove `YB_TODO` from yb_pg15 test which was intended to be removed after fixing yb_create_index.\n\nTest Plan:\nJenkins: rebase: pg15\n\n for _ in {1..50}; do grep TestPg15Regress pg15_tests/passing_tests.tsv; done | pg15_tests/run_tests.sh\n\nReviewers: jason\n\nReviewed By: jason\n\nSubscribers: jason, yql\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35694","shortMessageHtmlLink":"[pg15] test: fix yb_create_index"}},{"before":"305555b26414c0b093dbc76aa7575433c49cbbf7","after":"d072e370309f284eda2398f9a38854afded446ea","ref":"refs/heads/2.18","pushedAt":"2024-06-10T23:47:31.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hulien22","name":"Julien He","path":"/hulien22","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/32774836?s=80&v=4"},"commit":{"message":"[BACKPORT 2.18][#22618,#22608] docdb: Fix DeleteTabletListAndSendRequests deadlock and deleting xrepl tablets\n\nSummary:\nOriginal commit: aead171e524043624a7045fe6212ddf0eb8a06c5 / D35458\n\nUpdating retained_by_* maps in DeleteTabletListAndSendRequests before committing the tablet locks.\nThis ensures that if there are multiple calls to DeleteTabletListAndSendRequests (eg due to a few\nCleanupSplitTablets calls) that xrepl tablets are only hidden on the first call and ignored for\nlater calls.\n\nAlso fixing the deadlock in DeleteTabletListAndSendRequests that can arise with mutex_ and tablet\nlocks.\nJira: DB-11526, DB-11517\n\nTest Plan: ybd --cxx-test xcluster-tablet-split-itest --gtest_filter \"CdcTabletSplitThreeMastersITest.TestRaceAfterHidingAndRetainingTablet\"\n\nReviewers: xCluster, hsunder, skumar, vkushwaha\n\nReviewed By: hsunder\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35541","shortMessageHtmlLink":"[BACKPORT 2.18][#22618,#22608] docdb: Fix DeleteTabletListAndSendRequ…"}},{"before":"4504580fd69c09ae95858b8963cf128c44e8e15a","after":"889f44fb8153b9535663542d5bf4b4824c9da983","ref":"refs/heads/2.20.4","pushedAt":"2024-06-10T22:06:51.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hulien22","name":"Julien He","path":"/hulien22","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/32774836?s=80&v=4"},"commit":{"message":"[BACKPORT 2.20.4][#22618,#22608] docdb: Fix DeleteTabletListAndSendRequests deadlock and deleting xrepl tablets\n\nSummary:\nOriginal commit: aead171e524043624a7045fe6212ddf0eb8a06c5 / D35458\n\nUpdating retained_by_* maps in DeleteTabletListAndSendRequests before committing the tablet locks.\nThis ensures that if there are multiple calls to DeleteTabletListAndSendRequests (eg due to a few\nCleanupSplitTablets calls) that xrepl tablets are only hidden on the first call and ignored for\nlater calls.\n\nAlso fixing the deadlock in DeleteTabletListAndSendRequests that can arise with mutex_ and tablet\nlocks.\nJira: DB-11526, DB-11517\n\nTest Plan: ybd --cxx-test xcluster-tablet-split-itest --gtest_filter \"CdcTabletSplitThreeMastersITest.TestRaceAfterHidingAndRetainingTablet\"\n\nReviewers: xCluster, hsunder, skumar, vkushwaha\n\nReviewed By: hsunder\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35728","shortMessageHtmlLink":"[BACKPORT 2.20.4][#22618,#22608] docdb: Fix DeleteTabletListAndSendRe…"}},{"before":"04d0a467e2c4fe4a090daacc6cf7a3e06f9c7530","after":"43f64aa4e716d3807c01f0ba5eeb93a9e86d66bc","ref":"refs/heads/2024.1","pushedAt":"2024-06-10T21:32:13.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hulien22","name":"Julien He","path":"/hulien22","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/32774836?s=80&v=4"},"commit":{"message":"[BACKPORT 2024.1][#22618] docdb: Fix Deadlock in DeleteOrHideTabletsAndSendRequests\n\nSummary:\nOriginal commit: 9efe84e432d2906c28bba89a59081375a6c787a9 / D35457\nRemoving unneccessary sharedlock in DeleteOrHideTabletsAndSendRequests that was causing a potential\ndeadlock.\n\nAlso adding in test for testing #22608 which is how this bug was discovered\nJira: DB-11526\n\nTest Plan: ybd --cxx-test xcluster-tablet-split-itest --gtest_filter \"CdcTabletSplitThreeMastersITest.TestRaceAfterHidingAndRetainingTablet\"\n\nReviewers: xCluster, hsunder, skumar, vkushwaha\n\nReviewed By: hsunder\n\nSubscribers: ybase\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35539","shortMessageHtmlLink":"[BACKPORT 2024.1][#22618] docdb: Fix Deadlock in DeleteOrHideTabletsA…"}},{"before":"261bb58c82a2d069ca010ddb5fdf2acbbd983dd4","after":"fd217ce9dd79ab6726092a6057213e84b462235b","ref":"refs/heads/master","pushedAt":"2024-06-10T18:53:27.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"foucher","name":null,"path":"/foucher","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6496319?s=80&v=4"},"commit":{"message":"[#21093] DocDB: Make debug build able to interoperate with release build\n\nSummary:\nFor debugging purposes it’s sometimes useful to download Yugabyte from the web, where binaries are only available in the release flavor, and restart using a debug build you built locally. Modify the build logic so that debug and release builds are always compatible. Put the column ID debugging offset in ASAN and TSAN builds only.\nJira: DB-10054\n\nTest Plan:\nJenkins\n\nOn MacOS 14 arm64:\n curl https://downloads.yugabyte.com/releases/2.18.4.2/yugabyte-2.18.4.2-b2-darwin-x86_64.tar.gz | tar xzv -C /tmp\n pushd /tmp/yugabyte-2.18.4.2\n bin/yb-ctl create\n popd\n\n ./yb_build.sh fastdebug --sj\n\n bin/yb-ctl restart\n(Success of restart indicates the cluster is compatible.)\n\nI also did some experimentation on AlmaLinux8 to ensure the expected #defines are set in ASAN and TSAN.\n\nReviewers: hsunder, mbautin, skumar\n\nReviewed By: mbautin\n\nSubscribers: skumar, ybase, yql\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D32492","shortMessageHtmlLink":"[#21093] DocDB: Make debug build able to interoperate with release build"}},{"before":"1f8712e211b3d5fc2aa74df523070aaaa93648b1","after":"261bb58c82a2d069ca010ddb5fdf2acbbd983dd4","ref":"refs/heads/master","pushedAt":"2024-06-10T18:14:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"Jethro-M","name":null,"path":"/Jethro-M","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/88681329?s=80&v=4"},"commit":{"message":"[PLAT-13953] Refactor create xCluster modal and make txn ysql the default when possible\n\nSummary:\n**Context**\nNon-txn xCluster replication should only be used for bidirectional xCluster.\nIf a user does not need bidrection xCluster, we strongly suggest using txn xCluster instead because\nit doesn't have the same consistency issues as non-txn xCluster.\n\n**Change**\nThis diff moves the txn xCluster checkbox and table type selection to the first step of the create\nxCluster config modal.\nThis is done to highlight the fact that mixed table type xCluster configs are not allowed.\n\nThe txn xCluster checkbox will now be checked by default if the source and target universe satisfy the\npre-reqs for txn-xCluster.\n\nThe create config modal code is refactored to use react-hook-form instead of formik to stay consistent with all\nour newer form components.\n\nTest Plan:\nCreate ysql txn xCluster config.\nCreate ysql non-txn xCluster config.\nCreate ycql xCluster config.\nCreate an xCluster config that requires bootstrapping and one that does not.\nCreate xCluster DR config.\n\nVerify traveling to previously completed steps doesn't break the form.\nModify previously completed fields and verify the form is still in a valid state.\n- In particular, test the interaction of changing table type/target universe after already\n selecting tables & databases. The change in table type/target universe will make the previous\n table/database selection invalid. We expect the selection to be cleared along with any related\n errors.\n\nReviewers: rmadhavan\n\nReviewed By: rmadhavan\n\nSubscribers: yugaware\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35334","shortMessageHtmlLink":"[PLAT-13953] Refactor create xCluster modal and make txn ysql the def…"}},{"before":"1f8881a8bc44e6c95c9aa67d802c010649954353","after":"305555b26414c0b093dbc76aa7575433c49cbbf7","ref":"refs/heads/2.18","pushedAt":"2024-06-10T16:25:06.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"basavaraj29","name":"Basava Kolagani","path":"/basavaraj29","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17742021?s=80&v=4"},"commit":{"message":"[BACKPORT 2.18][#22630] DocDB: Don't set key bounds for intent iterator used during conflict resolution\n\nSummary:\nOriginal commit: fb9e8f8e18e56a73dff45526713bf6f09700e1d1 / D35543\nAs part of conflict resolution, we create an intent iterator respecting the tablet's key bounds. This could lead to undetected conflicts and violation of serializable isolation guarantees.\n\nFor instance, consider a serializable transaction that did `select * from table`. It would lead to the following strong intent for empty doc key on all tablets of the table\n```\nSubDocKey(DocKey([], []), []) [kStrongRead] -> \n```\n\nDuring conflict resolution, an intent iterator is created using\n```\n intent_iter_ = CreateIntentsIteratorWithHybridTimeFilter(\n doc_db_.intents, &status_manager(), doc_db_.key_bounds, &intent_key_upperbound_);\n```\n\nSo essentially, when another transaction is trying to do an update, it requests weak read/write locks on the empty doc key `DocKey([], [])`. While checking conflicts for this record, we have the following\n```\n Status ReadIntentConflicts(IntentTypeSet type, KeyBytes* intent_key_prefix) {\n ...\n // the below seeks to the tablet's lower key bound when the given target < tablet's lower key bound\n intent_iter_.Seek(intent_key_prefix->AsSlice());\n // and then we exit checking conflicts if the seeked intent record doesn't have prefix \n```\nwhich leads to undetected conflicts for empty doc key - `DocKey([], [])`. And the update/insert that should ideally have been blocked on the serializable txn instead goes through.\n\nThis issue is observed only when all of the following hold true\n1. the tablet has key bounds set, which seems to happen only for tablets created through split.\n2. there is a serializable transaction involved and other transaction are trying to perform a conflicting operation.\n\n**Solution**\nTo address the problem, we create the intent iterator with `kNoBounds` thus allowing it to see all intents of the parent tablet. There should be no significant overhead for this approach, because as part of conflict resolution, the intent iterator seeks to the given entry (by the current transaction) and calls `Next` until the found key doesn't have the supplied key as a prefix. Since post split, the new requests at the child tablet correspond to the keys hosted by the child, it should not result in unnecessary additional `Seek`/`Next` calls. Additionally, compaction on the intentsdb doesn't use key bounds, so the intent record(s) on empty key are preserved through compactions, which is necessary for correctness.\n\nIf there is any perf impact, we should revisit this issue. Here are a couple of other relevant observations-\n1. It is just the empty key that we had issues with in detecting conflicts. If serializable transaction are taken out of the picture, then we shouldn't have had hit such issues with just RC/RR transactions (since the conflict would have been at the key hash or higher, which falls within the tablet's key bounds).\n2. If necessary, we can create the intent iterator with no lower bound, but the upper bound set to the tablet's upper bound.\nJira: DB-11537\n\nTest Plan:\nJenkins\n\n./yb_build.sh --cxx-test pgwrapper_pg_tablet_split-test --gtest_filter PgTabletSplitTest.TestConflictResolutionChecksConflictsAgainstEmptyKey\n\nReviewers: rthallam, timur, arybochkin, sergei\n\nReviewed By: arybochkin\n\nSubscribers: ybase\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35701","shortMessageHtmlLink":"[BACKPORT 2.18][#22630] DocDB: Don't set key bounds for intent iterat…"}},{"before":"10f24bd178285d811bc5ba82cefae1c687ea0ed8","after":"1f8712e211b3d5fc2aa74df523070aaaa93648b1","ref":"refs/heads/master","pushedAt":"2024-06-10T16:12:09.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"shahrooz1997","name":"Hamidreza Zare","path":"/shahrooz1997","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/23063104?s=80&v=4"},"commit":{"message":"Revert \"[PLAT-13870] Support addition of databases in DB scoped DR config\"\n\nSummary:\nThis reverts commit 10f24bd178285d811bc5ba82cefae1c687ea0ed8.\n\nThat commit misses some of the changes in revision D35498, including using the new version of yb-client, leading to master build breakage.\n\nTest Plan: N/A\n\nReviewers: #yba-api-review!, spothuraju, vbansal\n\nReviewed By: spothuraju\n\nSubscribers: yugaware\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35725","shortMessageHtmlLink":"Revert \"[PLAT-13870] Support addition of databases in DB scoped DR co…"}},{"before":"f05a06090625dc2c50b910264dc44b5a20c1d3c6","after":"1f8881a8bc44e6c95c9aa67d802c010649954353","ref":"refs/heads/2.18","pushedAt":"2024-06-10T16:07:17.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"chidmuthu","name":"Muthu Chidambaram","path":"/chidmuthu","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/86024920?s=80&v=4"},"commit":{"message":"[BACKPORT 2.18][PLAT-13835][PLAT-13836] Upgrading python dependencies\n\nSummary: Upgrading setuptools and cyrptography. Running freeze altogether and landing in one diff.\n\nTest Plan: test-suite\n\nReviewers: svarshney, amalyshev, nsingh\n\nReviewed By: amalyshev\n\nSubscribers: yugaware\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35582","shortMessageHtmlLink":"[BACKPORT 2.18][PLAT-13835][PLAT-13836] Upgrading python dependencies"}},{"before":"352020fb910d69a292e2738bd0bb1896095526b3","after":"04d0a467e2c4fe4a090daacc6cf7a3e06f9c7530","ref":"refs/heads/2024.1","pushedAt":"2024-06-10T15:34:27.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"rajmaddy89","name":"Rajagopalan Madhavan","path":"/rajmaddy89","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/10095310?s=80&v=4"},"commit":{"message":"[BACKPORT 2024.1][PLAT-13920]: Not able to increase the tserver volume size through edit universe in K8\n\nSummary:\nSo this happens due to side effect of a code\nSo the components K8 universes never uses useVolumeHelper function field and it should never be invoked in first place\nBut what happens is UserTags component gets called during EDIT scenario even though it does not get displayed in K8 universe, it gets invoked, it calls useVolumeHelper which ultimately resets VOLUME SIZE in case of UPDATE operation\n\nThis diff ensures that volumeHelper function does not do any evaluation during EDIT mode and when universe is K8 based\n\nOriginal Commit: D35602/00fc7e6\n\nTest Plan:\nPlease refer to the video\n{F251348}\n\nReviewers: yshchetinin, jmak, anijhawan\n\nReviewed By: jmak\n\nSubscribers: yugaware\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35673","shortMessageHtmlLink":"[BACKPORT 2024.1][PLAT-13920]: Not able to increase the tserver volum…"}},{"before":"f97d0d3d7acef44e27f11a37ae87c70eb0f5b39e","after":"10f24bd178285d811bc5ba82cefae1c687ea0ed8","ref":"refs/heads/master","pushedAt":"2024-06-10T14:50:23.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"shahrooz1997","name":"Hamidreza Zare","path":"/shahrooz1997","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/23063104?s=80&v=4"},"commit":{"message":"[PLAT-13870] Support addition of databases in DB scoped DR config\n\nSummary:\nAllow users to add databases to the DR config after enabled DB scoped replication on YBA.\n\nUsers can enable this feature by enabling the yb.xcluster.db_scoped.enabled runtime flag.\n\nCurrently supports addition of databases without bootstrapping.\n\nExample of the setDatbases API:\n\n```\ncurl --location --request PUT 'localhost:9000/api/v1/customers/f33e3c9b-75ab-4c30-80ad-cba85646ea39/dr_configs/a4f7f7cb-0206-4385-82bc-8413f09b1fca/set_dbs' \\\n--header 'Content-Type: application/json' \\\n--header 'Accept: application/json' \\\n--header 'X-AUTH-YW-API-TOKEN: XYZ' \\\n--data '{\n \"databases\": [\n \"00004004000030008000000000000000\",\n \"00004005000030008000000000000000\"\n ]\n}'\n```\nThe schema of the table `xcluster_namespace_config` is modified to include the replication status:\n```\n Table \"public.xcluster_namespace_config\"\n Column | Type | Collation | Nullable | Default\n---------------------+-----------------------+-----------+----------+------------------------------\n config_uuid | uuid | | not null |\n source_namespace_id | character varying(64) | | not null |\n status | character varying(32) | | not null | 'Running'::character varying\nIndexes:\n \"pk_xcluster_namespace_config\" PRIMARY KEY, btree (config_uuid, source_namespace_id)\nCheck constraints:\n \"ck_xcluster_namespace_config_table_status\" CHECK (status::text = ANY (ARRAY['Validated'::character varying, 'Running'::character varying, 'Updating'::character varying, 'Bootstrapping'::character varying, 'Failed'::character varying]::text[]))\nForeign-key constraints:\n \"fk_xcluster_namespace_config_config_uuid\" FOREIGN KEY (config_uuid) REFERENCES xcluster_config(uuid) ON UPDATE CASCADE ON DELETE CASCADE\n```\n\nTest Plan:\nAdded UT\n\nCreate a source and target universe with db version >= 2.23.0.0-b247.\n\nCreate database `trial1` and `trial2` on both source and target universe\n\nAdd the following table to the `trial1` and `trial2` db on both source and target universe without any data in it.\n```\nCREATE TABLE house(\n ID INT PRIMARY KEY NOT NULL,\n LOCATION TEXT NOT NULL\n);\n```\n\nMake a call to the setDatabases endpoint with dbScoped boolean set as true.\nMake sure that the task succeeds.\n\nAdd data to the table on the source and check that it reflects on the target database.\n\nReviewers: #yba-api-review!, cwang, hzare, daniel, amindrov, sanketh\n\nReviewed By: cwang, hzare\n\nSubscribers: sanketh, jmak, amindrov, hzare, cwang, yugaware\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35498","shortMessageHtmlLink":"[PLAT-13870] Support addition of databases in DB scoped DR config"}},{"before":"afd31443886e2f55d0e7fbdd41a82962ef7c3a85","after":"f97d0d3d7acef44e27f11a37ae87c70eb0f5b39e","ref":"refs/heads/master","pushedAt":"2024-06-10T14:04:31.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"ddhodge","name":"Dwight Hodge","path":"/ddhodge","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79169168?s=80&v=4"},"commit":{"message":"[Docs] Allow 6sense domains in CSP (#22798)\n\n* Allow 6sense domains in CSP\r\n\r\n* Allow 6sense domains in CSP","shortMessageHtmlLink":"[Docs] Allow 6sense domains in CSP (#22798)"}},{"before":"e13f7b948aa76e231646a6d0d0782f72bee3386c","after":"4504580fd69c09ae95858b8963cf128c44e8e15a","ref":"refs/heads/2.20.4","pushedAt":"2024-06-10T13:26:39.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"suranjan","name":"suranjan kumar","path":"/suranjan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/189977?s=80&v=4"},"commit":{"message":"[BACKPORT 2.20.4][#22328] CDCSDK: Delete memory context after each GetChanges call\n\nSummary:\nOriginal commit: aa3116be688f5ec82c53c6c77210e870dd949395 / D34900\nThis diff ensures that the GetChanges RPC, upon its ScopeExit, will ensure deletion of its MemoryContext to prevent leaks caused by other RPCs setting their own MemoryContext without resetting it back to the old value.\n\nCDC uses Memory Context to allocate objects that are decoded from binary format. These memory contexts are thread-local objects. After each decode operation, this context is reset but not deleted to reduce allocation/deallocation.\n\nThis implies that each thread processing the GetChanges RPC would have one memory context saved in its thread-local storage. This is fine as long as some other RPCs don't reset this thread-local object without either deleting it or resetting it back to the old value. It seems there are other RPCs that could get executed by the same thread and they allocate a new memory context and set it to the same thread-local, leading to this leak.\n\nAs a good practice, each RPC/task that gets executed by a thread should do the following:\n\n```\nGet the old memory context\nCreate and Set the new memory context\nDelete its memory context\nReset the old on completion of its task\n```\n\nAs a safety precaution, we should also look for other instances where we are not setting the old memory context back to the thread_local.\nJira: DB-11236\n\nTest Plan: Manual Test\n\nReviewers: stiwary, amartsinchyk, sergei\n\nReviewed By: stiwary\n\nSubscribers: ycdcxcluster, ybase\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35716","shortMessageHtmlLink":"[BACKPORT 2.20.4][#22328] CDCSDK: Delete memory context after each Ge…"}},{"before":"d0a1fd77f41d304905ca223122145c9513fdbc66","after":"afd31443886e2f55d0e7fbdd41a82962ef7c3a85","ref":"refs/heads/master","pushedAt":"2024-06-10T10:27:24.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"Vars-07","name":"Shubham Varshney","path":"/Vars-07","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/19248012?s=80&v=4"},"commit":{"message":"[PLAT-14244] Set sshUser/Port from the overrides in case specified\n\nSummary:\nSet sshUser/Port from the overrides in case specified. This change was deprecated before\nrelease but given that YBM uses the same, we need to make the API backward compatible.\n\nTest Plan:\nCreated a provider specifying sshUserOverride/Port using the old format.\nEdited the provider - Verified provider edit is successful\n\nReviewers: amalyshev, #yba-api-review!\n\nReviewed By: amalyshev\n\nSubscribers: yugaware\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35619","shortMessageHtmlLink":"[PLAT-14244] Set sshUser/Port from the overrides in case specified"}},{"before":"cd4c95734a77573a27151ddba12481a38f2e6883","after":"d0a1fd77f41d304905ca223122145c9513fdbc66","ref":"refs/heads/master","pushedAt":"2024-06-10T10:24:14.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"Vars-07","name":"Shubham Varshney","path":"/Vars-07","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/19248012?s=80&v=4"},"commit":{"message":"[PLAT-13887][PLAT-14216] Configure user level node_exporter for new universes\n\nSummary:\nConfigure user level node_exporter for new universes.\nAlso, marks the permission for yb_home dir so that other users can traverse through it.\n\nTest Plan:\nCreated universe on YBA 2.18\nPatched the change.\nPerformed scale up - Verified that the new node is running node_exporter as system level systemd.\n\nCreated universe with the patch.\nVerified that new node is running node_exporter as user level.\n\nVerified the permissions of yb_home directory\n\nReviewers: amalyshev, anijhawan, #yba-api-review!\n\nReviewed By: amalyshev\n\nSubscribers: yugaware\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35632","shortMessageHtmlLink":"[PLAT-13887][PLAT-14216] Configure user level node_exporter for new u…"}},{"before":"3a0e897abc982679c08408ff696e5d342b2f6dee","after":"352020fb910d69a292e2738bd0bb1896095526b3","ref":"refs/heads/2024.1","pushedAt":"2024-06-10T08:52:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"asharma-yb","name":"Ayush Sharma","path":"/asharma-yb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/109268085?s=80&v=4"},"commit":{"message":"[BACKPORT 2024.1][#21688] Tests: Disable MiniCluster Backup tests\n\nSummary:\nOriginal commit: 05b4de205f0d512867d5392db7184fcc5b497f02/D33544\n\nDisable the Minicluster backup tests when we use YB Controller for backups.\nThis is because the `varz` endpoint in `MiniTabletServer` is not functional currently which causes the backups to fail.\n\nAlso don't start the YB Controller servers if the tests are disabled.\nJira: DB-10572\n\nTest Plan:\nVerified that these fail when we use YB Controller for backups. See [[ https://detective.dev.yugabyte.com/D33204 | here]].\nManually verified that these tests don't fail when run.\n```\nYB_DISABLE_MINICLUSTER_BACKUP_TESTS=1 YB_TEST_YB_CONTROLLER=1 ./yb_build.sh --cxx-test integration-tests_cql-backup-test --gtest_filter CqlBackupTest.TestBackupRestoreWithoutTSWebUI\n```\n\nReviewers: loginov\n\nReviewed By: loginov\n\nSubscribers: ybase, yql, asrivastava\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35684","shortMessageHtmlLink":"[BACKPORT 2024.1][#21688] Tests: Disable MiniCluster Backup tests"}},{"before":"a5b57b60a4549edebf4e596409792ffe802552fd","after":"3a0e897abc982679c08408ff696e5d342b2f6dee","ref":"refs/heads/2024.1","pushedAt":"2024-06-10T07:18:23.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"es1024","name":"Eric Sheng","path":"/es1024","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6742815?s=80&v=4"},"commit":{"message":"[2024.1][#22778] docdb: Turn off cdc_immediate_transaction_cleanup in release\n\nSummary: cdc_immediate_transaction_cleanup currently disables intent SST file cleanup when CDC is enabled due to a bug (#22227). This causes performance degradation even without backed up CDC streams due to CDC needing to scan a large amount of intent SST files. Disable cdc_immediate_transaction_cleanup in release to unblock CDC testing for 2024.1 release.\n\nTest Plan: Jenkins: rebase: 2024.1\n\nReviewers: rthallam\n\nReviewed By: rthallam\n\nSubscribers: rthallam, ybase\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35706","shortMessageHtmlLink":"[2024.1][#22778] docdb: Turn off cdc_immediate_transaction_cleanup in…"}},{"before":"25940f09ef9548723b8dfd2757ccf2b1f9f551d0","after":"cd4c95734a77573a27151ddba12481a38f2e6883","ref":"refs/heads/master","pushedAt":"2024-06-09T09:02:34.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"Vars-07","name":"Shubham Varshney","path":"/Vars-07","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/19248012?s=80&v=4"},"commit":{"message":"[PLAT-14099] Added logic for chrony/yugabyte module\n\nSummary: Added logic for chrony/yugabyte module\n\nTest Plan:\nitest pipeline\nTest script\n\n```\n#!/bin/bash\n\n######## Hello #########\necho \"hello run\"\necho \"hello world\"\n######## Hello #########\n\n######## ConfigureChrony #########\n# Enable debug mode and immediate exit on error\nset -ex\n\n# Adding servers to chrony.conf\n\necho 'server 0.pool.ntp.org prefer iburst minpoll 4 maxpoll 4' >> /etc/chrony.conf\n\necho 'server 1.pool.ntp.org prefer iburst minpoll 4 maxpoll 4' >> /etc/chrony.conf\n\n######## ConfigureChrony #########\n\n######## CreateYugabyteUser #########\n# Enable debug mode and immediate exit on error\nset -ex\n\n# Creating the yb_user\nuseradd -u 994 -s /bin/bash --create-home --home-dir /home/yugabyte yugabyte\n\n# Set the password for the new user\necho 'yugabyte:password' | chpasswd\n\n# Add yugabyte user to systemd-journal group\nusermod -aG systemd-journal yugabyte\n\n# Check SELinux status\nsestatus\n\n# Get SELinux status and store it in a variable\nSELINUX_STATUS=$(sestatus | grep 'SELinux status' | awk '{print $3}')\n\nif [ \"$SELINUX_STATUS\" == \"enabled\" ]; then\n # Configuring the correct SELinux context\n chcon -R -t ssh_home_t /home/yugabyte\nfi\n\n# Configure the public key\nif [ -z ]; then\n CURRENT_USER=$(whoami)\n PUBKEY_FILE=\"/home/$CURRENT_USER/.ssh/id_rsa.pub\"\n\n su - yugabyte mkdir -p /home/yugabyte/.ssh\n su - yugabyte chmod 700 /home/yugabyte/.ssh\n\n PUBKEY_CONTENT=$(cat \"$PUBKEY_FILE\")\n if [ -n \"$PUBKEY_CONTENT\" ]; then\n echo \"$PUBKEY_CONTENT\" | su - yugabyte tee -a /home/yugabyte/.ssh/authorized_keys > /dev/null\n\n # Set the appropriate permissions for the authorized_keys file\n su - yugabyte chmod 400 /home/yugabyte/.ssh/authorized_keys\n chown -R yugabyte:yugabyte /home/yugabyte/.ssh\n else\n echo \"The public key file is empty: $PUBKEY_FILE\"\n exit 1\n fi\nfi\n\n# Enable linger for yb_user\nsu - yugabyte loginctl enable-linger yugabyte\nsu - yugabyte export XDG_RUNTIME_DIR=/run/user/$(id -u yugabyte)\n######## CreateYugabyteUser #########\n```\n\nPre check script\n\n```\n#!/bin/bash\n\n######## Hello #########\necho \"hello precheck\"\necho \"hello world\"\n######## Hello #########\n\n######## ConfigureChrony #########\nchronyc makestep\n\n# Check the exit status of the command\nif [ $? -eq 0 ]; then\n echo \"System clock synchronized\"\nelse\n echo \"Error: chronyc makestep command failed\"\n exit 1\nfi\n######## ConfigureChrony #########\n\n######## CreateYugabyteUser #########\n\n# Check if the yugabyte user exists\nif id yugabyte &>/dev/null; then\n echo \"User yugabyte exists\"\nelse\n echo \"User yugabyte does not exist\"\n exit 1\nfi\n\n# Check the correct permissions for yb_home_dir\nif [ -d /home/yugabyte ]; then\n owner=$(stat -c \"%U\" \"/home/yugabyte\")\n group=$(stat -c \"%G\" /home/yugabyte\")\n permissions=$(stat -c \"%a\" \"/home/yugabyte\")\n\n if [ \"$owner\" != \"yugabyte\" ]; then\n echo \"Ownership of /home/yugabyte is incorrect. Expected owner: yugabyte, Found: $owner\"\n exit 1\n fi\n\n if [ \"$group\" != \"yugabyte\" ]; then\n echo \"Group ownership of /home/yugabyte is incorrect. Expected group: yugabyte, Found: $group\"\n exit 1\n fi\n\n if [ \"$permissions\" -lt 711 ]; then\n echo \"Permissions of /home/yugabyte are too permissive. Expected: 711 or greater, Found: $permissions\"\n exit 1\n fi\n\n echo \"/home/yugabyte has the correct ownership and acceptable permissions\"\nelse\n echo \"/home/yugabyte does not exist\"\n exit 1\nfi\n######## CreateYugabyteUser #########\n```\n\nReviewers: anijhawan, nbhatia\n\nReviewed By: anijhawan\n\nSubscribers: yugaware\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35508","shortMessageHtmlLink":"[PLAT-14099] Added logic for chrony/yugabyte module"}},{"before":"863ffadc92cd0d30a9f5d817864522c230068400","after":"599a763ae8a4f734c30115713d6c065e58fdabcb","ref":"refs/heads/posriniv/update-dbs","pushedAt":"2024-06-08T19:53:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"posriniv","name":"Srinivas Pothuraju","path":"/posriniv","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/48309285?s=80&v=4"},"commit":{"message":"address final review comments","shortMessageHtmlLink":"address final review comments"}},{"before":"ac59ff5bb829a4912b2d68730b9031ec6de78cae","after":"25940f09ef9548723b8dfd2757ccf2b1f9f551d0","ref":"refs/heads/master","pushedAt":"2024-06-08T15:43:26.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"ddhodge","name":"Dwight Hodge","path":"/ddhodge","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79169168?s=80&v=4"},"commit":{"message":"[doc][yba] Fix for manual on prem (#22639)\n\n* Fix for manual on prem\r\n\r\n* revert\r\n\r\n* stable\r\n\r\n* edits for style\r\n\r\n* minor fixes to RN\r\n\r\n* minor edit\r\n\r\n* format\r\n\r\n* minor edit","shortMessageHtmlLink":"[doc][yba] Fix for manual on prem (#22639)"}},{"before":"e9e806b2f49123eb5334d8d8b43f4f42037c019d","after":"ac59ff5bb829a4912b2d68730b9031ec6de78cae","ref":"refs/heads/master","pushedAt":"2024-06-08T04:37:07.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"d-uspenskiy","name":"Dmitry Uspenskiy","path":"/d-uspenskiy","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/47734295?s=80&v=4"},"commit":{"message":"[#20797] YSQL: Fix SameTempTableCreationWithResponseCache/ResponseCacheInvalidationOnConnectionWithTempTableClosure unit tests\n\nSummary:\nThe `SameTempTableCreationWithResponseCache` and `ResponseCacheInvalidationOnConnectionWithTempTableClosure` unit tests require client connection to be fully closed by postgres (i.e. process started for connection processing must be finished). Both tests use sleep for this purpose. But there is no guaranty that process will be finished within specified time.\n\nCurrent diff substitutes the sleep with using of the `ClientConnectionsCountFetcher` helper class. This class is able to wait for client connection process termination by using info from the postgres' webserver proxy.\n\n**Note**: The diff moves some utility functions for json processing into `json_util.h` file. Local versions of same functions in several files are substituted with these new functions.\n\nTest Plan:\nJenkins\n\n```\n./yb_build.sh --gtest_filter PgCatalogPerfTest.SameTempTableCreationWithResponseCache -n 20\n./yb_build.sh --gtest_filter PgCatalogPerfTest.ResponseCacheInvalidationOnConnectionWithTempTableClosure -n 20\n```\n\nReviewers: fizaa, myang, kfranz\n\nReviewed By: myang\n\nSubscribers: ybase, yql\n\nTags: #jenkins-ready\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35565","shortMessageHtmlLink":"[#20797] YSQL: Fix SameTempTableCreationWithResponseCache/ResponseCac…"}},{"before":"1f0aec226abcd76eb13ba4243f4a57857db05f4e","after":"e9e806b2f49123eb5334d8d8b43f4f42037c019d","ref":"refs/heads/master","pushedAt":"2024-06-07T21:51:44.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"pao214","name":"Bvsk Patnaik","path":"/pao214","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/16426043?s=80&v=4"},"commit":{"message":"[#22615] YSQL: Incorrect seek key in prefix-based backward scan\n\nSummary:\n### Context\n\nHybridScanChoices adds a kGroupEnd marker at the end of the DocKey. ScanChoices adds this marker at the end of the prefix in a prefix-based scan. This is acceptable in a forward scan since we wish to seek to the smallest key >= the scan target. However, in a backward scan, we wish to seek to the largest possible key <= the scan target. kGroupEnd marker is fighting against us in this case. We append kHighest (representing +Inf) to seek to the largest key but that happens after the kGroupEnd marker is appended. This is undesirable.\n\n### Fix\n\nRemove the kGroupEnd marker during the backward prefix-based seek scan (from a copy of current scan target).\n\n### Impact\n\n1. Uses a strict prefix-based scan.\n\nFull key scans are exempt from this issue since the kGroupEnd is not added on a key column.\n\n2. Is a backward scan.\n\nAs explained in the context section, kGroupEnd is fine when scanning forward since it is a small value.\n\n3. Has IN clauses.\n\nWithout multiple options, we may not be changing the scan target based on the user provided input more than once. Seeks still happen, however, we do not append a kGroupEnd marker on new scan targets obtained directly from scanning the database.\n\n### Scan Target Debugging\n\n1. Scan Target in HybridScanChoices is not always followed by a kGroupEnd marker. This marker is used to end hash keys group and range keys group. When converting a DocKey to a human-readable string, we need this end of the keys marker. This change appends this marker so we do not get corruption errors when debugging the doc keys.\n\n2. Propagate the allow_special flag when decoding keys so that special keys such as +Inf can be debug dumped appropriately.\nJira: DB-11524\n\nTest Plan:\nJenkins\n\n./yb_build.sh --java-test TestPgRegressDistinctPushdown\n\nAdded a test case that\n\n1. Uses a prefix-based scan.\n2. Is descending.\n3. Has multiple Option Ranges (IN clause).\n\nBackport-through: 2.18\n\nReviewers: tnayak, telgersma, smishra\n\nReviewed By: tnayak\n\nSubscribers: yql, ybase\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35497","shortMessageHtmlLink":"[#22615] YSQL: Incorrect seek key in prefix-based backward scan"}},{"before":"a80a224b40011a8e87928a3f21b66c375d768c7f","after":"1f0aec226abcd76eb13ba4243f4a57857db05f4e","ref":"refs/heads/master","pushedAt":"2024-06-07T21:46:27.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"aishwarya24","name":"Aishwarya Chakravarthy ","path":"/aishwarya24","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5341399?s=80&v=4"},"commit":{"message":"[docs] sorted releases table by date (#22777)\n\n* sorted releases\r\n\r\n* some improvements","shortMessageHtmlLink":"[docs] sorted releases table by date (#22777)"}},{"before":"959513677c481a3f29dbc33bb28ab9bd23ed4cf2","after":"a80a224b40011a8e87928a3f21b66c375d768c7f","ref":"refs/heads/master","pushedAt":"2024-06-07T20:27:01.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"rajmaddy89","name":"Rajagopalan Madhavan","path":"/rajmaddy89","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/10095310?s=80&v=4"},"commit":{"message":"[PLAT-14284]: Modify API Url in common components and integrate with YBA\n\nSummary:\n1. Modify API Url query param from customerUuid to customer_uuid in common components and integrate with YBA\n2. In triubleshoot-universe.tsx page, pass apiUrl as a param to the API in common component\n3. Split 1 component into 2 for better readability\n\nTest Plan: Not changes in behavior, same as previous time, just minor improvements\n\nReviewers: jmak, amalyshev\n\nReviewed By: jmak\n\nSubscribers: yugaware\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35703","shortMessageHtmlLink":"[PLAT-14284]: Modify API Url in common components and integrate with YBA"}},{"before":"2ce3383230c44995a1d82e2349e0bf0d3efba681","after":"959513677c481a3f29dbc33bb28ab9bd23ed4cf2","ref":"refs/heads/master","pushedAt":"2024-06-07T20:21:03.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"ddhodge","name":"Dwight Hodge","path":"/ddhodge","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79169168?s=80&v=4"},"commit":{"message":"[DOC-388] updated CBO flags (#22765)\n\n* updated flags\r\n\r\n* fixed links\r\n\r\n* Enhanced Postgres Compatibility Mode\r\n\r\n* more packed row caveats\r\n\r\n* Apply suggestions from code review\r\n\r\n* Edit\r\n\r\n* v2.21 fixes\r\n\r\n* fix Versions menu\r\n\r\n* review comment\r\n\r\n---------\r\n\r\nCo-authored-by: Dwight Hodge \r\nCo-authored-by: Dwight Hodge <79169168+ddhodge@users.noreply.github.com>","shortMessageHtmlLink":"[DOC-388] updated CBO flags (#22765)"}},{"before":"fedd72540fbfee6ea0ea95453717bbf4506fe4cb","after":"2ce3383230c44995a1d82e2349e0bf0d3efba681","ref":"refs/heads/master","pushedAt":"2024-06-07T20:12:22.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"ddhodge","name":"Dwight Hodge","path":"/ddhodge","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/79169168?s=80&v=4"},"commit":{"message":"[docs] OS support pages update for v2.20, v2024.1, v2.21. (#22774)\n\n* some fixes\r\n\r\n* added an entry\r\n\r\n* added unsupported entries\r\n\r\n* edits for clarity\r\n\r\n* minor edits\r\n\r\n* minor edit\r\n\r\n* minor edit\r\n\r\n* version fix\r\n\r\n---------\r\n\r\nCo-authored-by: Dwight Hodge ","shortMessageHtmlLink":"[docs] OS support pages update for v2.20, v2024.1, v2.21. (#22774)"}},{"before":"387775641c90a9fbc00b3d16ac89b9befecba2e0","after":"fedd72540fbfee6ea0ea95453717bbf4506fe4cb","ref":"refs/heads/master","pushedAt":"2024-06-07T19:06:24.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"artem-mindrov","name":"Artem","path":"/artem-mindrov","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1575475?s=80&v=4"},"commit":{"message":"[PLAT-9735][xCluster] show errors exposed by GetReplicationStatus\n\nSummary: expose short descriptions of GetReplicationStatus errors via XClusterTableConfig in the GET XClusterConfig response\n\nTest Plan:\nTest with manually populated errors in the RPC response in `XClusterConfigTaskBase#setReplicationStatus`:\n\n```\n List replicationErrors =\n new ArrayList<>(replicationStatus.getErrorsList());\n replicationErrors.add(\n ReplicationStatusErrorPB.newBuilder()\n .setError(REPLICATION_AUTO_FLAG_CONFIG_VERSION_MISMATCH)\n .setErrorDetail(\"test\")\n .build());\n replicationErrors.add(\n ReplicationStatusErrorPB.newBuilder()\n .setError(REPLICATION_SCHEMA_MISMATCH)\n .setErrorDetail(\"test1\")\n .build());\n replicationErrors.add(\n ReplicationStatusErrorPB.newBuilder()\n .setError(REPLICATION_MISSING_TABLE)\n .setErrorDetail(\"test2\")\n .build());\n```\n\nXCluster config overview page shows:\n{F251165}\nXCluster config details page:\n{F251167}\nRestart replication modal:\n{F251168}\n\nReviewers: hzare, cwang, vbansal, spothuraju, jmak, #yba-api-review\n\nReviewed By: hzare, cwang, jmak, #yba-api-review\n\nSubscribers: sanketh, yugaware\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35571","shortMessageHtmlLink":"[PLAT-9735][xCluster] show errors exposed by GetReplicationStatus"}},{"before":"9bb032f1f64e6314bac675b7a236ae0597956712","after":"387775641c90a9fbc00b3d16ac89b9befecba2e0","ref":"refs/heads/master","pushedAt":"2024-06-07T18:16:18.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"Deepti-yb","name":"Deepti Kumar","path":"/Deepti-yb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/108267959?s=80&v=4"},"commit":{"message":"[PLAT-14195]Add GFlag groups field in Specific GFlags for create universe workflow\n\nSummary:\nAdding `gflagGroups` to `SpecificGFlags` that'll allow users to set groups of GFlags managed\nby YBA\n\nAddition to `UserIntent`\n```\n\"specificGFlags\": {\n \"inheritFromPrimary\": false,\n \"gflagGroups\": [\n \"ENHANCED_POSTGRES_COMPATIBILITY\"\n ],\n \"perProcessFlags\": {\n \"value\": {\n \"MASTER\": {},\n \"TSERVER\": {}\n }\n },\n \"perAZ\": {}\n }\n```\n\nIf a user tries to manually edit the gflags when the groups are added, the entries are overridden with values present in YBA.\n\nTest Plan:\n # Universe creation with correct group name\n\n # Universe creation with incorrect group name\n\n # GFlag groups with audit logs (Both have entries to `ysql_pg_conf_csv`) - Needs to be tested\n\n # User entries to `ysql_pg_conf_csv` a) on the same fields as the group b) different fields\n\n # Apply the group to both primary and read replica clusters if present in primary cluster user intent regardless of `inheritFromPrimary` field\n\nReviewers: #yba-api-review, sanketh, sneelakantan\n\nReviewed By: #yba-api-review, sneelakantan\n\nSubscribers: yugaware\n\nDifferential Revision: https://phorge.dev.yugabyte.com/D35659","shortMessageHtmlLink":"[PLAT-14195]Add GFlag groups field in Specific GFlags for create univ…"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEYdQKpwA","startCursor":null,"endCursor":null}},"title":"Activity · yugabyte/yugabyte-db"}