cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: managed-apikeys.md

title: API keys headerTitle: API keys linkTitle: API keys description: Manage API keys for use with YugabyteDB Managed automation tools including API, CLI, and Terraform provider. headcontent: Use API keys to authenticate with automation tools aliases: /preview/yugabyte-cloud/cloud-admin/cloud-admin-apikeys/ menu: preview_yugabyte-cloud: identifier: managed-apikeys parent: managed-automation weight: 10 type: docs YugabyteDB Managed provides a REST API so that you can manage clusters programmatically. The API uses bearer token authentication, and each request requires a secret key, called an API key. API keys are not stored in YugabyteDB Managed. Safeguard them by doing the following: Store API keys in a secure location with strong encryption, such as a password manager. Revoke keys that are lost or compromised. Don't embed keys in code. Applications that contain keys can be de-compiled to extract keys, or de-obfuscated from on-device storage. API keys can also be compromised if committed to a code repository. API keys are ; for example, keys assigned a Developer role can only be used to perform developer-level tasks using the API. The API Keys tab under Access Control on the Security page displays a list of API keys created for your account that includes the key name, key status, the user that created the key, and the date it was created, last used, and expires. To view API key details, select an API key in the list to display the API Key Details sheet. To create an API key: Navigate to Security > Access Control > API Keys, and click Create API Key. Enter a name and description for the key. Choose a for the API Key. Set the key expiration or select Never expire to create a key without an expiration. Click Generate Key. Click the Copy icon to copy the key and store the key in a secure location. {{< warning title="Important" >}} The key is only displayed one time; it is not available in YugabyteDB Managed after you click Done. Store keys in a secure location. If you lose a key, revoke it and create a new one. {{< /warning >}} Click Done. To revoke an API key, click Revoke for the API key in the list you want to revoke. You can also revoke an API key by clicking Revoke API Key in the API Key Details sheet.
Project: YugabyteDB (App Definition and Development / Database)
File: tsrevrangebytime.md

title: TSREVRANGEBYTIME linkTitle: TSREVRANGEBYTIME description: TSREVRANGEBYTIME menu: preview: parent: api-yedis weight: 2460 aliases: /preview/api/redis/tsrevrangebytime /preview/api/yedis/tsrevrangebytime type: docs `TSREVRANGEBYTIME key low_ts high_ts [LIMIT limit]` This command fetches the values for the given `lowts`, `hights` range in the time series that is specified by the given `key` ordered from newest to oldest. If `LIMIT` is specified, then at most `limit` pairs will be fetched. If the given `key` is associated with non-time series data, an error is raised. If the given `lowts` or `hights` are not a valid signed 64 bit integers, an error is raised. If `limit` is not a valid positive 32 bit integer, an error is raised. `lowts` and `hights` are inclusive unless they are prefixed with `(`, in that case they are exclusive. Special bounds `-inf` and `+inf` are also supported to retrieve an entire range Returns a list of timestamp, value pairs found in the range specified by `lowts`, `hights`. If `LIMIT` is specified, at most `limit` pairs will be fetched. You can do this as shown below. ```sh TSADD ts_key 1 one 2 two 3 three 4 four 5 five 6 six ``` ``` "OK" ``` ```sh TSREVRANGEBYTIME ts_key 2 4 ``` ``` 1) "4" 2) "four" 3) "3" 4) "three" 5) "2" 6) "two" ``` 2 is exclusive ```sh TSREVRANGEBYTIME ts_key (2 4 ``` ``` 1) "4" 2) "four" 3) "3" 4) "three" ``` 2 and 4 are exclusive ```sh TSREVRANGEBYTIME ts_key (2 (4 ``` ``` 1) "3" 2) "three" ``` ```sh TSREVRANGEBYTIME ts_key -inf 3 ``` ``` 1) "3" 2) "three" 3) "2" 4) "two" 5) "1" 6) "one" ``` ```sh TSREVRANGEBYTIME ts_key 2 +inf ``` ``` 1) "6" 2) "six" 3) "5" 4) "five" 5) "4" 6) "four" 7) "3" 8) "three" 9) "2" 10) "two" ``` ```sh TSREVRANGEBYTIME ts_key -inf 3 LIMIT 2 ``` ``` 1) "3" 2) "three" 3) "2" 4) "two" ``` ```sh TSREVRANGEBYTIME ts_key -inf 3 LIMIT 10 ``` ``` 1) "3" 2) "three" 3) "2" 4) "two" 5) "1" 6) "one" ``` , , , , ,
Project: KICS (Provisioning / Security & Compliance)
File: f262118c-1ac6-4bb3-8495-cc48f1775b85.md

