The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.

Overview

Project website www.tarantool.io/en/doc/latest
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@github.com:tarantool/doc.git
Repository branch test-weblate
Last remote commit updated pot afee6c42
TarantoolBot authored a year ago
Weblate repository http://weblate.tarantool.io/git/testing_project/documentation-dev_guideinternalsmsgpack_extensions/
File mask locale/*/LC_MESSAGES/dev_guide/internals/file_formats.po
Translation file Not available
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 26 1,085 7,375
Translated 100% 26 100% 1,085 100% 7,375
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 26 100% 1,085 100% 7,375
Failing checks 3% 1 19% 211 19% 1,406
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 28 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

1,085
Hosted words
26
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

Example
a year ago
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

To maintain data persistence, Tarantool writes each data change request (insert, update, delete, replace, upsert) into a write-ahead log (WAL) file in the :ref:`wal_dir <cfg_basic-wal_dir>` directory. A new WAL file is created when the current one reaches the :ref:`wal_max_size <cfg_binary_logging_snapshots-wal_max_size>` size. Each data change request gets assigned a continuously growing 64-bit log sequence number. The name of the WAL file is based on the log sequence number of the first record in the file, plus an extension ``.xlog``.
a year ago
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

0 3 4 17
+-------------+========+============+===========+=========+
| | | | | |
| 0xd5ba0bab | LENGTH | CRC32 PREV | CRC32 CUR | PADDING |
| | | | | |
+-------------+========+============+===========+=========+
MP_FIXEXT2 MP_INT MP_INT MP_INT ---

+============+ +===================================+
| | | |
| HEADER | | BODY |
| | | |
+============+ +===================================+
MP_MAP MP_MAP
a year ago
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

After the file header come the data tuples. Tuples begin with a row marker ``0xd5ba0bab`` and the last tuple may be followed by an EOF marker ``0xd510aded``. Thus, between the file header and the EOF marker, there may be data tuples that have this form:
a year ago
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

<type>\n SNAP\n or XLOG\n
<version>\n currently 0.13\n
Server: <server_uuid>\n where UUID is a 36-byte string
VClock: <vclock_map>\n e.g. {1: 0}\n
\n
a year ago
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

The header of a ``.snap`` or ``.xlog`` file looks like:
a year ago
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

Secondarily, the .snap file's records are ordered by primary key within space id.
a year ago
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

Primarily, the .snap file's records are ordered by space id. Therefore the records of system spaces -- such as ``_schema``, ``_space``, ``_index``, ``_func``, ``_priv`` and ``_cluster`` -- will be at the start of the .snap file, before the records of any spaces that were created by users.
a year ago
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

The format of a snapshot .snap file is nearly the same as the format of a WAL .xlog file. However, the snapshot header differs: it contains the instance's global unique identifier and the snapshot file's position in history, relative to earlier snapshot files. Also, the content differs: an .xlog file may contain records for any data-change requests (inserts, updates, upserts, and deletes), a .snap file may only contain records of inserts to memtx spaces.
a year ago
User avatar None

New source string

testing_project / Documentation: dev_guide/internals/file_formats — English

The snapshot file format
a year ago
Browse all translation changes