1
0
Fork 0
forgejo/modules/indexer/code
dark-angel 00370f17a4
[gitea] fix: Elasticsearch: Request Entity Too Large #28117 (#29062)
Fix for gitea putting everything into one request without batching and
sending it to Elasticsearch for indexing as issued in #28117

This issue occured in large repositories while Gitea tries to
index the code using ElasticSearch.

I've applied necessary changes that takes batch length from below config
(app.ini)
```
[queue.code_indexer]
BATCH_LENGTH=<length_int>
```
and batches all requests to Elasticsearch in chunks as configured in the
above config

(cherry picked from commit 5c0fc9087211f01375f208d679a1e6de0685320c)
2024-02-10 10:53:43 +01:00
..
bleve Preserve BOM in web editor (#28935) 2024-01-27 18:02:51 +00:00
elasticsearch [gitea] fix: Elasticsearch: Request Entity Too Large #28117 (#29062) 2024-02-10 10:53:43 +01:00
internal Refactor indexer (#25174) 2023-06-23 12:37:56 +00:00
git.go Abstract hash function usage (#28138) 2023-12-13 21:02:00 +00:00
indexer.go Penultimate round of db.DefaultContext refactor (#27414) 2023-10-11 04:24:07 +00:00
indexer_test.go Replace assert.Fail with assert.FailNow (#27578) 2023-10-11 11:02:24 +00:00
search.go Add option to disable ambiguous unicode characters detection (#28454) 2023-12-17 14:38:54 +00:00