title: Ecs Data Disk Kms Key Id Undefined hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f262118c-1ac6-4bb3-8495-cc48f1775b85 Query name: Ecs Data Disk Kms Key Id Undefined Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: Ecs Data Disk Kms Key Id should be set<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2" resource "aliclouddisk" "ecsdisk" { availability_zone = "cn-beijing-b" name = "New-disk" description = "Hello ecs disk." category = "cloud_efficiency" size = "30" encrypted = true tags = { Name = "TerraformTest" } } ``` ```tf title="Negative test num. 1 - tf file" resource "aliclouddisk" "ecsdisk" { availability_zone = "cn-beijing-b" name = "New-disk" description = "Hello ecs disk." category = "cloud_efficiency" size = "30" encrypted = true kmskeyid = "2a6767f0-a16c-4679-a60f-13bf*" tags = { Name = "TerraformTest" } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-12-2022-01-53-10_56b762eb.md

timestamp: "2022-10-12 01:53:00 UTC Wed" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.15" k8s-distro: minikube k8s-version: "v1.20.11" service-mesh: Consul service-mesh-version: "v0.49.0" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Metal³ (Provisioning / Automation & Configuration)
File: feature_request.md

name: Feature addition about: Suggest and track an idea for this project User Story As a [developer/user/operator] I would like to [high level description] for [reasons] Detailed Description [A clear and concise description of what you want to happen.] Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] /kind feature
Project: YugabyteDB (App Definition and Development / Database)
File: alter_sequence,name,alter_sequence_options.grammar.md

```output.ebnf altersequence ::= ALTER SEQUENCE [ IF EXISTS ] sequencename altersequenceoptions name ::= '<Text Literal>' altersequenceoptions ::= [ AS seqdatatype ] [ INCREMENT [ BY ] increment ] [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ] [ START [ WITH ] start ] [ RESTART [ [ WITH ] restart ] ] [ CACHE cache ] [ OWNED BY tablename.tablecolumn | NONE ] ```
Project: KICS (Provisioning / Security & Compliance)
File: 4d7ee40f-fc5d-427d-8cac-dffbe22d42d1.md

