This could result in a broken instance if it terminated in between the
two storage writes. Now we always persist the commit index before
applying the persisted entries and do so in a transaction with unstable
entries or snapshot if they are present.

test: mark test_script_failure as xfail, because it's too flaky and doesn't check for anything we care about

Arseniy Volynets authored 1 year ago and Yaroslav Dynnikov committed 1 year ago

- Update sbroad submodule to commit adding support
for subqueries
- Add integration tests for sql queries with
subqueries and global tables

Supported queries:
- Queries that reference global tables in subqueries:
```sql
select a from segment_t where
b in (select c + d from global_t)
```
- Queries that read from global tables and use subquery:
```sql
select c from global_t
where d in (select a from segment_t)
```

Note: the support of subqueries applies only to types
of queries currently supported for global tables.
Joins, aggregates, except, union all are currently not
supported for global tables.

Rename space object type to table

Now the records look like this:

```
{
  "message": "instance is starting",
  "severity": "low",
  "time": "2023-11-22T22:10:24.211+0300",
  "title": "local_startup"
}
{
  "message": "target grade of instance `i1` changed to Online(7)",
  "severity": "low",
  "time": "2023-11-22T22:10:24.334+0300",
  "title": "change_target_grade"
}
{
  "message": "current grade of instance `i1` changed to Replicated(7)",
  "severity": "medium",
  "time": "2023-11-22T22:10:24.436+0300",
  "title": "change_current_grade"
}
```

This patch adds the following events:
* create_database
* change_target_grade
* change_current_grade

sbroad needs to be updated to the version that supports newer
tarantool-module

sbroad support for new module version was merged here:
https://git.picodata.io/picodata/picodata/sbroad/-/merge_requests/355

Dmitry Rodionov authored 1 year ago and Yaroslav Dynnikov committed 1 year ago

It has been observed that on Fedora -export-dynamic triggers some
reincarnation of this bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47390

TLDR: it treated leading -e as entrypoint argument so resulting binary
was completely broken, i e there was no main in it and entrypoint was
set to unrelated deregister_tm_clones. Big thanks to @gmoshkin for
finding the solution and to @funbringer for assistance with debugging

- Now we explicitly store the current & target vshard configuration in
  global storage

Follow-up for bfe08313

Also fix some docstrings

This patch changes the way audit records are formatted. Previously
we would format them as plain strings (we still do that in tlog),
now we use json to store all KV pairs including the message.

TODO: optimize string allocations using a stream formatter.

Example:

```
{
  "time": "2023-11-16T22:48:08.297+0300",
  "level": "WARN",
  "auth_type": "chap-sha1",
  "message": "created user `idris`",
  "title": "create_user",
  "pid": 66625,
  "cord_name": "main",
  "fiber_id": 111,
  "fiber_name": "raft_main_loop",
  "file": "src/storage.rs",
  "line": 2633
}
```

This is useful to avoid sorting during snapshot preparation and in
upcoming access control patch it simplifies the check whether a
particular space id belongs to system space id range.

This patch implements an `--audit` flag (disabled by default) which
gives user the ability to enable and configure the audit log. The
flag takes a string containing the mode and parameters needed to
initialize tarantool's logging machinery.

See the flag's documentation for more info.

Example:

```
picodata run --interactive --audit=/tmp/audit.log
```