PPascal Bleserchore(graph): use metrics tools introduced in 8821053ff8
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
use plain pkg module Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 1 年前 | |
feat(search): per-field case-insensitive search via _lowercase siblings Keyword and path fields always index their case-preserved base and, when CaseInsensitive is set, an additional <field>_lowercase sibling used only for matching. The KQL lowering marks a restriction case-insensitive; each backend searches the sibling and lowercases the query value the same way the sibling is precomputed at index time (Go strings.ToLower on both sides, so non-ASCII stays consistent). Search always returns the case-preserved base, so the sibling never has to be read back. In bleve it is indexed but not stored, kept out of _all, and without doc values. In OpenSearch it deliberately stays in _source: excluding it would make every update-by-query script rebuild all siblings from the document via painless toLowerCase, which lowercases differently than Go and would drift from the query side. Keeping it in _source avoids that, and a lowercased copy of a name or path is negligible disk in a cluster. The OpenSearch move script keeps the base and its sibling in sync by swapping the moved prefix in Path_lowercase and setting Name_lowercase from Go-lowercased params, so case-insensitive search still finds a file after it moves (previously the sibling went stale). bleve re-indexes the whole document on move/delete/restore, so its siblings stay fresh for free. This also repairs OpenSearch path search (the query value was no longer folded to lowercase, so path:<Foo> returned nothing) and makes bleve path queries match a folder and its descendants like OpenSearch's path_hierarchy. The Path base stays case-preserved so the move/delete descendant update (an exact TermQuery on Path) matches mixed-case folders. | 6 天前 | |
use plain pkg module Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 1 年前 | |
Use the opencloud reva from now on | 1 年前 | |
use plain pkg module Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 1 年前 | |
fix(runtime): keep the usage block for flag errors only | 1 个月前 | |
chore: replace interface with any | 4 个月前 | |
refactor(search): cleanup for review | 1 年前 | |
use plain pkg module Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 1 年前 | |
chore: replace interface with any | 4 个月前 | |
enhancement: make collaboration mention functionality public | 2 个月前 | |
Rebrand pkg | 1 年前 | |
make firstNRunes more readable Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 11 个月前 | |
use plain pkg module Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 1 年前 | |
Switch to opencloud-eu fork of libre-graph-api-go | 1 年前 | |
refactor(kql): move parse/validation errors into pkg/kql The KQL parser produced its own validation errors but imported them from the search service's query package. Move them into pkg/kql and let the search backend consume kql.IsValidationError, so the parser stops depending on a service package. | 6 天前 | |
fix: translations for activities and others This fixes the server-side translations for "activties" and e.g. the default space description. We need to bump "leonelquinteros/gotext" to latest master for that as even the latest release still contains and issue that cause `go vet` to complain about non-constant format strings. Fixes: #2833, #2835 | 3 个月前 | |
use plain pkg module Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 1 年前 | |
chore: replace interface with any | 4 个月前 | |
fix: markdown links formatting (#2143) | 7 个月前 | |
chore(graph): use metrics tools introduced in 8821053ff8 * introduce a fix in the metrics tools introduced with 8821053ff8 in order to deal with a struct that has fields that are not exported (as is the case here) * introduce a func in the toplevel metrics package that registers a single metric, as that needs to be done explicitly for unexported ones * in the graph service, use RegisterAll and BuildInfo from the toplevel metrics package, as introduced with 8821053ff8 | 5 天前 | |
fix(middleware): reject empty OIDC providers safely | 8 天前 | |
add tls support for all nats connections Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 2 个月前 | |
fix: distinguish between go-micro and ocis connections to registry | 11 个月前 | |
chore: replace interface with any | 4 个月前 | |
fix: distinguish between go-micro and ocis connections to registry | 11 个月前 | |
Set new defaults for caches and stores See https://github.com/opencloud-eu/opencloud/issues/2681 for more details. | 4 个月前 | |
update comments Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 11 个月前 | |
chore(debug): remove leftover commented-out probeHandler | 3 个月前 | |
chore: adjust for changed automemlimit API | 11 天前 | |
fix(graph-metadata): lazy cs3 metadata storage initialization | 1 年前 | |
use plain pkg module Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 1 年前 | |
chore: replace interface with any | 4 个月前 | |
use plain pkg module Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 1 年前 | |
fix: enhance resource creation with detailed process information (#1978) Co-authored-by: Stavros Kois <s.kois@outlook.com> | 8 个月前 | |
chore: bump reva to 2.49.0 | 12 天前 | |
feat(posixfs): #3182 add basepath option in the "posixfs scan" command * add support for specifying a basepath using -p when running the posixfs scan command, to indicate a directory under which to start scanning, or a singular file to scan, as opposed to scanning from the storage root directory as is the default behaviour * implements https://github.com/opencloud-eu/opencloud/issues/3182 | 1 个月前 | |
use plain pkg module Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de> | 1 年前 | |
build: Modify mockery config to work with v3 Maintaining the positioning of the files from v2 to reduce cognitive load. Indentation of yaml files now matches `.editorconfig`. All mock files regenerated. Added empty `{}` following convention from `mockery init` etc. Removed directory specification where it would already match. | 1 年前 | |
Makefile: remove unneeded recursion.mk The MAKE_DEPTH variable is not used anywhere anymore. | 1 年前 |