cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_alert.md

title: kbcli alert Manage alert receiver, include add, list and delete receiver. ``` -h, --help help for alert ``` ``` --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 ``` - Add alert receiver, such as email, slack, webhook and so on. - Set smtp server config - Delete alert receiver. - List all alert receivers. - List alert smtp servers config.
Project: Distribution (Provisioning / Container Registry)
File: inmemory.md

description: Explains how to use the in-memory storage drivers keywords: registry, service, driver, images, storage, in-memory title: In-memory storage driver (testing only) For purely tests purposes, you can use the `inmemory` storage driver. This driver is an implementation of the `storagedriver.StorageDriver` interface which uses local memory for object storage. If you would like to run a registry from volatile memory, use the on a ramdisk. {{< hint type=important >}} This storage driver does not persist data across runs. This is why it is only suitable for testing. Never use this driver in production. {{< /hint >}} None
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-container-exists.1.md

% podman-container-exists 1 podman\-container\-exists - Check if a container exists in local storage podman container exists [options] container podman container exists checks if a container exists in local storage. The container ID or name is used as input. Podman returns an exit code of `0` when the container is found. A `1` is returned otherwise. An exit code of `125` indicates there was an issue accessing the local storage. Check for external containers as well as Podman containers. These external containers are generally created via other container technology such as `Buildah` or `CRI-O`.\ The default is false. -h, --help Prints usage statement.\ The default is false. Check if a container called "webclient" exists in local storage. Here, the container does exist. ``` $ podman container exists webclient $ echo $? 0 ``` Check if a container called "webbackend" exists in local storage. Here, the container does not exist. ``` $ podman container exists webbackend $ echo $? 1 ``` Check if a container called "ubi8-working-container" created via Buildah exists in local storage. Here, the container does not exist. ``` $ podman container exists --external ubi8-working-container $ echo $? 1 ``` November 2018, Originally compiled by Brent Baude <bbaude@redhat.com>
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 06_basic_schema.md

Prompt: What are schemas in Apache Beam? Response: A is a language-independent type definition for a `PCollection`. The schema defines elements of that `PCollection` as an ordered list of named fields. In many cases, the element type in a `PCollection` has a structure that can be introspected. Some examples are JSON, Protocol Buffer, Avro, and database row objects. All of these formats can be converted to Beam Schemas. To take advantage of schemas, your `PCollection` objects must have a schema attached. Often, the source itself attaches a schema to the `PCollection`. Although schemas are language-independent, they're designed to embed naturally into the Beam SDK programming languages. This feature lets you continue while leveraging the advantage of having Beam understand your element schemas. Beam provides a collection of that operate on schemas. For an example, see . The following list includes key capabilities provided by schema transforms: field selection grouping and aggregation join operations filtering data adding and removing fields renaming fields type conversion enhanced ParDo functionality For more information about schemas and the Apache Beam best practices when working with structured data, see .
Project: YugabyteDB (App Definition and Development / Database)
File: having_clause.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="245" height="35" viewbox="0 0 245 35"><path class="connector" d="M0 22h15m68 0h10m137 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="68" height="25" rx="7"/><text class="text" x="25" y="22">HAVING</text><a xlink:href="../../../syntaxresources/grammardiagrams#boolean-expression"><rect class="rule" x="93" y="5" width="137" height="25"/><text class="text" x="103" y="22">boolean_expression</text></a><polygon points="241,29 245,29 245,15 241,15" style="fill:black;stroke-width:0"/></svg>
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: cpu-period.md

Set the CPU period for the Completely Fair Scheduler (CFS), which is a duration in microseconds. Once the container's CPU quota is used up, it will not be scheduled to run until the current period ends. Defaults to 100000 microseconds. On some systems, changing the resource limits may not be allowed for non-root users. For more details, see https://github.com/containers/podman/blob/main/troubleshooting.md#26-running-containers-with-resource-limits-fails-with-a-permissions-error This option is not supported on cgroups V1 rootless systems.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.0.23.7.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | DFS Scalability: Incremental block reports* WARNING: No release note provided for this change. | Major | Killing an unassigned task attempt causes the job to fail* Handle TaskAttempt diagnostic updates while in the NEW and UNASSIGNED states. | Trivial | Add missing fields to FIleStatus.toString* Update FileStatus.toString to include missing fields
Project: OpenYurt (Provisioning / Automation & Configuration)
File: bug-report.md

