Merge branch 'main' into stage_table

Author: youngsofun

.github/actions/build_linux/action.yml

@@ -14,7 +14,7 @@ runs:
       uses: ./.github/actions/setup_build_tool
       with:
         image: ${{ inputs.target }}
-        bypass_env_vars: RUSTFLAGS,RUST_LOG,RUSTC_WRAPPER,SCCACHE_BUCKET,SCCACHE_S3_KEY_PREFIX,SCCACHE_S3_USE_SSL,AWS_DEFAULT_REGION,AWS_REGION,AWS_ROLE_ARN,AWS_STS_REGIONAL_ENDPOINTS,AWS_WEB_IDENTITY_TOKEN_FILE
+        bypass_env_vars: RUSTFLAGS,RUST_LOG,RUSTC_WRAPPER,SCCACHE_BUCKET,SCCACHE_S3_KEY_PREFIX,SCCACHE_S3_USE_SSL,AWS_DEFAULT_REGION,AWS_REGION,AWS_ROLE_ARN,AWS_STS_REGIONAL_ENDPOINTS,AWS_WEB_IDENTITY_TOKEN_FILE,je_cv_pthread_getname_np
 
     - name: Build Debug
       if: inputs.profile == 'debug'

.github/auto_assign.yml

@@ -64,6 +64,15 @@ jobs:
           # fetch all tags,  metasrv and metaclient need tag as its version.
           fetch-depth: 0
       - uses: ./.github/actions/build_linux
+        env:
+          # To avoid the `undefined reference to pthread_getname_np` error during linking,
+          # here we override set config environment var `je_cv_pthread_getname_np` to `no`,
+          # as suggested by tikv-jemalloc-sys's maintainer @BusyJay:
+          # https://github.com/tikv/jemallocator/issues/30#issuecomment-1183786410
+          #
+          # Hopefully this trick can be removed when rust upgraded to musl 1.2.3
+          # https://github.com/rust-lang/rust/pull/102891
+          je_cv_pthread_getname_np: no
         with:
           target: ${{ matrix.arch }}-unknown-linux-musl
           profile: debug

.github/workflows/dev-linux.yml

