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

If the value of the `YDBUSER` or `YDBPASSWORD` environment variable is set, the username and password based authentication mode is used. The username is read from the `YDBUSER` variable. If it is not set, an error saying `User password was provided without user name` is returned. The password is read from the `YDBPASSWORD` variable. If it is not set, then, depending on whether the `--no-password` command-line option is specified, either an empty password is used or a password is requested interactively.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.6.md

RabbitMQ `3.9.6` 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.0.5 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. TLS information delivered in header is now attached to connection metrics as if it was provided by a non-proxying client. GitHub issues: , contributed by @prefiks, sponsored by CloudAMQP `maxmessagesize` had a one-off error in the validator. GitHub issue: `mirroringsyncbatch_size` was incorrectly validated as if it represented batch size in bytes. It represents batch size in number of messages, so the new default hard cap is now 1M (a very high number that's impractical) GitHub issue: Offset parameters were not stored correctly in some cases. GitHub issue: , contributed by @korsmakolnikov Partitions list order is now stable. GitHub issue: When stream clients close connections abruptly, publisher and consumer metrics get cleaned up correctly. GitHub issue: Stream publishers are now listed on the individual stream page. GitHub issue: Counters have been added to the tiles of several sections on detail pages. GitHub issue: Osiris was Ranch was To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.6.tar.xz` instead of the source tarball produced by GitHub.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: bond.md

+++ title = "bond resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "bond" identifier = "inspec/resources/os/bond.md bond resource" parent = "inspec/resources/os" +++ Use the `bond` Chef InSpec audit resource to test a logical, bonded network interface (i.e. "two or more network interfaces aggregated into a single, logical network interface"). On Linux platforms, any value in the `/proc/net/bonding` directory may be tested. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `bond` resource block declares a bonded network interface, and then specifies the properties of that bonded network interface to be tested: describe bond('name') do it { should exist } end where `'name'` is the name of the bonded network interface `{ should exist }` is a valid matcher for this resource The `content` property returns the contents in the file that defines the bonded network interface. The values of the `content` property are arbitrary. its('content') { should match('value') } The `interfaces` property tests if the named secondary interfaces are available. its('interfaces') { should eq ['eth0', 'eth1', ...] } The `mode` property returns the Bonding Mode. its('mode') { should eq 'IEEE 802.3ad Dynamic link aggregation' } The `params` property returns arbitrary parameters for the bonded network interface. its('params') { should eq 'value' } describe bond('bond0') do it { should exist } it { should have_interface 'eth0' } end describe bond('bond0') do its('mode') { should eq 'IEEE 802.3ad Dynamic link aggregation' } its('params') { should have_key 'Transmit Hash Policy' } its('params') { should include 'Transmit Hash Policy' => 'layer3+4 (1)' } its('params') { should have_key 'MII Status' } its('params') { should include 'MII Status' => 'up' } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `exist` matcher tests if the bonded network interface is available: it { should exist } The `have_interface` matcher tests if the bonded network interface has one (or more) secondary interfaces: it { should have_interface }
Project: ClickHouse (App Definition and Development / Database)
File: exchange.md

slug: /en/sql-reference/statements/exchange sidebar_position: 49 sidebar_label: EXCHANGE Exchanges the names of two tables or dictionaries atomically. This task can also be accomplished with a query using a temporary name, but the operation is not atomic in that case. :::note The `EXCHANGE` query is supported by the database engine only. ::: Syntax ```sql EXCHANGE TABLES|DICTIONARIES [db0.]nameA AND [db1.]nameB [ON CLUSTER cluster] ``` Exchanges the names of two tables. Syntax ```sql EXCHANGE TABLES [db0.]tableA AND [db1.]tableB [ON CLUSTER cluster] ``` Exchanges the names of two dictionaries. Syntax ```sql EXCHANGE DICTIONARIES [db0.]dictA AND [db1.]dictB [ON CLUSTER cluster] ``` See Also
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.27.md

RabbitMQ `3.7.27` is a maintenance release. It contains a couple of backports from the `3.8.x` branch. RabbitMQ `3.7.x` series are out of general support and covered by the only. Please consider to . This release . Erlang `21.3+` is now a hard requirement checked on node startup. Make sure a is used before upgrading. explains what package repositories and tools can be used to provision latest patch versions of Erlang `21.3.x` and `22.x`. When upgrading to this release and upgrading Erlang to 21.x or later at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21 or later, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes first if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . More peer discovery errors are retried. GitHub issue: Initial Erlang/OTP 24 compatibility. Erlang/OTP 24 is expected to ship in mid-2021. While RabbitMQ 3.7 will be by then, some initial compatibility work was backported to this branch due to contious integration on Erlang/OTP master. One-off connections periodically used by exchange federation links now handle timeouts in certain operations gracefully. This avoids unnecessary link disruption and restarts in certain environments. The default interval has also been bumped from 30s to 90s. In environments with stable topologies the interval can be significantly increased to decrease connection churn, simplify monitoring and in general conserve some resources: ``` erlang %% advanced.config [ {rabbitmq_federation, [ %% 86400 seconds or 24 hours {internalexchangecheck_interval, 86400000} ]} ]. ``` GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.7.27.tar.xz`.
Project: Druid (App Definition and Development / Database)
File: tranquility.md

id: tranquility title: "Tranquility" <!-- ~ 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. --> is a separately distributed package for pushing streams to Druid in real-time. Tranquility has not been built against a version of Druid later than Druid 0.9.2 release. It may still work with the latest Druid servers, but not all features and functionality will be available due to limitations of older Druid APIs on the Tranquility side. For new projects that require streaming ingestion, we recommend using Druid's native support for or . For more details, check out the .
Project: Checkov (Provisioning / Security & Compliance)
File: Custom Policies Overview.md

layout: default published: true title: Custom Policies Overview nav_order: 1 Custom Policies allow monitoring and enforcing of cloud infrastructure configuration in accordance with your organization's specific needs. For example, for certain resource types, you may want to enforce a tagging methodology or a special secure password policy; or you may want to restrict usage of a new service depending on the types of other services it is connected to. You can create custom policies in that check for the status of configuration attributes. You can create custom policies in that can both check for the status of configuration attributes and check the connection state between types of resources. You can also apply sophisticated logic to multiple conditions within a Custom Policy. Check out our . After creating tests for your custom policies, you can contribute them back to Checkov! Learn how to .
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_pubsub_topic_iam_binding.md

+++ title = "googlepubsubtopiciambinding resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlepubsubtopiciambinding" identifier = "inspec/resources/gcp/googlepubsubtopiciambinding.md googlepubsubtopiciambinding resource" parent = "inspec/resources/gcp" +++ A `googlepubsubtopiciambinding` is used to test a Google Topic Iam Bindings ```ruby describe googlepubsubtopiciambinding(project: "project", name: "name", role: "roles/editor") do it { should exist } its('members') { should include 'user:testuser@example.com' } end ``` Properties that can be accessed from the `googlepubsubtopiciambinding` resource: `role` : Role that is assigned to members. For example, roles/viewer, roles/editor, or roles/owner. `members` : Specifies the identities requesting access for a Cloud Platform resource. Ensure the is enabled for the current project.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: ml-ensembles.md

layout: global title: Tree ensemble methods displayTitle: Tree ensemble methods 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. > This section has been moved into the .
Project: StarRocks (App Definition and Development / Database)
File: atan.md

displayed_sidebar: "English" Computes the arc tangent of the argument. ```Haskell DOUBLE atan(DOUBLE arg) ``` `arg`: You can specify only a numeric value. This function converts the numeric value into a DOUBLE value before it computes the arc tangent of the value. Returns a value of the DOUBLE data type. If you specify a non-numeric value, this function returns `NULL`. ```Plain mysql> select atan(1); +--+ | atan(1) | +--+ | 0.7853981633974483 | +--+ mysql> select atan(0); ++ | atan(0) | ++ | 0 | ++ mysql> select atan(-1); ++ | atan(-1) | ++ | -0.7853981633974483 | ++ mysql> select atan(""); +-+ | atan('') | +-+ | NULL | +-+ ``` ATAN
Project: Druid (App Definition and Development / Database)
File: javascript.md

id: javascript title: "JavaScript programming guide" sidebar_label: "JavaScript functionality" <!-- ~ 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. --> This page discusses how to use JavaScript to extend Apache Druid. JavaScript can be used to extend Druid in a variety of ways: JavaScript can be injected dynamically at runtime, making it convenient to rapidly prototype new functionality without needing to write and deploy Druid extensions. Druid uses the Mozilla Rhino engine at optimization level 9 to compile and execute JavaScript. Druid does not execute JavaScript functions in a sandbox, so they have full access to the machine. So JavaScript functions allow users to execute arbitrary code inside druid process. So, by default, JavaScript is disabled. However, on dev/staging environments or secured production environments you can enable those by setting the `druid.javascript.enabled = true`. Avoid using global variables. Druid may share the global scope between multiple threads, which can lead to unpredictable results if global variables are used. Simple JavaScript functions typically have a slight performance penalty to native speed. More complex JavaScript functions can have steeper performance penalties. Druid compiles JavaScript functions once on each data process per query. You may need to pay special attention to garbage collection when making heavy use of JavaScript functions, especially garbage collection of the compiled classes themselves. Be sure to use a garbage collector configuration that supports timely collection of unused classes (this is generally easier on JDK8 with the Metaspace than it is on JDK7). Generally we recommend using JavaScript when security is not an issue, and when speed of development is more important than performance or memory use. If security is an issue, or if performance and memory use are of the utmost importance, we recommend developing a native Druid extension. In addition, native Druid extensions are more flexible than JavaScript functions. There are some kinds of extensions (like sketches) that must be written as native Druid extensions due to their need for custom data formats.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: time-fault.md

title: Simulate time faults description: Simulate time faults sidebar_position: 9 sidebar_label: Simulate time faults You can use this experiment type to simulate a time offset scenario. This document describes how to create a TimeChaos experiment. :::note TimeChaos only affects the PID `1` process in the PID namespace of the container, and child processes of the PID `1`. For example, the process started by `kubectl exec` does not be affected. ::: | Option | Short | Description | Default value | Required | | :-- | :- | : | : | :- | | `--time-offset` | None | It specifies the length of time offset. | None | Yes | | `--clock-id` | None | It specifies the ID of clock that will be offset. See the for details. | CLOCK_REALTIME | No | | `--container` | -c | It specifies a container name for fault injection. | None | No | This experiment configuration shifts the time of the processes in the specified Pod forward by 5 seconds. Once this time fault is injected into the Pod, a failure occurs to this Pod and this Pod restarts. ```bash kbcli fault time --time-offset=-5s ``` This section introduces the YAML configuration file examples. You can also refer to the for details. Write the experiment configuration to the `time.yaml` file. In the following example, Chaos Mesh injects a time fault to shift the time of the processes in the specified Pod forward by 5 seconds. Once this time fault is injected into the Pod, a failure occurs to this Pod and this Pod restarts. ```yaml apiVersion: chaos-mesh.org/v1alpha1 kind: TimeChaos metadata: creationTimestamp: null generateName: time-chaos- namespace: default spec: duration: 10s mode: all selector: namespaces: default timeOffset: -5s ``` Run `kubectl` to start an experiment. ```bash kubectl apply -f ./time.yaml ``` The fields in the YAML configuration file are described in the following table: | Parameter | Type | Note | Default value | Required | | : | : | : | : | : | | timeOffset | string | It specifies the length of time offset. | None | Yes | | clockIds | for details. | `["CLOCK_REALTIME"]` | No | | mode | string | It specifies the mode of an experiment. The mode options include `one` (selecting a random Pod), `all` (selecting all eligible Pods), `fixed` (selecting a specified number of eligible Pods), `fixed-percent` (selecting a specified percentage of Pods from the eligible Pods), and `random-max-percent` (selecting the maximum percentage of Pods from the eligible Pods). | None | Yes | | value | string | It provides parameters for the `mode` configuration, depending on `mode`. For example, when `mode` is set to `fixed-percent`, `value` specifies the percentage of Pods. | None | No | | containerNames | []string | It specifies the name of the container into which the fault is injected. | None | No | | selector | struct | It specifies the target Pod. | None | Yes |
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Fault-tolerance.md

layout: documentation This page explains the design details of Storm that make it a fault-tolerant system. When a worker dies, the supervisor will restart it. If it continuously fails on startup and is unable to heartbeat to Nimbus, Nimbus will reassign the worker to another machine. The tasks assigned to that machine will time-out and Nimbus will reassign those tasks to other machines. The Nimbus and Supervisor daemons are designed to be fail-fast (process self-destructs whenever any unexpected situation is encountered) and stateless (all state is kept in Zookeeper or on disk). As described in , the Nimbus and Supervisor daemons must be run under supervision using a tool like daemontools or monit. So if the Nimbus or Supervisor daemons die, they restart like nothing happened. Most notably, no worker processes are affected by the death of Nimbus or the Supervisors. This is in contrast to Hadoop, where if the JobTracker dies, all the running jobs are lost. If you lose the Nimbus node, the workers will still continue to function. Additionally, supervisors will continue to restart workers if they die. However, without Nimbus, workers won't be reassigned to other machines when necessary (like if you lose a worker machine). So the answer is that Nimbus is "sort of" a SPOF. In practice, it's not a big deal since nothing catastrophic happens when the Nimbus daemon dies. There are plans to make Nimbus highly available in the future. Storm provides mechanisms to guarantee data processing even if nodes die or messages are lost. See for the details.
Project: YugabyteDB (App Definition and Development / Database)
File: extension-fuzzystrmatch.md

title: fuzzystrmatch extension headerTitle: fuzzystrmatch extension linkTitle: fuzzystrmatch description: Using the fuzzystrmatch extension in YugabyteDB menu: v2.18: identifier: extension-fuzzystrmatch parent: pg-extensions weight: 20 type: docs The module provides several functions to determine similarities and distance between strings. ```sql CREATE EXTENSION fuzzystrmatch; SELECT levenshtein('Yugabyte', 'yugabyte'), metaphone('yugabyte', 8); ``` ```output levenshtein | metaphone -+-- 2 | YKBT (1 row) ```
Project: ClickHouse (App Definition and Development / Database)
File: sqlite.md

slug: /en/sql-reference/table-functions/sqlite sidebar_position: 185 sidebar_label: sqlite title: sqlite Allows to perform queries on a data stored in an database. Syntax ``` sql sqlite('dbpath', 'tablename') ``` Arguments `db_path` Path to a file with an SQLite database. . `table_name` Name of a table in the SQLite database. . Returned value A table object with the same columns as in the original `SQLite` table. Example Query: ``` sql SELECT * FROM sqlite('sqlite.db', 'table1') ORDER BY col2; ``` Result: ``` text col1col2 line1 1 line2 2 line3 3 ``` See Also table engine
Project: Apache CarbonData (App Definition and Development / Database)
File: How-to-build-carbondata-notebook-docker-image-by-dockerfile.md

This documentation will describe how to build carbondata notebook docker images. It should already installed docker environment. go to directory of dockerfile ``` cd build/docker/carbondata-notebook ``` build image ``` docker build -t carbondata:2.3.0 . ``` ```history localhost:carbondata-notebook xubo$ docker build -t carbondata:2.3.1 . [+] Building 20.2s (7/7) FINISHED => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 260B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load metadata for docker.io/jupyter/all-spark-notebook:spark-3.1.1 0.0s => [1/3] FROM docker.io/jupyter/all-spark-notebook:spark-3.1.1 0.0s => CACHED [2/3] WORKDIR . 0.0s => [3/3] RUN wget https://dlcdn.apache.org/carbondata/2.3.0/apache-carbondata-2.3.0-bin-spark3.1.1-hadoop2.7.2.jar -P /usr/local/spark-3.1.1-bin-hadoop3.2/jars/ 19.4s => exporting to image 0.6s => => exporting layers 0.6s => => writing image sha256:25c5b977aaa5e2404ce720b2f5784dfb9b16921e8bb2cab004e9e50fc0631c2c 0.0s => => naming to docker.io/library/carbondata:2.3.1 0.0s localhost:carbondata-notebook xubo$ pwd /Users/xubo/Desktop/xubo/git/carbondata1/build/docker/carbondata-notebook localhost:carbondata-notebook xubo$ docker images |grep carbondata carbondata 2.3.1 25c5b977aaa5 About a minute ago 4.22GB carbondata 2.3.0 2307a01af387 2 minutes ago 4.22GB ``` Please refer to