name: Bug Report about: Create a report to help us improve title: "[BUG]" labels: kind/bug <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--> What happened: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: OpenYurt version: Kubernetes version (use `kubectl version`): OS (e.g: `cat /etc/os-release`): Kernel (e.g. `uname -a`): Install tools: Others: others /kind bug
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.3.1.3.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | DelegationTokenAuthenticationFilter get wrong doAsUser since it does not decode URL* Fix DelegationTokenAuthentication filter for incorrectly double encode doAs user parameter. | Major | Service AM support for decommissioning component instances* Component instance number is not linear increment when decommission feature is used. Application with assumption of linear increment component instance number maybe impacted by introduction of this feature. | Major | Serial number in BlockTokenSecretManager could overlap between different namenodes* NameNodes rely on independent block token key ranges to communicate block token identities to DataNodes and clients in a way that does not create conflicts between the tokens issued by multiple NameNodes. HDFS-6440 introduced the potential for overlaps in key ranges; this fixes the issue by creating 64 possible key ranges that NameNodes assign themselves to, allowing for up to 64 NameNodes to run safely. This limitation only applies within a single Namespace; there may be more than 64 NameNodes total spread among multiple federated Namespaces. | Minor | NetUtils#canonicalizeHost gives different value for same host* The above patch will resolve the race condition | Blocker | Failed to load image from FSImageFile when downgrade from 3.x to 2.x* During a rolling upgrade from Hadoop 2.x to 3.x, NameNode cannot persist erasure coding information, and therefore a user cannot start using erasure coding feature until finalize is done.
Project: StarRocks (App Definition and Development / Database)
File: System_limit.md

displayed_sidebar: "English" This topic describes the rules and limits that apply when you use StarRocks. StarRocks uses the MySQL protocol for communication. You can connect to the StarRocks cluster via a MySQL client or JDBC. We recommend that you use a MySQL client whose version is 5.1 or later. Versions earlier than 5.1 do not support usernames that are longer than 16 characters. Naming conventions for objects such as catalogs, databases, tables, views, partitions, columns, indexes, usernames, roles, repositories, resources, storage volumes, and pipes: The name can only consist of digits (0-9), letters (a-z or A-Z), and underscores (\_). Usernames can be all digits. The name can start with a letter or an underscore (\_). The name cannot exceed 64 characters in length, among which: Database name cannot exceed 256 characters. Table name and column name cannot exceed 1024 characters. Username cannot exceed 128 characters. Column name (column alias), partition name, and index name are not case-sensitive. Other names are case-sensitive. Naming conventions for labels: You can specify the label of a job when you load data. The label name can consist of digits (0-9), letters (a-z or A-Z), and underscores (\_), and cannot exceed 128 characters in length. The label name has no requirement for the starting character. When you create a table, the key column cannot be of the FLOAT or DOUBLE type. You can use the DECIMAL type to represent decimals. The maximum length of a VARCHAR value varies in different versions: In versions earlier than StarRocks 2.1, the length ranges from 1 to 65533 bytes. [Preview] In StarRocks 2.1 and later versions, the length ranges from 1 to 1048576 bytes. Maximum length of a VARCHAR value = Maximum row size (1048578 bytes) - Length prefix (2 bytes). The length prefix indicates the number of bytes in the value. The default length is 1 byte. StarRocks supports only UTF-8 encoding, not GBK. StarRocks does not support modifying column names in tables. StarRocks does not support modifying the table types of an existing table. For example, you cannot change a Duplicate Key table to a Primary Key table. You must create a new table. By default, a query can be nested with a maximum of 10,000 subqueries, which is controlled by the FE parameter `exprchildrenlimit`.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_onprem_instance-types_remove.md

