cwielenb/CNCF-Dataset huggingface dataset:
Project: YDB (App Definition and Development / Database)
File: system-requirements.md

This section provides recommendations for deploying {{ ydb-short-name }} clusters that are relevant regardless of the chosen deployment method (, , or ). The fault-tolerance requirements determine the necessary number of servers and disks. For more information, see . Processor (CPU)* A {{ ydb-short-name }} server can only run on x86-64 processors with AVX2 instruction support: Intel Haswell (4th generation) and later, AMD EPYC and later. The ARM architecture is currently not supported. RAM* We recommend using error-correcting code (ECC) memory to protect against hardware failures. Disk subsystem* A {{ ydb-short-name }} server can run on servers with any disk type (HDD/SSD/NVMe). However, we recommend using SSD/NVMe disks for better performance. {% include %} {{ ydb-short-name }} works with disk drives directly and does not use any filesystem to store data. Don't mount a file system or perform other operations with partitions used by {{ ydb-short-name }}. Also, avoid sharing the {{ ydb-short-name }}'s block device with the operating system and different processes, which can lead to significant performance degradation. Prefer to use physical local disk drives for {{ ydb-short-name }} instead of virtual or network storage devices. Remember that {{ ydb-short-name }} uses some disk space for internal needs when planning disk capacity. For example, on a medium-sized cluster of 8 nodes, you can expect approximately 100 GB to be consumed for a static group on the whole cluster. On a large cluster with more than 1500 nodes, this will be about 200 GB. There are also 25.6 GB of logs on each Pdisk and a system area on each Pdisk. Its size depends on the size of the Pdisk but is no less than 0.2 GB. A {{ ydb-short-name }} server can be run on servers with a Linux operating system, kernel 4.19 and higher, and libc 2.30. For example, Ubuntu 20.04, Debian 11, Fedora 34, or newer releases. {{ ydb-short-name }} uses the memory allocator. To make it efficient, Transparent Huge Pages and Memory overcommitment. If the server has more than 32 CPU cores, to increase {{ ydb-short-name }} performance, run each dynamic node in a separate taskset/cpuset of 10 to 32 cores. For example, in the case of 128 CPU cores a viable approach would be to run four 32-CPU dynamic nodes, each in a dedicated taskset. MacOS and Windows operating systems are currently unsupported for running production {{ ydb-short-name }} servers. However, running {{ ydb-short-name }} in a on them is acceptable for development and functional testing.
Project: Apollo (Provisioning / Automation & Configuration)
File: portal-how-to-enable-webhook-notification.md

Starting with version 1.8.0, Apollo has added webhook support, which will be triggered to send you a message when your configuration is released. The configuration items are stored in the table named ApolloPortalDB.ServerConfig. You may also config them in `Admin Tools - System Configuration` page. The configuration changes will take effect within one minute. webhook.supported.envs The environment lists to enable webhook support. Multiple environments should be separated by commas, e.g., ``` DEV, FAT, UAT, PRO ``` config.release.webhook.service.url Config the url that receives HTTP post request sent by webhook for notifying. Multiple urls should be separated by commas, e.g., ``` http://www.xxx.com/webhook1,http://www.xxx.com/webhook2 ``` URL parameters parameter name | parameter annotation | env | env of the configuration to be released Request body sample ```json { "appId": "", // appId "clusterName": "", // cluster "namespaceName": "", // namespace "operator": "", // modifier "releaseId": 2, // release id "releaseTitle": "", // release title "releaseComment": "", // release Comment "releaseTime": "", // release time eg2020-01-01T00:00:00.000+0800 "configuration": [ { // all configurations to be released; also applys to gray release "firstEntity": "", // key of configuration "secondEntity": "" // value of configuration } ], "isReleaseAbandoned": false, "previousReleaseId": 1, // releaseId of latest formal release "operation": // 0-normal release 1-rollabck 2-gray release 4-full release "operationContext": { // property setting for operation "isEmergencyPublish": true/false, // emergercy release or not "rules": [ { // rules for gray release "clientAppId": "", // appId "clientIpList": [ "10.0.0.2", "10.0.0.3" ] // IP lists } ], "branchReleaseKeys": [ "", "" ] // key of Gray Release } } ```
Project: ArangoDB (App Definition and Development / Database)
File: app-map-tidylib.md

