This module allows OpenResty applications to use the LMDB (Lightning Memory-Mapped Database) inside the Nginx worker process. It has two parts, a core module built into Nginx that controls the life cycle of the database environment, and a FFI based Lua binding for interacting with the module to access/change data.
syntax: value, err = lmdb.get(key, db?)
context: any context except init_by_lua*
Gets the value corresponding to key from LMDB database db. If db is omitted,
it defaults to "_default".
If the key does not exist, nil will be returned.
In case of error, nil and a string describing the error will be returned instead.
syntax: ok, err = lmdb.set(key, value, db?)
context: any context except init_by_lua*
Sets the value corresponding to key to value inside LMDB database db. If db is omitted,
it defaults to "_default".
Setting a key's value to nil will remove that key from the corresponding database.
In case of error, nil and a string describing the error will be returned instead.
syntax: status, err = lmdb.get_env_info()
context: any context except init_by_lua*
Get the LMDB database runtime information. status table struct as below.
{
"page_size": 4096,
"max_readers":126,
"num_readers": 1,
"allocated_pages": 2,
"in_use_pages": 0,
"entries": 0,
"map_size": 10485760 # in bytes
}
In case of error, nil and a string describing the error will be returned instead.
syntax: ok, err = lmdb.db_drop(delele?, db?)
context: any context except init_by_lua*
Clears the contents of database db. If delete is true, then the database handle is also dropped.
In case of error, nil and a string describing the error will be returned instead.
syntax: for key, value in lmdb.prefix(prefix) do
context: any context
Returns all key and their associated value for keys starting with prefix.
For example, if the database contains:
key1: value1
key11: value11
key2: value2
Then a call of lmdb.prefix("key") will yield key1, key11 and key2 respectively.
In case of errors while fetching from LMDB, key will be nil and value will be
a string describing the error. The caller must anticipate this happening and check each return
value carefully before consuming.
Warning on transaction safety: Since the number of keys that could potentially
be returned with this method could be very large, this method does not return all
results inside a single transaction as this will be very expensive. Instead, this
method gets keys from LMDB in batches using different read transaction. Therefore, it
is possible that the database content has changed between batches. We may introduce a
mechanism for detecting this case in the future, but for now there is a small opportunity
for this to happen and you should guard your application for concurrent writes if this
is a huge concern. This function makes best effort to detect when database content
definitely changed between iterations, in this case nil, "DB content changed while iterating"
will be returned from the iterator.
syntax: txn:reset()
context: any context
Resets a transaction object. Removes all existing transactions and results (if any) from the object but
keeps the table's capacity. After this call the transaction can be reused as if it was a new transaction
returned by transaction.begin().
syntax: txn:get(key, db?)
context: any context
Appends a get operation in the transactions table. If db is omitted,
it defaults to "_default". The output table contains the following
fields:
value: Value forkey, ornilifkeyis not found
syntax: txn:set(key, value, db?)
context: any context
Appends a set operation in the transactions table. If db is omitted,
it defaults to "_default". The output able contains the following
fields:
result: Alwaystruefor successful transaction commits
syntax: txn:db_open(create, db?)
context: any context
Appends a db_open operation in the transactions table. If db is omitted,
it defaults to "_default". This operation does not return anything
in case of successful transaction commits.
syntax: txn:db_drop(delete, db?)
context: any context
Appends a db_drop operation in the transactions table. If db is omitted,
it defaults to "_default". This operation does not return anything
in case of successful transaction commits.
syntax: local res, err = txn:commit()
context: any context except init_by_lua*
Commits all operations currently inside the transactions table using a single LMDB transaction. Since LMDB transaction exhibits ACID (atomicity, consistency, isolation, durability) properties, this method will either commit all operations at once or fail without causing side effects.
In case of successful transaction commit, true will be returned. Output value of each operation
can be accessed like this: txn[3].value. Please note that Lua table index starts at 1 and the
order corresponds to the order operations were appended into the transaction. So the first operation's
output will be inside txn[1] and second operation's result will be inside txn[2].
In case of any error during the transaction, it will be rolled back and nil and
an string describing the reason of the failure will be returned instead. Accessing the output value
from the txn table when commit() returned an error is undefined.
syntax: res, err = prefix.page(start, prefix, db?)
context: any context
Return all keys >= start and starts with prefix. If db is omitted,
it defaults to "_default".
The return value of this function is a table res where res[1].key and res[1].value
corresponds to the first key and value, res[2].key and res[2].value corresponds to the
second and etc. If no keys matched the provided criteria, then an empty table will be
returned.
In case of errors, nil and an string describing the reason of the failure will be returned.
syntax: lmdb_environment_path path;
context: main
Set the directory in which the LMDB database files reside.
syntax: lmdb_max_databases number;
context: main
Set the maximum number of named databases, the default value is 1.
syntax: lmdb_map_size number;
context: main
Set the size of the memory map, the default value is 1048576(1MB).
syntax: lmdb_validation_tag value;
default: none
context: main
Set a content validation tag into LMDB. When LMDB starts, it will check the tag value, if the value is different from the directive value, the content of LMDB will be cleaned up.
When this directive is not set, tag validation is disabled.
Copyright (c) 2021-2022 Kong, Inc.
Licensed under the Apache License, Version 2.0 <LICENSE or https://www.apache.org/licenses/LICENSE-2.0>. Files in the project may not be copied, modified, or distributed except according to those terms.