Delete instance type of a YugabyteDB Anywhere on-premises provider Delete instance types of a YugabyteDB Anywhere on-premises provider ``` yba provider onprem instance-types remove [flags] ``` ``` --instance-type-name string [Required] Instance type name. -f, --force [Optional] Bypass the prompt for non-interactive usage. -h, --help help for remove ``` ``` -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, instance-types and nodes. -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 YugabyteDB Anywhere onprem instance types
Project: KICS (Provisioning / Security & Compliance)
File: 5ef61c88-bbb4-4725-b1df-55d23c9676bb.md

title: Cloud DNS Without DNSSEC hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5ef61c88-bbb4-4725-b1df-55d23c9676bb Query name: Cloud DNS Without DNSSEC Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: DNSSEC must be enabled for Cloud DNS<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10" // comment // comment // comment // comment resource "googlednsmanaged_zone" "positive1" { name = "foobar" dns_name = "foo.bar." dnssec_config { state = "off" non_existence = "nsec3" } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlednsmanaged_zone" "negative1" { name = "foobar" dns_name = "foo.bar." dnssec_config { state = "on" non_existence = "nsec3" } } ```
Project: YugabyteDB (App Definition and Development / Database)
File: drop_owned,role_specification.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="506" height="100" viewbox="0 0 506 100"><path class="connector" d="M0 52h15m53 0h10m67 0h10m35 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h54m24 0h54q5 0 5 5v20q0 5-5 5m-5 0h50m77 0h22m-109 25q0 5 5 5h5m79 0h5q5 0 5-5m-104-25q5 0 5 5v33q0 5 5 5h89q5 0 5-5v-33q0-5 5-5m5 0h15"/><polygon points="0,59 5,52 0,45" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="35" width="53" height="25" rx="7"/><text class="text" x="25" y="52">DROP</text><rect class="literal" x="78" y="35" width="67" height="25" rx="7"/><text class="text" x="88" y="52">OWNED</text><rect class="literal" x="155" y="35" width="35" height="25" rx="7"/><text class="text" x="165" y="52">BY</text><rect class="literal" x="269" y="5" width="24" height="25" rx="7"/><text class="text" x="279" y="22">,</text><a xlink:href="#role-specification"><rect class="rule" x="220" y="35" width="122" height="25"/><text class="text" x="230" y="52">role_specification</text></a><rect class="literal" x="392" y="35" width="77" height="25" rx="7"/><text class="text" x="402" y="52">CASCADE</text><rect class="literal" x="392" y="65" width="79" height="25" rx="7"/><text class="text" x="402" y="82">RESTRICT</text><polygon points="502,59 506,59 506,45 502,45" style="fill:black;stroke-width:0"/></svg> <svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="188" height="95" viewbox="0 0 188 95"><path class="connector" d="M0 22h35m84 0h54m-148 25q0 5 5 5h5m118 0h5q5 0 5-5m-143-25q5 0 5 5v50q0 5 5 5h5m116 0h7q5 0 5-5v-50q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><a xlink:href="../../../syntaxresources/grammardiagrams#role-name"><rect class="rule" x="35" y="5" width="84" height="25"/><text class="text" x="45" y="22">rolename</text></a><rect class="literal" x="35" y="35" width="118" height="25" rx="7"/><text class="text" x="45" y="52">CURRENTUSER</text><rect class="literal" x="35" y="65" width="116" height="25" rx="7"/><text class="text" x="45" y="82">SESSION_USER</text><polygon points="184,29 188,29 188,15 184,15" style="fill:black;stroke-width:0"/></svg>
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-describe-database.md