title: Authorization Mode Node Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4d7ee40f-fc5d-427d-8cac-dffbe22d42d1 Query name: Authorization Mode Node Not Set Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: When using kube-apiserver command, the 'authorization-mode' flag should have 'Node' mode<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--authorization-mode=AlwaysAllow"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--authorization-mode=RBAC"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--authorization-mode=RBAC,Node"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver","--authorization-mode=RBAC,Node"] args: [] restartPolicy: OnFailure ```
Project: ShardingSphere (App Definition and Development / Database)
File: show-default-sharding-strategy.en.md

+++ title = "SHOW DEFAULT SHARDING STRATEGY" weight = 4 +++ The `SHOW DEFAULT SHARDING STRATEGY` syntax is used to query default sharding strategy in specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowDefaultShardingStrategy::= 'SHOW' 'DEFAULT' 'SHARDING' 'STRATEGY' ('FROM' databaseName)? databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. | Column | Description | |--|-| | name | Sharding strategy scope | | type | Sharding strategy type | | sharding_column | Sharding column | | shardingalgorithmname | Sharding algorithm name | | shardingalgorithmtype | Sharding algorithm type | | shardingalgorithmprops | Sharding algorithm properties | Query default sharding strategy in specified database. ```sql SHOW DEFAULT SHARDING STRATEGY FROM sharding_db; ``` ```sql mysql> SHOW DEFAULT SHARDING STRATEGY FROM sharding_db; +-+-+--+-+-+--+ | name | type | shardingcolumn | shardingalgorithmname | shardingalgorithmtype | shardingalgorithm_props | +-+-+--+-+-+--+ | TABLE | STANDARD | orderid | tableinline | inline | {algorithm-expression=torderitem${orderid % 2}} | | DATABASE | STANDARD | orderid | tableinline | inline | {algorithm-expression=torderitem${orderid % 2}} | +-+-+--+-+-+--+ 2 rows in set (0.00 sec) ``` Query default sharding strategy in current database. ```sql SHOW DEFAULT SHARDING STRATEGY; ``` ```sql mysql> SHOW DEFAULT SHARDING STRATEGY; +-+-+--+-+-+--+ | name | type | shardingcolumn | shardingalgorithmname | shardingalgorithmtype | shardingalgorithm_props | +-+-+--+-+-+--+ | TABLE | STANDARD | orderid | tableinline | inline | {algorithm-expression=torderitem${orderid % 2}} | | DATABASE | STANDARD | orderid | tableinline | inline | {algorithm-expression=torderitem${orderid % 2}} | +-+-+--+-+-+--+ 2 rows in set (0.00 sec) ``` `SHOW`, `DEFAULT`, `SHARDING`, `STRATEGY`, `FROM`
Project: ClickHouse (App Definition and Development / Database)
File: v22.3.8.39-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : - Change `all|noarch` packages to architecture-dependent - Fix some documentation for it - Push aarch64|arm64 packages to artifactory and release assets - Fixes . (). Backported in : Fix bug with nested short-circuit functions that led to execution of arguments even if condition is false. Closes . (). Backported in : Fix incorrect result of distributed queries with `DISTINCT` and `LIMIT`. Fixes . (). Backported in : Now it's possible to start a clickhouse-server and attach/detach tables even for tables with the incorrect values of IPv4/IPv6 representation. Proper fix for issue . (). Backported in : `rankCorr` function will work correctly if some arguments are NaNs. This closes . (). Backported in : Fix use-after-free for Map combinator that leads to incorrect result. (). Backported in : Fix projection analysis which might lead to wrong query result when IN subquery is used. This fixes . (). Backported in : - Fix potential error with literals in `WHERE` for join queries. Close . (). Try to fix some trash (). Update docker-compose to try get rid of v1 errors (). Trying backport useful features for CI (). Fix backports diff ().
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_kubernetes_delete.md

Delete a Kubernetes YugabyteDB Anywhere provider Delete a Kubernets provider in YugabyteDB Anywhere ``` yba provider kubernetes delete [flags] ``` ``` -f, --force [Optional] Bypass the prompt for non-interactive usage. -h, --help help for delete ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere K8s provider
Project: Trivy (Provisioning / Security & Compliance)
File: gcr.md

None, Trivy uses Google Cloud SDK. You don't need to install `gcloud` command. Credential file must have the `roles/storage.objectViewer` permissions. More information can be found in The JSON file specified should have the following format provided by google's service account mechanisms: ```json { "type": "service_account", "projectid": "yourspecial_project", "privatekeyid": "XXXXXXXXXXXXXXXXXXXXxx", "private_key": "--BEGIN PRIVATE KEY--\nNONONONO\n--END PRIVATE KEY--\n", "clientemail": "somedude@yourspecial_project.iam.gserviceaccount.com", "client_id": "1234567890", "auth_uri": "https://accounts.google.com/o/oauth2/auth", "token_uri": "https://oauth2.googleapis.com/token", "authproviderx509certurl": "https://www.googleapis.com/oauth2/v1/certs", "clientx509certurl": "https://www.googleapis.com/robot/v1/metadata/x509/somedude%40yourspecial_project.iam.gserviceaccount.com" } ``` If you want to use target project's repository, you can set them via `GOOGLEAPPLICATIONCREDENTIALS`. ```bash export GOOGLEAPPLICATIONCREDENTIALS=/path/to/credential.json ``` You can test credentials in the following manner (assuming they are in `/tmp` on host machine). ```bash docker run -it --rm -v /tmp:/tmp\ -e GOOGLEAPPLICATIONCREDENTIALS=/tmp/service_account.json\ aquasec/trivy image gcr.io/yourspecialproject/yourspecialimage:yourspecialtag ```
Project: YugabyteDB (App Definition and Development / Database)
File: setex.md

