cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: distinct.md

slug: /en/sql-reference/statements/select/distinct sidebar_label: DISTINCT If `SELECT DISTINCT` is specified, only unique rows will remain in a query result. Thus, only a single row will remain out of all the sets of fully matching rows in the result. You can specify the list of columns that must have unique values: `SELECT DISTINCT ON (column1, column2,...)`. If the columns are not specified, all of them are taken into consideration. Consider the table: ```text abc 1 1 1 1 1 1 2 2 2 2 2 2 1 1 2 1 2 2 ``` Using `DISTINCT` without specifying columns: ```sql SELECT DISTINCT * FROM t1; ``` ```text abc 1 1 1 2 2 2 1 1 2 1 2 2 ``` Using `DISTINCT` with specified columns: ```sql SELECT DISTINCT ON (a,b) * FROM t1; ``` ```text abc 1 1 1 2 2 2 1 2 2 ``` ClickHouse supports using the `DISTINCT` and `ORDER BY` clauses for different columns in one query. The `DISTINCT` clause is executed before the `ORDER BY` clause. Consider the table: ``` text ab 2 1 1 2 3 3 2 4 ``` Selecting data: ```sql SELECT DISTINCT a FROM t1 ORDER BY b ASC; ``` ``` text a 2 1 3 ``` Selecting data with the different sorting direction: ```sql SELECT DISTINCT a FROM t1 ORDER BY b DESC; ``` ``` text a 3 1 2 ``` Row `2, 4` was cut before sorting. Take this implementation specificity into account when programming queries. `DISTINCT` works with as if `NULL` were a specific value, and `NULL==NULL`. In other words, in the `DISTINCT` results, different combinations with `NULL` occur only once. It differs from `NULL` processing in most other contexts. It is possible to obtain the same result by applying across the same set of values as specified as `SELECT` clause, without using any aggregate functions. But there are few differences from `GROUP BY` approach: `DISTINCT` can be applied together with `GROUP BY`. When is omitted and is defined, the query stops running immediately after the required number of different rows has been read. Data blocks are output as they are processed, without waiting for the entire query to finish running.
Project: Open Application Model (App Definition and Development / Application Definition & Image Build)
File: notational_convention.md

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in . The key words "unspecified", "undefined", and "implementation-defined" are to be interpreted as described in the [rationale for the C99 standard][c99-unspecified]. An implementation IS compliant if it satisfies all the MUST, REQUIRED, and SHALL requirements. An implementation IS NOT compliant if it fails to satisfy one or more of the MUST, REQUIRED, or SHALL requirements.
Project: YugabyteDB (App Definition and Development / Database)
File: create-admin-user.md

title: Create admin user headerTitle: Create admin user linkTitle: Create admin user description: Create an admin user. menu: v2.18_yugabyte-platform: identifier: create-admin-user parent: configure-yugabyte-platform weight: 10 type: docs YugabyteDB Anywhere allows you to create an admin account and manage your user profile. You can create an admin account via `http://<yugabytedbanywhere-host-ip>/register`, replacing yugabytedbanywhere-host-ip with the IP address hosting your YugabyteDB Anywhere instance, as per the following example: ```output http://10.170.1.192/register ``` The following illustration shows the admin console: Note that by default YugabyteDB Anywhere runs as a single-tenant application. You proceed with the account creation as follows: Select the environment. Enter your new user credentials. Confirm the user agreement. Click Register. You are now redirected to the login page located at `http://<yugabydbanywhere-host-ip>/login`. This page allows you to log in to YugabyteDB Anywhere using your new credentials. Once logged in, you may change the information related to your account, including the user name and password, by clicking the User icon at the top right, and then selecting User Profile.
Project: ClickHouse (App Definition and Development / Database)
File: date32.md