+++ title = "Mapping the HTMLTidy library into the Application" weight = 45 +++ Once again, we create a custom STL exception type to represent failure from the HTMLTidy library. We also create an `app` namespace wrapper for the C `tidy_html()` function which is more C++ friendly. {{% snippet "finale.cpp" "appmaptidylib" %}}
Project: ShardingSphere (App Definition and Development / Database)
File: create-default-shadow-algorithm.en.md

+++ title = "CREATE DEFAULT SHADOW ALGORITHM" weight = 4 +++ The `CREATE DEFAULT SHADOW ALGORITHM` syntax is used to create a default shadow algorithm. {{< tabs >}} {{% tab name="Grammar" %}} ```sql CreateDefaultShadowAlgorithm ::= 'CREATE' 'DEFAULT' 'SHADOW' 'ALGORITHM' ifNotExists? shadowAlgorithm ifNotExists ::= 'IF' 'NOT' 'EXISTS' shadowAlgorithm ::= 'TYPE' '(' 'NAME' '=' algorithmType ',' propertiesDefiinition ')' algorithmType ::= string propertiesDefinition ::= 'PROPERTIES' '(' key '=' value (',' key '=' value)* ')' key ::= string value ::= literal ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `algorithmType` currently supports `VALUEMATCH`, `REGEXMATCH` and `SQL_HINT`; `ifNotExists` clause is used for avoid `Duplicate default shadow algorithm` error. Create default shadow algorithm ```sql CREATE DEFAULT SHADOW ALGORITHM TYPE(NAME="SQL_HINT"); ``` Create default shadow algorithm with `ifNotExist` clause ```sql CREATE DEFAULT SHADOW ALGORITHM IF NOT EXISTS TYPE(NAME="SQL_HINT"); ``` `CREATE`, `DEFAULT`, `SHADOW`, `ALGORITHM`, `TYPE`, `NAME`, `PROPERTIES`
Project: userver (App Definition and Development / Streaming & Messaging)
File: build_userver.md

Usually there's no need to build userver itself. Refer to @ref scripts/docs/en/userver/tutorial/build.md section to make a service from a template and build it. If there's a strong need to build the userver and run its tests, then: Download and extract the latest release from https://github.com/userver-framework/userver ``` bash git clone git@github.com:userver-framework/userver.git cd userver ``` Install the build dependencies from @ref scripts/docs/en/userver/tutorial/build.md Build the userver: ``` bash mkdir build_release cd build_release cmake -DCMAKEBUILDTYPE=Release .. # Adjust with flags from "Configure and Build" section cmake --build . -j$(nproc) ``` Run tests via `ulimit -n 4096 && ctest -V` Alternatively you could use a docker container with all the build dependencies installed from @ref scripts/docs/en/userver/tutorial/build.md If you need to edit or make your own docker image with custom configuration, read about it at @ref scripts/docker/Readme.md. @anchor userver_conan @note conan must have version >= 1.51, but < 2.0 Thanks to Open-Source community we have Conan support. You must run the following in the userver directory: ``` conan profile new --detect default && conan profile update settings.compiler.libcxx=libstdc++11 default conan create . --build=missing -pr:b=default -tf conan/test_package/ ``` Make sure to pass flags corresponding to the desired userver libraries, e.g. `--with_grpc=1` Now you can use userver as conan package and build it in your services: ```cmake targetlinklibraries(${PROJECT_NAME} PUBLIC userver::grpc) ``` @see @ref userver_libraries @htmlonly <div class="bottom-nav"> @endhtmlonly @ref scripts/docs/en/userver/driver_guide.md | @ref scripts/docs/en/userver/publications.md @htmlonly </div> @endhtmlonly
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_restore.md