title: SETEX linkTitle: SETEX description: SETEX menu: preview: parent: api-yedis weight: 2271 aliases: /preview/api/redis/setex /preview/api/yedis/setex type: docs `SETEX key ttl_in_sec string_value` This command sets the value of `key` to be `stringvalue`, and sets the key to expire in `ttlin_sec` seconds. Returns status string. ```sh $ SETEX yugakey 10 "Yugabyte" ``` ``` "OK" ``` ```sh $ GET yugakey ``` ``` "Yugabyte" ``` ```sh $ TTL yugakey ``` ``` (integer) 10 ``` , , , , , , , , ,
Project: StarRocks (App Definition and Development / Database)
File: date_add.md

displayed_sidebar: "English" Adds a specified time interval to a date. ```Haskell DATETIME DATE_ADD(DATETIME|DATE date,INTERVAL expr type) ``` `date`: It must be a valid date or datetime expression. `expr`: the time interval you want to add. It must be of the INT type. `type`: the unit of the time interval. It can only be set to any of the following values: YEAR, QUARTER, MONTH, DAY, HOUR, MINUTE, SECOND, MILLISECOND (since 3.1.7), and MICROSECOND (since 3.1.7). Returns a DATETIME value. If the date does not exist, for example, `2020-02-30`, NULL is returned. If the date is a DATE value, it will be converted into a DATETIME value. ```Plain Text select date_add('2010-11-30 23:59:59', INTERVAL 2 DAY); +-+ | date_add('2010-11-30 23:59:59', INTERVAL 2 DAY) | +-+ | 2010-12-02 23:59:59 | +-+ select date_add('2010-12-03', INTERVAL 2 DAY); +-+ | date_add('2010-12-03', INTERVAL 2 DAY) | +-+ | 2010-12-05 00:00:00 | +-+ select date_add('2010-11-30 23:59:59', INTERVAL 2 QUARTER); +--+ | date_add('2010-11-30 23:59:59', INTERVAL 2 QUARTER) | +--+ | 2011-05-30 23:59:59 | +--+ select adddate('2023-10-31 23:59:59', INTERVAL 1 MILLISECOND); +--+ | adddate('2023-10-31 23:59:59', INTERVAL 1 MILLISECOND) | +--+ | 2023-10-31 23:59:59.001000 | +--+ select adddate('2023-10-31 23:59:59', INTERVAL 1 MICROSECOND); +--+ | adddate('2023-10-31 23:59:59', INTERVAL 1 MICROSECOND) | +--+ | 2023-10-31 23:59:59.000001 | +--+ ```
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: IMPLEMENTATIONS.md

Below is a list of tooling that claims to implement the Alternative Schema proposal. While support for this feature matures, refer to the details of projects listed below for any notes about stability and roadmap. The process to improve the OpenAPI specification includes feedback from end-users and tooling creators. We strongly encourage draft tooling be made available for early users of OAS drafts. These tools are not endorsed by the OAI | Title | Project Link | Language | Description | -- | -- | -- | -- |TBD |TBD |TBD |TBD | | Title | Project Link | Language |Description | |-|--|-|| |TBD |TBD |TBD |TBD | | Title | Project Link | Language |Description | |-|--|-|| |TBD |TBD |TBD |TBD | | Title | Project Link | Language | Description | | -- | | -- | -- | |TBD |TBD |TBD |TBD | | Title | Project Link | Language |Description | |-|--|-|| |TBD |TBD |TBD |TBD | | Title | Project Link | Language |Description | |-|--|-|| |TBD |TBD |TBD |TBD |
Project: Pulumi (Provisioning / Automation & Configuration)
File: PULL_REQUEST_TEMPLATE.md

<! Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the documentation. --> <! Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. --> Fixes # (issue) [ ] I have run `make tidy` to update any new dependencies [ ] I have run `make lint` to verify my code passes the lint check [ ] I have formatted my code using `gofumpt` <! Please provide details if the checkbox below is to be left unchecked. --> [ ] I have added tests that prove my fix is effective or that my feature works <! User-facing changes require a CHANGELOG entry. --> [ ] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change <!-- If the change(s) in this PR is a modification of an existing call to the Pulumi Cloud, then the service should honor older versions of the CLI where this change would not exist. You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add it to the service. --> [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Cloud API version <!-- @Pulumi employees: If yes, you must submit corresponding changes in the service repo. -->
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.18.0.md