slug: /en/sql-reference/data-types/date32 sidebar_position: 14 sidebar_label: Date32 A date. Supports the date range same with . Stored as a signed 32-bit integer in native byte order with the value representing the days since 1970-01-01 (0 represents 1970-01-01 and negative values represent the days before 1970). Examples Creating a table with a `Date32`-type column and inserting data into it: ``` sql CREATE TABLE dt32 ( `timestamp` Date32, `event_id` UInt8 ) ENGINE = TinyLog; ``` ``` sql -- Parse Date -- - from string, -- - from 'small' integer interpreted as number of days since 1970-01-01, and -- - from 'big' integer interpreted as number of seconds since 1970-01-01. INSERT INTO dt32 VALUES ('2100-01-01', 1), (47482, 2), (4102444800, 3); SELECT * FROM dt32; ``` ``` text timestampevent_id 2100-01-01 1 2100-01-01 2 ``` See Also
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_events_attach.md

Events attach to 'events' channels command Events attach command allows to display 'events' channel content for debugging proposes ``` kubemq events attach [flags] ``` ``` kubemq events attach * kubemq events attach some-events kubemq events attach some-events1 some-events2 kubemq events attach some-events -i some* kubemq events attach some-events -e not-some* ``` ``` -e, --exclude stringArray set (regex) strings to exclude -h, --help help for attach -i, --include stringArray set (regex) strings to include ``` - Execute Kubemq 'events' Pub/Sub commands
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_addon_disable.md

title: kbcli addon disable Disable an addon. ``` kbcli addon disable ADDON_NAME [flags] ``` ``` --allow-missing-template-keys If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true) --dry-run string[="unchanged"] Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource. (default "none") --edit Edit the API resource -h, --help help for disable -o, --output string Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). --show-managed-fields If true, keep the managedFields when printing objects in JSON or YAML format. --template string Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]. ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Addon command.
Project: KICS (Provisioning / Security & Compliance)
File: 0e59d33e-bba2-4037-8f88-9765647ca7ad.md

title: BOM - AWS Kinesis hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0e59d33e-bba2-4037-8f88-9765647ca7ad Query name: BOM - AWS Kinesis Platform: Terraform Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of Kinesis resources found. Amazon Kinesis is a real-time streaming service that provides collection, processing, and analysis of video and data streams in real-time<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 20" resource "awskinesisstream" "positive1" { name = "terraform-kinesis-test" shard_count = 1 retention_period = 48 shardlevelmetrics = [ "IncomingBytes", "OutgoingBytes", ] streammodedetails { stream_mode = "PROVISIONED" } tags = { Environment = "test" } } resource "awskinesisstream" "positive2" { name = "terraform-kinesis-test2" shard_count = 1 retention_period = 48 shardlevelmetrics = [ "IncomingBytes", "OutgoingBytes", ] streammodedetails { stream_mode = "PROVISIONED" } tags = { Environment = "test" } kmskeyid = "1234abcd-12ab-34cd-56ef-0987654321ab" } ``` ```tf title="Negative test num. 1 - tf file" module "kinesis-stream" { source = "rodrigodelmonte/kinesis-stream/aws" version = "v2.0.3" name = "kinesisstreamexample" shard_count = 1 retention_period = 24 shardlevelmetrics = ["IncomingBytes", "OutgoingBytes"] enforceconsumerdeletion = false encryption_type = "KMS" kmskeyid = "alias/aws/kinesis" tags = { Name = "kinesisstreamexample" } } ```
Project: YugabyteDB (App Definition and Development / Database)
File: python.md

title: Build a YugabyteDB application using Python and YEDIS headerTitle: Build an application using Python linkTitle: Python description: Use Python to build a YugabyteDB application that interacts with YEDIS aliases: /preview/yedis/develop/client-drivers/python menu: preview: identifier: client-drivers-yedis-python parent: develop-yedis type: docs Install the Python driver using the following command. ```sh $ sudo pip install yedis ``` This tutorial assumes that you have: installed YugabyteDB, created a universe, and are able to interact with it using the Redis shell. If not, follow the steps in . Create a file `yb-redis-helloworld.py` and add the following content to it. ```python import redis r = redis.Redis(host='localhost', port=6379) userid = 1 user_profile = {"name": "John", "age": "35", "language": "Python"} r.hmset(userid, user_profile) print "Inserted userid=1, profile=%s" % user_profile print r.hgetall(userid) ``` To run the application, type the following: ```sh $ python yb-redis-helloworld.py ``` You should see the following output. ``` Inserted userid=1, profile={'age': '35', 'name': 'John', 'language': 'Python'} {'age': '35', 'name': 'John', 'language': 'Python'} ```
Project: StarRocks (App Definition and Development / Database)
File: array_contains_all.md