title: kbcli cluster restore Restore a new cluster from backup. ``` kbcli cluster restore [flags] ``` ``` kbcli cluster restore new-cluster-name --backup backup-name ``` ``` --backup string Backup name -h, --help help for restore --restore-to-time string point in time recovery(PITR) --volume-restore-policy string the volume claim restore policy, supported values: [Serial, Parallel] (default "Parallel") ``` ``` --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 ``` - Cluster command.
Project: ClickHouse (App Definition and Development / Database)
File: clickhouse-compressor.md

slug: /ru/operations/utilities/clickhouse-compressor Simple program for data compression and decompression in ClickHouse way. Compress data with LZ4: ``` $ ./clickhouse-compressor < inputfile > outputfile ``` Decompress data from LZ4 format: ``` $ ./clickhouse-compressor --decompress < inputfile > outputfile ``` Compress data with ZSTD at level 5: ``` $ ./clickhouse-compressor --codec 'ZSTD(5)' < inputfile > outputfile ``` Compress data with Delta of four bytes and ZSTD level 10. ``` $ ./clickhouse-compressor --codec 'Delta(4)' --codec 'ZSTD(10)' < inputfile > outputfile ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: memcachedDeploymentSizeUndesired.md

MemcachedDeploymentSizeUndesired is triggered when the number of available <code>memcached-sample</code> replicas doesn't match the requested configuration. Unavailability of distributed memory object caching system in the cluster. Check memcached-sample's pod namespace: <code>export NAMESPACE="$(kubectl get deployment -A | grep memcached-sample | awk '{print $1}')"</code> Observe the status of the memcached-sample deployment: <code>kubectl get deploy memcached-sample -n $NAMESPACE -o yaml</code> Observe the logs of the memcached manager pod, to see why it cannot create the memcached-sample pods. <code>kubectl get logs <memcached-operator-controller-manager-pod> -n memcached-operator-system</code> There can be several reasons. Like: Node resource exhaustion Not enough memory on the cluster Nodes are down Try to identify the root cause and fix it.
Project: Foreman (Provisioning / Automation & Configuration)
File: PULL_REQUEST_TEMPLATE.md

<! Thank you for contributing to The Foreman, please read the , in short: Reference the issue via `Fixes #1234` in the commit message Prefer present-tense, imperative-style commit messages Mark all strings for translation, see [1] Suggest prerequisites for testing and testing scenarios following example above. Prepend `[WIP]` for work in progress to prevent bots from triggering actions Be patient, we will do our best to take a look as soon as we can Explain the purpose of the PR, attach screenshots if applicable List all prerequisites for testing (e.g. VMware cluster, two smart proxies...) Reviewers often use extensive list of items to check, have a look prior submitting [2] Be nice and respectful 1: https://projects.theforeman.org/projects/foreman/wiki/Translating#Translating-for-developers 2: https://github.com/theforeman/foreman/blob/develop/developerdocs/prreview.asciidoc -->
Project: ClickHouse (App Definition and Development / Database)
File: nullable.md