@@ -58,6 +58,7 @@ members = [
     "src/query/storages/stage",
     "src/query/storages/system",
     "src/query/storages/view",
+    "src/query/storages/parquet",
     "src/query/users",
     # databend-query
     "src/query/service",

Cargo.lock

@@ -9,6 +9,10 @@ This guideline will introduce how to back up and restore the meta service cluste
 
 ## Export Data From Meta Service
 
+It supports to export from a databend-meta data dir or from a running databend-meta server.
+
+### Export from data dir
+
 Shutdown the `databend-meta` service.
 
 Then export sled DB from the dir(`<your_meta_dir>`) in which the `databend-meta` stores meta to a local file `output_fn`, in multi-line JSON format.
@@ -29,6 +33,20 @@ E.g., every line in the output file is a JSON of an exported key-value record.
 
 Note: without the `--db` argument, the exported data will output to the stdio instead.
 
+### Export from a running server
+
+Similar to exporting from data dir, but with the service endpoint argument `--grpc-api-address <ip:port>` in place of the `--raft-dir`,
+where `<ip:port>` is the `grpc_api_address` in [databend-meta config.toml](./15-metasrv-config.md), e.g.:
+
+```shell
+./target/debug/databend-metactl --export --grpc-api-address "127.0.0.1:9191" --db <output_fn>
+
+# tail "<output_fn>"
+# ["state_machine/0",{"Nodes":{"key":2,"value":{"name":"","endpoint":{"addr":"localhost","port":28203}}}}]
+# ...
+```
+
+
 ## Restore a databend-meta
 
 The following command rebuild a meta service db in `<your_meta_dir>` from

Cargo.toml

@@ -0,0 +1,73 @@
+---
+title: RESTORE TABLE
+---
+
+Restores a table to an earlier version with a snapshot ID or timestamp.
+
+By the snapshot ID or timestamp you specify in the command, Databend restores the table to a prior state where the snapshot was created. To retrieve snapshot IDs and timestamps of a table, use [FUSE_SNAPSHOT](../../../15-sql-functions/111-system-functions/fuse_snapshot.md).
+
+The capability to restore a table is subject to these conditions:
+
+- The command only restores existing tables to their prior states. To recover a dropped table, use [UNDROP TABLE](21-ddl-undrop-table.md).
+
+- Restoring a table is part of Databend's time travel feature. Before using the command, make sure the table you want to restore is eligible for time travel. For example, the command doesn't work for transient tables because Databend does not create or store snapshots for such tables.
+
+- You cannot roll back after restoring a table to a prior state, but you can restore the table again to an earlier state.
+
+- Databend recommends this command for emergency recovery only. To query the history data of a table, use the [AT](../../20-query-syntax/dml-at.md) clause.
+
+## Syntax
+
+```sql
+-- Restore with a snapshot ID
+ALTER TABLE <table> FLASHBACK TO (SNAPSHOT => '<snapshot-id>');
+
+-- Restore with a snapshot timestamp
+ALTER TABLE <table> FLASHBACK TO (TIMESTAMP => '<timestamp>'::TIMESTAMP);
+```
+
+## Examples
+
+```sql
+CREATE TABLE mytable(a int);
+
+INSERT INTO mytable VALUES(1);
+INSERT INTO mytable VALUES(2);
+INSERT INTO mytable VALUES(3);
+
+SELECT * FROM mytable;
+
+a|
+-+
+3|
+2|
+1|
+
+-- Retrieve snapshot information
+SELECT snapshot_id, timestamp FROM FUSE_SNAPSHOT('default','mytable');
+
+snapshot_id                     |timestamp                    |
+--------------------------------+-----------------------------+
+2648bee0e85044f9879e71f1d37f453b|2022-12-06 20:50:53.324485000|
+7e5d4f7ebdbc44d08116771193533346|2022-12-06 20:50:23.623331000|
+41c94c7ea47a432388770ada0a66b6c0|2022-12-06 20:49:56.125918000|
+
+-- Restore with a snapshot ID
+ALTER TABLE mytable FLASHBACK TO (SNAPSHOT => '7e5d4f7ebdbc44d08116771193533346');
+
+SELECT * FROM mytable;
+
+a|
+-+
+2|
+1|
+
+-- Restore with a snapshot timestamp
+ALTER TABLE mytable FLASHBACK TO (TIMESTAMP => '2022-12-06 20:49:56.125918000'::TIMESTAMP);
+
+SELECT * FROM mytable;
+
+a|
+-+
+1|
+```

docs/doc/10-deploy/06-metasrv/30-metasrv-backup-restore.md

@@ -11,7 +11,8 @@ SELECT
     [ALL | DISTINCT]
     select_expr [[AS] alias], ...
     [INTO variable [, ...]]
-    [ FROM table_references
+    [EXCLUDE (col_name1 [, col_name2, col_name3, ...] ) ]
+    [FROM table_references
     [AT ...]
     [WHERE expr]
     [GROUP BY {{col_name | expr | col_alias | col_position}, ...
@@ -22,6 +23,7 @@ SELECT
     [OFFSET row_count]
     [IGNORE_RESULT]
     ]
+    ]
 ```
 
 :::tip
@@ -41,6 +43,47 @@ SELECT number FROM numbers(3);
 +--------+
 ```
 
+### EXCLUDE Parameter
+
+Excludes one or more columns by their names from the result. The parameter is usually used in conjunction with `SELECT * ...` to exclude a few columns from the result instead of retrieving them all.
+
+```sql
+SELECT * FROM allemployees ORDER BY id;
+
+---
+| id | firstname | lastname | gender |
+|----|-----------|----------|--------|
+| 1  | Ryan      | Tory     | M      |
+| 2  | Oliver    | Green    | M      |
+| 3  | Noah      | Shuster  | M      |
+| 4  | Lily      | McMent   | F      |
+| 5  | Macy      | Lee      | F      |
+
+-- Exclude the column "id" from the result
+SELECT * EXCLUDE id FROM allemployees;
+
+---
+| firstname | lastname | gender |
+|-----------|----------|--------|
+| Noah      | Shuster  | M      |
+| Ryan      | Tory     | M      |
+| Oliver    | Green    | M      |
+| Lily      | McMent   | F      |
+| Macy      | Lee      | F      |
+
+-- Exclude the columns "id" and "lastname" from the result
+SELECT * EXCLUDE (id,lastname) FROM allemployees;
+
+---
+| firstname | gender |
+|-----------|--------|
+| Oliver    | M      |
+| Ryan      | M      |
+| Lily      | F      |
+| Noah      | M      |
+| Macy      | F      |
+```
+
 ## FROM Clause
 
 ```sql