displayed_sidebar: "English" Checks whether `arr1` contains all the elements of `arr2`, that is, whether `arr2` is a subset of `arr1`. If yes, 1 is returned. If not, 0 is returned. ~~~Haskell BOOLEAN arraycontainsall(arr1, arr2) ~~~ `arr`: the two arrays to compare. This syntax checks whether `arr2` is a subset of `arr1`. The data types of elements in the two arrays must be the same. For the data types of array elements supported by StarRocks, see . Returns a value of the BOOLEAN type. 1 is returned if `arr2` is a subset of `arr1`. Otherwise, 0 is returned. If any of the two arrays is NULL, NULL is returned. If an array contains `null` elements, `null` is processed as a value. An empty array is a subset of any array. Elements in the two arrays can have different order. Create a table named `t1` and insert data into this table. ~~~SQL CREATE TABLE t1 ( c0 INT, c1 ARRAY<INT>, c2 ARRAY<INT> ) ENGINE=OLAP DUPLICATE KEY(c0) DISTRIBUTED BY HASH(c0); INSERT INTO t1 VALUES (1,[1,2,3],[1,2]), (2,[1,2,3],[1,4]), (3,NULL,[1]), (4,[1,2,null],NULL), (5,[1,2,null],[null]), (6,[2,3],[]); ~~~ Query data from this table. ~~~Plain SELECT * FROM t1 ORDER BY c0; +++-+ | c0 | c1 | c2 | +++-+ | 1 | [1,2,3] | [1,2] | | 2 | [1,2,3] | [1,4] | | 3 | NULL | [1] | | 4 | [1,2,null] | NULL | | 5 | [1,2,null] | [null] | | 6 | [2,3] | [] | +++-+ ~~~ Check whether each row of `c2` is a subset of the corresponding row of `c1`. ~~~Plaintext SELECT c0, c1, c2, arraycontainsall(c1, c2) FROM t1 ORDER BY c0; +++-+-+ | c0 | c1 | c2 | arraycontainsall(c1, c2) | +++-+-+ | 1 | [1,2,3] | [1,2] | 1 | | 2 | [1,2,3] | [1,4] | 0 | | 3 | NULL | [1] | NULL | | 4 | [1,2,null] | NULL | NULL | | 5 | [1,2,null] | [null] | 1 | | 6 | [2,3] | [] | 1 | +++-+-+ ~~~ In the output: For row 1, `c2` is a subset of `c1` and 1 is returned. For row 2, `c2` is not a subset of `c1` and 0 is returned. For row 3, `c1` is NULL and NULL is returned. For row 4, `c2` is NULL and NULL is returned. For row 5, the two arrays contain `null` and `null` is processed as a normal value, `1` is returned. For row 6, `c2` is an empty array and considered a subset of `c1`. Therefore, `1` is returned.
Project: openGemini (App Definition and Development / Database)
File: ADOPTERS.md

This document lists the organizations that use openGemini on production or testing environment and projects that adopts openGemini as their upstream. Please make a pull request on this document if any organization or project would like to be added or removed. | Adopter name | Adopter Type | Usage Scenario | | | - | - | | Huawei Cloud Eye Service | Service provider | Monitors cloud services and resources | | Huawei Cloud IIoT | OSS project | Use openGemini to store devices data | | Huawei Cloud CloudScope | Service provider | Huawei Cloud serivce O&M | | Yinhehangtian | OSS project | Used for IT system O&M monitoring | | Databuff | OSS project | Used for cloud-native serivce O&M monitoring | | Yunnan Yuntianhua | OSS project | Used for Industrial manufacturing | | Kehua | OSS project | Stores monitoring data for smart electric energy solutions |
Project: KICS (Provisioning / Security & Compliance)
File: 0c82eae2-aca0-401f-93e4-fb37a0f9e5e8.md