title: v1.18.0 weight: 998982000 Additions: chore: bump go 1.17, k8s 1.23, and kubebuilder 3.3 chore(deps): update to Quarkus SDK extension 3.0.2 and Quarkus 2.6.3 chore(deps): update to use Quarkus JOSDK extension 3.0.1 Remove useless file chore: bump k8s 1.22.2 and kubebuilder 3.2 exposed exnpoints for micrometer metrics modified the Quarkus operator SDK version and tutorial too chore: bump fabric8 5.8.0 & quarkus 2.4.0 modified the doc file and removed file after generation release: fix release script to understand release branches Bug Fixes: Fix for wrongly generated file name See for more details. Add following variables to your project's `Makefile` below the `BUNDLE_IMG ?=`. ``` BUNDLEGENFLAGS ?= -q --overwrite --version $(VERSION) $(BUNDLEMETADATAOPTS) USEIMAGEDIGESTS ?= false ifeq ($(USEIMAGEDIGESTS), true) BUNDLEGENFLAGS += --use-image-digests endif ``` Using the YAML string '|' operator means that newlines in this string will Then in the `bundle` target we want to replace the flags passed to `generate bundle` with a reference to the `BUNDLEGENFLAGS` above. The `generate bundle` line should look like this ``` $(KUSTOMIZE) build config/manifests | operator-sdk generate bundle $(BUNDLEGENFLAGS) ``` For reference the PREVIOUS version looked as follows ``` $(KUSTOMIZE) build config/manifests | operator-sdk generate bundle -q --overwrite --version $(VERSION) $(BUNDLEMETADATAOPTS) ``` See for more details. Add the following line in `requirements.go` when using operator ansible sdk: ``` name: cloud.common version: "2.1.0" ``` See for more details.
Project: ClickHouse (App Definition and Development / Database)
File: clickhouse-format.md

slug: /en/operations/utilities/clickhouse-format title: clickhouse-format Allows formatting input queries. Keys: `--help` or`-h` Produce help message. `--query` Format queries of any length and complexity. `--hilite` Add syntax highlight with ANSI terminal escape sequences. `--oneline` Format in single line. `--maxlinelength` Format in single line queries with length less than specified. `--comments` Keep comments in the output. `--quiet` or `-q` Just check syntax, no output on success. `--multiquery` or `-n` Allow multiple queries in the same file. `--obfuscate` Obfuscate instead of formatting. `--seed <string>` Seed arbitrary string that determines the result of obfuscation. `--backslash` Add a backslash at the end of each line of the formatted query. Can be useful when you copy a query from web or somewhere else with multiple lines, and want to execute it in command line. Formatting a query: ```bash $ clickhouse-format --query "select number from numbers(10) where number%2 order by number desc;" ``` Result: ```bash SELECT number FROM numbers(10) WHERE number % 2 ORDER BY number DESC ``` Highlighting and single line: ```bash $ clickhouse-format --oneline --hilite <<< "SELECT sum(number) FROM numbers(5);" ``` Result: ```sql SELECT sum(number) FROM numbers(5) ``` Multiqueries: ```bash $ clickhouse-format -n <<< "SELECT min(number) FROM numbers(5); SELECT max(number) FROM numbers(5);" ``` Result: ``` SELECT min(number) FROM numbers(5) ; SELECT max(number) FROM numbers(5) ; ``` Obfuscating: ```bash $ clickhouse-format --seed Hello --obfuscate <<< "SELECT costfirstscreen BETWEEN a AND b, CASE WHEN x >= 123 THEN y ELSE NULL END;" ``` Result: ``` SELECT treasurymammothhazelnut BETWEEN nutmeg AND span, CASE WHEN chive >= 116 THEN switching ELSE ANYTHING END; ``` Same query and another seed string: ```bash $ clickhouse-format --seed World --obfuscate <<< "SELECT costfirstscreen BETWEEN a AND b, CASE WHEN x >= 123 THEN y ELSE NULL END;" ``` Result: ``` SELECT horsetapesummer BETWEEN folklore AND moccasins, CASE WHEN intestine >= 116 THEN nonconformist ELSE FORESTRY END; ``` Adding backslash: ```bash $ clickhouse-format --backslash <<< "SELECT * FROM (SELECT 1 AS x UNION ALL SELECT 1 UNION DISTINCT SELECT 3);" ``` Result: ``` SELECT * \ FROM \ ( \ SELECT 1 AS x \ UNION ALL \ SELECT 1 \ UNION DISTINCT \ SELECT 3 \ ) ```