realaravinth/bench-forgejo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
bench-forgejo/vendor/github.com/ethantkoenig/rupture
History
6543 30ce3731a1
Vendor Update Go Libs (#13444) 
* denisenkom/go-mssqldb untagged -> v0.9.0

* github.com/editorconfig/editorconfig-core-go v2.3.7 -> v2.3.8

* github.com/go-testfixtures/testfixtures v3.4.0 -> v3.4.1

* github.com/mholt/archiver v3.3.2 -> v3.5.0

* github.com/olivere/elastic v7.0.20 -> v7.0.21

* github.com/urfave/cli v1.22.4 -> v1.22.5

* github.com/xanzy/go-gitlab v0.38.1 -> v0.39.0

* github.com/yuin/goldmark-meta untagged -> v1.0.0

* github.com/ethantkoenig/rupture 0a76f03a811a -> c3b3b810dc77

* github.com/jaytaylor/html2text 8fb95d837f7d -> 3577fbdbcff7

* github.com/kballard/go-shellquote cd60e84ee657 -> 95032a82bc51

* github.com/msteinert/pam 02ccfbfaf0cc -> 913b8f8cdf8b

* github.com/unknwon/paginater 7748a72e0141 -> 042474bd0eae

* CI.restart()

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2020-11-06 13:41:42 -05:00
..
.gitignore Use Go1.11 module (#5743) 2019-03-27 19:15:23 +08:00
.travis.yml Vendor Update Go Libs (#13444) 2020-11-06 13:41:42 -05:00
flushing_batch.go Reduce repo indexer disk usage (#3452) 2018-02-05 20:29:17 +02:00
Gopkg.lock Use Go1.11 module (#5743) 2019-03-27 19:15:23 +08:00
Gopkg.toml Use Go1.11 module (#5743) 2019-03-27 19:15:23 +08:00
LICENSE Reduce repo indexer disk usage (#3452) 2018-02-05 20:29:17 +02:00
metadata.go Reduce repo indexer disk usage (#3452) 2018-02-05 20:29:17 +02:00
README.md Vendor Update Go Libs (#13444) 2020-11-06 13:41:42 -05:00
sharded_index.go Reduce repo indexer disk usage (#3452) 2018-02-05 20:29:17 +02:00

README.md

rupture

Build Status GoDoc Go Report Card

An explosive companion to the bleve indexing library

Features

rupture includes the following additions to bleve:

  • Flushing batches: Batches of operation which automatically flush to the underlying bleve index.
  • Sharded indices: An index-like abstraction built on top of several underlying indices. Sharded indices provide lower write latencies for indices with large amounts of data.
  • Index metadata: Track index version for easily managing migrations and schema changes.