slug: /en/sql-reference/data-types/nullable sidebar_position: 44 sidebar_label: Nullable(T) Allows to store special marker () that denotes missing value alongside normal values allowed by `T`. For example, a `Nullable(Int8)` type column can store `Int8` type values, and the rows that do not have a value will store `NULL`. `T` cant be any of the composite data types , and but composite data types can contain `Nullable` type values, e.g. `Array(Nullable(Int8))`. A `Nullable` type field cant be included in table indexes. `NULL` is the default value for any `Nullable` type, unless specified otherwise in the ClickHouse server configuration. To store `Nullable` type values in a table column, ClickHouse uses a separate file with `NULL` masks in addition to normal file with values. Entries in masks file allow ClickHouse to distinguish between `NULL` and a default value of corresponding data type for each table row. Because of an additional file, `Nullable` column consumes additional storage space compared to a similar normal one. :::note Using `Nullable` almost always negatively affects performance, keep this in mind when designing your databases. ::: It is possible to find `NULL` values in a column by using `null` subcolumn without reading the whole column. It returns `1` if the corresponding value is `NULL` and `0` otherwise. Example Query: ``` sql CREATE TABLE nullable (`n` Nullable(UInt32)) ENGINE = MergeTree ORDER BY tuple(); INSERT INTO nullable VALUES (1) (NULL) (2) (NULL); SELECT n.null FROM nullable; ``` Result: ``` text n.null 0 1 0 1 ``` ``` sql CREATE TABLE t_null(x Int8, y Nullable(Int8)) ENGINE TinyLog ``` ``` sql INSERT INTO t_null VALUES (1, NULL), (2, 3) ``` ``` sql SELECT x + y FROM t_null ``` ``` text plus(x, y) 5 ```
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_drop_type.md

title: DROP TYPE statement [YSQL] headerTitle: DROP TYPE linkTitle: DROP TYPE description: Use the DROP TYPE statement to remove a user-defined type from the database. menu: v2.18: identifier: ddldroptype parent: statements type: docs Use the `DROP TYPE` statement to remove a user-defined type from the database. {{%ebnf%}} drop_type {{%/ebnf%}} Specify the name of the user-defined type to drop. Simple example ```plpgsql yugabyte=# CREATE TYPE feature_struct AS (id INTEGER, name TEXT); yugabyte=# DROP TYPE feature_struct; ``` `IF EXISTS` example ```plpgsql yugabyte=# DROP TYPE IF EXISTS feature_shell; ``` `CASCADE` example ```plpgsql yugabyte=# CREATE TYPE feature_enum AS ENUM ('one', 'two', 'three'); yugabyte=# CREATE TABLE featuretabenum (featurecol featureenum); yugabyte=# DROP TYPE featuretabenum CASCADE; ``` `RESTRICT` example ```plpgsql yugabyte=# CREATE TYPE feature_range AS RANGE (subtype=INTEGER); yugabyte=# CREATE TABLE featuretabrange (featurecol featurerange); yugabyte=# -- The following should error: yugabyte=# DROP TYPE feature_range RESTRICT; yugabyte=# DROP TABLE featuretabrange; yugabyte=# DROP TYPE feature_range RESTRICT; ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: SDK-002-java-jdk-versions.md

Accepted Dapr offers a Java SDK. Java 11 is the latest LTS version. Java 8 is the previous LTS version but still the mainly used version by the Java community in 2019. What should be the minimum Java version supported by Dapr's Java SDK? See https://github.com/dapr/java-sdk/issues/17 Java 8 should be the minimum version supported for Dapr's Java SDK. Java 11 should be used in samples and user documentation to encourage adoption. Java 8's commercial support ends in 2022. Dapr's Java SDK shoud migrate to Java 11 prior to that. The timeline still not decided. Customers running with Java 7 or below cannot use Dapr's Java SDK. Customers running with Java 8 are still supported, even through Java 11 is the recommended version. Modern language features will not be available in Dapr's Java SDK code. Modern JVM features can still be used since the Java 11 JVM can run Java 8 bytecode.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-ddl-create-table.md

layout: global title: CREATE TABLE displayTitle: CREATE TABLE 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. `CREATE TABLE` statement is used to define a table in an existing database. The CREATE statements:
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_set_role.md

title: SET ROLE statement [YSQL] headerTitle: SET ROLE linkTitle: SET ROLE description: Use the SET ROLE statement to set the current user of the current session to be the specified user. menu: v2.18: identifier: dclsetrole parent: statements type: docs Use the `SET ROLE` statement to set the current user of the current session to be the specified user. {{%ebnf%}} set_role, reset_role {{%/ebnf%}} The specified `role_name` must be a role that the current session user is a member of. Superusers can set to any role. Once the role is set to `role_name`, any further SQL commands will use the privileges available to that role. To reset the role back to current user, `RESET ROLE` or `SET ROLE NONE` can be used. Change to new role John. ```plpgsql yugabyte=# select sessionuser, currentuser; sessionuser | currentuser --+-- yugabyte | yugabyte (1 row) yugabyte=# set role john; SET yugabyte=# select sessionuser, currentuser; sessionuser | currentuser --+-- yugabyte | john (1 row) ``` Changing to new role assumes the privileges available to that role. ```plpgsql yugabyte=# select sessionuser, currentuser; sessionuser | currentuser --+-- yugabyte | yugabyte (1 row) yugabyte=# create database db1; CREATE DATABASE yugabyte=# set role john; SET yugabyte=# select sessionuser, currentuser; sessionuser | currentuser --+-- yugabyte | john (1 row) yugabyte=# create database db2; ERROR: permission denied to create database ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.8.md

