mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-10-09 20:37:52 +00:00
No description
28b9d6d7fc
UpdateEvery can change every key, and I think it strongly suggests no reasonable expectation of repeated access to a previously-accessed key, but also it can change the containers and replace them. We were avoiding caching mapped containers in some but not all cases, and that was causing segfaults. But really, the *problem* is that the remap operation wasn't clearing (or updating) the cache. Cleaning that up allows us to take advantage of the caching performance advantage even when working with read-only/mapped bitmaps. The only way to hit this: * Have mmapped containers to begin with. * Do reads so those containers get frozen. * Access, either reading or writing, a specific container with key K. * Snapshot, so the bitmap gets its containers replaced. * Remember, they have to be frozen -- if they aren't frozen, we'll update the containers in place. * Now have GC run so it actually unmaps the data. * Now try to write to the container with key K *before reading or writing any other key*. You have to get through the whole snapshot and GC process without any other reads or writes. * You get the cached value. You try to use it. You explode. The sliceContainers code was also setting lastKey to 0 in some cases, but also setting lastContainer to nil, so this wouldn't have caused problems, but just to be careful, I've standardized on ^uint64(0) for everything. |
||
|---|---|---|
| .circleci | ||
| .github | ||
| api/client | ||
| boltdb | ||
| cmd | ||
| ctl | ||
| docs | ||
| encoding/proto | ||
| enterprise | ||
| extensions | ||
| gcnotify | ||
| gopsutil | ||
| gossip | ||
| http | ||
| internal | ||
| logger | ||
| lru | ||
| mock | ||
| pql | ||
| prometheus | ||
| proto | ||
| roaring | ||
| server | ||
| shardwidth | ||
| stats | ||
| statsd | ||
| syswrap | ||
| test | ||
| testdata | ||
| toml | ||
| tracing | ||
| .gitignore | ||
| .golangci.yml | ||
| api.go | ||
| api_test.go | ||
| apimethod_string.go | ||
| attr.go | ||
| attr_test.go | ||
| broadcast.go | ||
| cache.go | ||
| cache_test.go | ||
| CHANGELOG.md | ||
| client.go | ||
| cluster.go | ||
| cluster_internal_test.go | ||
| cmd.go | ||
| CONTRIBUTING.md | ||
| diagnostics.go | ||
| diagnostics_internal_test.go | ||
| doc.go | ||
| Dockerfile | ||
| Dockerfile-clustertests | ||
| event.go | ||
| executor.go | ||
| executor_internal_test.go | ||
| executor_test.go | ||
| extension.go | ||
| field.go | ||
| field_internal_test.go | ||
| field_test.go | ||
| fragment.go | ||
| fragment_internal_test.go | ||
| gc.go | ||
| gendebug_test.go | ||
| generation.go | ||
| generation_debug.go | ||
| generation_nodebug.go | ||
| generation_test.go | ||
| go.mod | ||
| go.sum | ||
| handler.go | ||
| holder.go | ||
| holder_internal_test.go | ||
| holder_test.go | ||
| index.go | ||
| index_internal_test.go | ||
| index_test.go | ||
| iterator.go | ||
| iterator_internal_test.go | ||
| LICENSE | ||
| license.exceptions | ||
| Makefile | ||
| mmap_test.go | ||
| NOTES | ||
| NOTICE | ||
| pilosa.go | ||
| pilosa_internal_test.go | ||
| pilosa_test.go | ||
| README.md | ||
| row.go | ||
| row_test.go | ||
| server.go | ||
| server_internal_test.go | ||
| snapshotqueue.go | ||
| time.go | ||
| time_internal_test.go | ||
| translate.go | ||
| translator_test.go | ||
| uri.go | ||
| uri_internal_test.go | ||
| utils_internal_test.go | ||
| version.go | ||
| view.go | ||
| view_internal_test.go | ||
An open source, distributed bitmap index.
Want to contribute? One of the easiest ways is to tell us how you're using (or want to use) Pilosa. We learn from every discussion!
Docs
See our Documentation for information about installing and working with Pilosa.
Getting Started
-
Start Pilosa with the default configuration:
pilosa serverand verify that it's running:
curl localhost:10101/nodes -
Follow along with the Sample Project to get a better understanding of Pilosa's capabilities.
Data Model
Check out how the Pilosa Data Model works.
Query Language
You can interact with Pilosa directly in the console using the Pilosa Query Language (PQL).
Client Libraries
There are supported libraries for the following languages:
Licenses
The core Pilosa code base and all default builds (referred to as Pilosa Community Edition) are licensed completely under the Apache License, Version 2.0.
If you build Pilosa with the enterprise build tag (Pilosa Enterprise Edition), then that build will include features licensed under the GNU Affero General
Public License (AGPL). Enterprise code is located entirely in the github.com/pilosa/pilosa/enterprise
directory. See github.com/pilosa/pilosa/NOTICE and
github.com/pilosa/pilosa/LICENSE for more information about Pilosa licenses.
Get Support
There are several channels available for you to reach out to us for support.
Contributing
Pilosa is an open source project. Please see our Contributing Guide for information about how to get involved.