)]}'
{
  "commit": "fa06a731b989f5bd81edca5afb00e767cebad827",
  "tree": "28d65a89e8fc05ad64ded40f5ffdbecd8334ec30",
  "parents": [
    "349b5f07231f96bffe1acb6c24c1749d5442217c"
  ],
  "author": {
    "name": "Jacek Centkowski",
    "email": "geminica.programs@gmail.com",
    "time": "Fri Feb 04 12:39:34 2022 +0100"
  },
  "committer": {
    "name": "Jacek Centkowski",
    "email": "geminica.programs@gmail.com",
    "time": "Wed Mar 09 17:11:31 2022 +0100"
  },
  "message": "Limit \u0027maxPages\u0027 to \u0027100\u0027 by deafult\n\nIt seems that Lucene implementation has to scan through the large amount\nof data in order to reach distant page and results in substantial amount\nof memory being used (results in OOO exception). In order to mitigate it\nlimit \u0027maxPages\u0027 to `100\u0027 if no value is set. Note that one can still\nset it to unlimited by changing the value to \u00270\u0027.\n\nRelease-Notes: Limit \u0027index.maxPages\u0027 to \u0027100\u0027 by default\nBug: Issue 15563\nChange-Id: I5a9a50b755d9814fcdd47910702b8ec80b2a029f\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "10baed2750e999f932bed5c12ea14dbfd5abfc17",
      "old_mode": 33188,
      "old_path": "Documentation/config-gerrit.txt",
      "new_id": "31bb6be4806a6cd5b661a300eaa5580a391e4f64",
      "new_mode": 33188,
      "new_path": "Documentation/config-gerrit.txt"
    },
    {
      "type": "modify",
      "old_id": "29b8ea657ef1dd745905a6f503e8e8d88bb7b398",
      "old_mode": 33188,
      "old_path": "java/com/google/gerrit/index/IndexConfig.java",
      "new_id": "c93c5393c265179b9a60d284cdbfc0ca37fb57a3",
      "new_mode": 33188,
      "new_path": "java/com/google/gerrit/index/IndexConfig.java"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "6d3fcb7024f8cbc3244fc9840e9ae1daecd4e708",
      "new_mode": 33188,
      "new_path": "javatests/com/google/gerrit/index/IndexConfigTest.java"
    }
  ]
}