title: SQL DB Instance Backup Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0c82eae2-aca0-401f-93e4-fb37a0f9e5e8 Query name: SQL DB Instance Backup Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Backup URL: Checks if backup configuration is enabled for all Cloud SQL Database instances<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="24 3 13 38" name: create a instance google.cloud.gcpsqlinstance: name: "{{ resource_name }}-2" region: us-central1 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a second instance google.cloud.gcpsqlinstance: name: "{{ resource_name }}-2" settings: tier: db-n1-standard-1 region: us-central1 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a third instance google.cloud.gcpsqlinstance: name: "{{ resource_name }}-2" settings: backup_configuration: binarylogenabled: yes tier: db-n1-standard-1 region: us-central1 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a forth instance google.cloud.gcpsqlinstance: name: "{{ resource_name }}-2" settings: backup_configuration: binarylogenabled: yes enabled: no tier: db-n1-standard-1 region: us-central1 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: create a instance google.cloud.gcpsqlinstance: name: '{{ resource_name }}-2' settings: backup_configuration: binarylogenabled: yes enabled: yes tier: db-n1-standard-1 region: us-central1 project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: CHANGELOG-v2022.12.24-rc.1.md

title: Changelog | KubeDB description: Changelog menu: docs_{{.version}}: identifier: changelog-kubedb-v2022.12.24-rc.1 name: Changelog-v2022.12.24-rc.1 parent: welcome weight: 20221224 product_name: kubedb menuname: docs{{.version}} sectionmenuid: welcome url: /docs/{{.version}}/welcome/changelog-v2022.12.24-rc.1/ aliases: /docs/{{.version}}/CHANGELOG-v2022.12.24-rc.1/ Revise PgBouncer api (#1002) Update Redis Root Username (#1010) Remove docker utils (#1008) Add API for ProxySQL UI-Server (#1003) Prepare for release v0.15.0-rc.1 (#127) Prepare for release v0.30.0-rc.1 (#690) Prepare for release v0.6.0-rc.1 (#53) Prepare for release v0.30.0-rc.1 (#619) Use go-containerregistry for image digest (#618) Prepare for release v2022.12.24-rc.1 (#580) Add MariaDB Version 10.10.2 (#579) Update crds for kubedb/apimachinery@7f6ffca9 (#578) Add support for PgBouncer 1.18.0 (#577) Add Redis Version 6.2.8 and 7.0.6 (#576) Prepare for release v0.1.0-rc.1 (#8) Use go-containerregistry for image digest (#7) Use kauth.NoServiceAccount when no sa is specified Fix Image digest detection (#6) Prepare for release v0.14.0-rc.1 (#190) Use go-containerregistry for image digest (#189) Prepare for release v0.10.0-rc.1 (#67) Prepare for release v0.23.0-rc.1 (#379) Prepare for release v0.23.0-rc.1 (#526) Use go-containerregistry for image digest (#525) Prepare for release v0.23.0-rc.1 (#514) Use go-containerregistry for image digest (#513) Prepare for release v0.8.0-rc.1 (#65) remove appeding singnal clusterstatusok (#64) Prepare for release v0.17.0-rc.1 (#399) Use kmodules image library for parsing image (#398) Add adminUserName as CommonName for PgBouncer (#394) Update deps Use go-containerregistry for image digest (#397) Fix evict api usage for k8s < 1.22 (#396) Prepare for release v0.17.0-rc.1 (#292) Use go-containerregistry for image digest (#291) Prepare for release v0.3.0-rc.1 (#24) Prepare for release v0.14.0-rc.1 (#106) Prepare for release v0.17.0-rc.1 (#253) Add authSecret & configSecret (#249) Use go-containerregistry for image digest (#252) Prepare for release v0.30.0-rc.1 (#617) Revert to k8s 1.25 client libraries Use go-containerregistry for image digest (#616) Prepare for release v0.30.0-rc.1 (#30) Prepare for release v0.17.0-rc.1 (#272) Fix Monitoring Port Issue (#271) Fix Validator Issue (#270) Use go-containerregistry for image digest (#268) Prepare for release v0.23.0-rc.1 (#441) Update Redis Root UserName (#440) Use go-containerregistry for image digest (#439) Prepare for release v0.9.0-rc.1 (#57) Prepare for release v0.17.0-rc.1 (#219) Prepare for release v0.6.0-rc.1 (#57) Prepare for release v0.15.0-rc.1 (#209) Update deps Proxysql UI server (#57) Prepare for release v0.6.0-rc.1 (#42)
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: bug.md

name: Bug Report about: Explain a defect discovered in Habitat labels: C-bug Hello - thanks for reporting an issue with Habitat. In order to help us troubleshoot the issue, please be sure to include the following information if applicable: [ ] The OS (including version) where you are running any of the Habitat commands. [ ] Debug/backtrace of the command you are trying to run. You can set the following environment variables before running the `hab` command to generate a trace: RUSTLOG=debug RUSTBACKTRACE=1 hab ... $env:RUSTLOG="debug"; $env:RUSTBACKTRACE=1; hab ... [ ] Current Habitat environment variables where the `hab` command or supervisor is running. These can be gathered using: env | grep HAB | grep -v HABAUTHTOKEN *DO NOT include `HAB_AUTH_TOKEN`* or any other sensitive information. More info on Habitat environment variables can be found . , please use the `env | grep ...` command specified above to include environment variables: [ ] a. before starting the studio [ ] b. inside the studio [ ] If this is a key related issue, please include the list of files (including user/group permissions) in `/hab/cache/keys` and `$HOME/.hab/cache/keys` via `ls -la`. ls -la /hab/cache/keys ls -la $HOME/.hab/cache.keys ls C:\hab\cache\keys
Project: Chef Infra (Provisioning / Automation & Configuration)
File: chef-apply.md

+++ title = "chef-apply (executable)" draft = false gh_repo = "chef-workstation" aliases = ["/ctlchefapply.html", "/ctlchefapply/"] [menu] [menu.workstation] title = "chef-apply (executable)" identifier = "chefworkstation/chefworkstationtools/ctlchef_apply.md chef-apply (executable)" parent = "chefworkstation/chefworkstation_tools" weight = 30 +++ chef-apply is an executable program that runs a single recipe from the command line: Is part of Chef Workstation A great way to explore resources Is NOT how Chef is run in production This command has the following syntax: ``` bash chef-apply nameofrecipe.rb ``` This tool has the following options: `-e RECIPETEXT`, `--execute RECIPETEXT` : Execute a resource using a string. `-l LEVEL`, `--log_level LEVEL` : The level of logging to be stored in a log file. `-s`, `--stdin` : Execute a resource using standard input. `-v`, `--version` : The Chef Infra Client version. `-W`, `--why-run` : Run the executable in why-run mode, which is a type of Chef Infra Client run that does everything except modify the system. Use why-run mode to understand why Chef Infra Client makes the decisions that it makes and to learn more about the current and proposed state of the system. `-h`, `--help` : Show help for the command. Run a recipe Run a recipe named `machinations.rb`: ``` bash chef-apply machinations.rb ``` Install Emacs Run: ``` bash sudo chef-apply -e "package 'emacs'" ``` Returns: ``` bash Recipe: (chef-apply cookbook)::(chef-apply recipe) package[emacs] action install install version 23.1-25.el6 of package emacs ``` Install nano Run: ``` bash sudo chef-apply -e "package 'nano'" ``` Returns: ``` bash Recipe: (chef-apply cookbook)::(chef-apply recipe) package[nano] action install install version 2.0.9-7.el6 of package nano ``` Install vim Run: ``` bash sudo chef-apply -e "package 'vim'" ``` Returns: ``` bash Recipe: (chef-apply cookbook)::(chef-apply recipe) package[vim] action install install version 7.2.411-1.8.el6 of package vim-enhanced ``` Rerun a recipe Run: ``` bash sudo chef-apply -e "package 'vim'" ``` Returns: ``` bash Recipe: (chef-apply cookbook)::(chef-apply recipe) package[vim] action install (up to date) ```
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. iOS] Version [e.g. 22] Additional context Add any other context about the problem here.