RabbitMQ `3.9.8` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports the latest Erlang 24 version, 24.1.2 at the time of release. has more details on Erlang version requirements for RabbitMQ. Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and a more consistent release schedule. When the mandatory flag was used when publishing to classic queues, but publisher confirms were not, channels memory usage would grow indefinitely. GitHub issue: `rabbitmq-diagnostics memory_breakdown` failed to read memory of connection reader, writer and channel processes. GitHub issue: In some environments, Stream replicas advertised IP addresses that could not be reached by cluster peers (eg. IP addresses behind a NAT in a Docker deployment). RabbitMQ node hostnames are now advertised as well so that other peers can resolve them to get an externally visible IP address. GitHub issue: More data is exposed via the `GET /metrics/detailed` endpoint. GitHub issue: When setting topic permissions, the list of exchanges in the UI now honors the currently selected virtual host. Contributed by @LuisCusihuaman. GitHub issue: The plugin now logs more details for failed AWS API requests. Contributed by @tvhong-amazon (AWS) GitHub issue: STOMP-over-WebSockets connections now can consume from . GitHub issue: Osiris was To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.8.tar.xz` instead of the source tarball produced by GitHub.
Project: KICS (Provisioning / Security & Compliance)
File: 2059155b-27fd-441e-b616-6966c468561f.md

title: API Gateway X-Ray Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2059155b-27fd-441e-b616-6966c468561f Query name: API Gateway X-Ray Disabled Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: API Gateway should have X-Ray Tracing enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8 12" name: Setup AWS API Gateway setup on AWS and deploy API definition community.aws.awsapigateway: swaggerfile: myapi.yml stage: production cache_enabled: true cache_size: '1.6' tracing_enabled: false endpoint_type: EDGE state: present name: Update API definition to deploy new version community.aws.awsapigateway: api_id: 'abc123321cba' swaggerfile: myapi.yml deploy_desc: Make auth fix available. cache_enabled: true cache_size: '1.6' endpoint_type: EDGE state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: Setup AWS API Gateway setup on AWS and deploy API definition community.aws.awsapigateway: swaggerfile: myapi.yml stage: production cache_enabled: true cache_size: '1.6' tracing_enabled: true endpoint_type: EDGE state: present ```
Project: Redpanda (App Definition and Development / Streaming & Messaging)
File: SECURITY.md

Official Redpanda Security Policy can be found on As with any complex system, it is certain that bugs will be found, some of them security-relevant. If you find a security bug please report it privately via email to . We will fix the issue as soon as possible and coordinate a release date with you. You will be able to choose if you want public acknowledgement of your effort and if you want to be mentioned by name. The public disclosure date is agreed between the Redpanda Team and the bug submitter. We prefer to fully disclose the bug as soon as possible, but only after a mitigation or fix is available. We will ask for delay if the bug or the fix is not yet fully understood or the solution is not tested to our standards yet. While there is no fixed time frame for fix & disclosure, we will try our best to be quick and do not expect to need the usual 90 days most companies ask or. For a vulnerability with a straightforward mitigation, we expect report date to disclosure date to be on the order of 7 days.