layout: global title: DESCRIBE DATABASE displayTitle: DESCRIBE DATABASE license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. `DESCRIBE DATABASE` statement returns the metadata of an existing database. The metadata information includes database name, database comment, and database location on the filesystem. If the optional `EXTENDED` option is specified, it returns the basic metadata information along with the database properties. The `DATABASE` and `SCHEMA` are interchangeable. ```sql { DESC | DESCRIBE } DATABASE [ EXTENDED ] db_name ``` db_name* Specifies a name of an existing database or an existing schema in the system. If the name does not exist, an exception is thrown. ```sql -- Create employees DATABASE CREATE DATABASE employees COMMENT 'For software companies'; -- Describe employees DATABASE. -- Returns Database Name, Description and Root location of the filesystem -- for the employees DATABASE. DESCRIBE DATABASE employees; +-+--+ |databasedescriptionitem| databasedescriptionvalue| +-+--+ | Database Name| employees| | Description| For software companies| | Location|file:/Users/Temp/employees.db| +-+--+ -- Create employees DATABASE CREATE DATABASE employees COMMENT 'For software companies'; -- Alter employees database to set DBPROPERTIES ALTER DATABASE employees SET DBPROPERTIES ('Create-by' = 'Kevin', 'Create-date' = '09/01/2019'); -- Describe employees DATABASE with EXTENDED option to return additional database properties DESCRIBE DATABASE EXTENDED employees; +-++ |databasedescriptionitem| databasedescriptionvalue| +-++ | Database Name| employees| | Description| For software companies| | Location| file:/Users/Temp/employees.db| | Properties|((Create-by,kevin), (Create-date,09/01/2019))| +-++ -- Create deployment SCHEMA CREATE SCHEMA deployment COMMENT 'Deployment environment'; -- Describe deployment, the DATABASE and SCHEMA are interchangeable, their meaning are the same. DESC DATABASE deployment; +-++ |databasedescriptionitem|databasedescriptionvalue | +-++ | Database Name| deployment| | Description| Deployment environment| | Location|file:/Users/Temp/deployment.db| +-++ ```
Project: StarRocks (App Definition and Development / Database)
File: SHOW_AUTHENTICATION.md

displayed_sidebar: "English" Displays the authentication information of the current user or all users in the current cluster. :::tip All users have the privilege to view their own authentication information. Only users with the `user_admin` role can view the authentication information of all users or the authentication information of specified users. ::: ```SQL SHOW [ALL] AUTHENTICATION [FOR USERNAME] ``` | Parameter | Required | Description | | - | | | | ALL | No | If this keyword is specified, the authentication information of all users in the current cluster is returned. If this keyword is not specified, only the authentication information of the current user is returned. | | USERNAME | No | If this parameter is specified, the authentication information of a specified user can be viewed. If this parameter is not specified, only the authentication information of the current user can be viewed. | ```SQL ++-+-+-+ | UserIdentity | Password | AuthPlugin | UserForAuthPlugin | ++-+-+-+ ``` | Field | Description | | -- | | | UserIdentity | The user identity. | | Password | Whether a password is used to log in to the StarRocks cluster.<ul><li>`Yes`: A password is used.</li><li>`No`: No password is used.</li></ul> | | AuthPlugin | The interface that is used for authentication. Valid values: `MYSQLNATIVEPASSWORD` and `AUTHENTICATIONLDAPSIMPLE`. If no interface is used, `NULL` is returned. | | UserForAuthPlugin | The name of the user using the LDAP or Kerberos authentication. If no authentication is used, `NULL` is returned. | Example 1: Display the authentication information of the current user. ```Plain SHOW AUTHENTICATION; +--+-++-+ | UserIdentity | Password | AuthPlugin | UserForAuthPlugin | +--+-++-+ | 'root'@'%' | No | NULL | NULL | +--+-++-+ ``` Example 2: Display the authentication information of all users in the current cluster. ```Plain SHOW ALL AUTHENTICATION; ++-+-+-+ | UserIdentity | Password | AuthPlugin | UserForAuthPlugin | ++-+-+-+ | 'root'@'%' | Yes | NULL | NULL | | 'chelsea'@'%' | No | AUTHENTICATIONLDAPSIMPLE | NULL | ++-+-+-+ ``` Example 3: Display the authentication information of a specified user. ```Plain SHOW AUTHENTICATION FOR root; +--+-++-+ | UserIdentity | Password | AuthPlugin | UserForAuthPlugin | +--+-++-+ | 'root'@'%' | Yes | NULL | NULL | +--+-++-+ ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.7.11.3-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix the number of threads used in `GLOBAL IN` subquery (it was executed in single threads since bugfix). (). Backported in : Fix segfault while inserting into column with type LowCardinality(Nullable) in Avro input format. (). Do not add const group by key for query with only having. (). Merging (). Fix terminate on uncaught exception ().
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-12-2023-02-20-10_90f0d049.md

timestamp: "2023-10-12 02:20:33 UTC Thu" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.22.2" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"