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

title: "Overview of client load balancing in {{ ydb-short-name }}" description: "The section contains code recipes with client load balancing settings in different {{ ydb-short-name }} SDKs." {% include %} {{ ydb-short-name }} uses client load balancing because it is more efficient when a lot of traffic from multiple client applications comes to a database. In most cases, it just works in the {{ ydb-short-name }} SDK. However, sometimes specific settings for client load balancing are required, for example, to reduce server hops and request time or to distribute the load across availability zones. Note that custom balancing is limited when it comes to {{ ydb-short-name }} sessions. Custom balancing in the {{ ydb-short-name }} SDKs is performed only when creating a new {{ ydb-short-name }} session on a specific node. Once the session is created, all queries in this session are passed to the node where the session was created. Queries in the same {{ ydb-short-name }} session are not balanced between different {{ ydb-short-name }} nodes. This section contains code recipes with client load balancing settings in different {{ ydb-short-name }} SDKs. Table of contents:
Project: BigchainDB (App Definition and Development / Database)
File: release-notes.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > You can find a list of all BigchainDB Server releases and release notes on GitHub at: The contains much the same information, but it also has notes about what to expect in the next release. We also have .
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-show-create-table.md

layout: global title: SHOW CREATE TABLE displayTitle: SHOW 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. `SHOW CREATE TABLE` returns the or that was used to create a given table or view. `SHOW CREATE TABLE` on a non-existent table or a temporary view throws an exception. ```sql SHOW CREATE TABLE table_identifier [ AS SERDE ] ``` table_identifier* Specifies a table or view name, which may be optionally qualified with a database name. Syntax: `[ databasename. ] tablename` AS SERDE* Generates Hive DDL for a Hive SerDe table. ```sql CREATE TABLE test (c INT) ROW FORMAT DELIMITED FIELDS TERMINATED BY ',' STORED AS TEXTFILE TBLPROPERTIES ('prop1' = 'value1', 'prop2' = 'value2'); SHOW CREATE TABLE test; +-+ | createtab_stmt| +-+ |CREATE TABLE `default`.`test` (`c` INT) USING text TBLPROPERTIES ( 'transient_lastDdlTime' = '1586269021', 'prop1' = 'value1', 'prop2' = 'value2') +-+ SHOW CREATE TABLE test AS SERDE; ++ | createtab_stmt| ++ |CREATE TABLE `default`.`test`( `c` INT) ROW FORMAT SERDE 'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe' WITH SERDEPROPERTIES ( 'serialization.format' = ',', 'field.delim' = ',') STORED AS INPUTFORMAT 'org.apache.hadoop.mapred.TextInputFormat' OUTPUTFORMAT 'org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat' TBLPROPERTIES ( 'prop1' = 'value1', 'prop2' = 'value2', 'transient_lastDdlTime' = '1641800515') ++ ```
Project: kpt (Provisioning / Automation & Configuration)
File: 02-exploring-a-package.md

After you fetch a package to your local filesystem, you typically want to explore the package to understand how it is composed and how it can be customized for your needs. Given a kpt package is just an ordinary directory of human-readable YAML files, you can naturally use your favorite file explorer, shell commands, or editor to explore the package. kpt also provides the `tree` command which is handy for quickly viewing package hierarchy and the constituent packages, files, and resources: ```shell $ kpt pkg tree wordpress/ Package "wordpress" [Kptfile] Kptfile wordpress [service.yaml] Service wordpress deployment [deployment.yaml] Deployment wordpress [volume.yaml] PersistentVolumeClaim wp-pv-claim Package "mysql" [Kptfile] Kptfile mysql [deployment.yaml] PersistentVolumeClaim mysql-pv-claim [deployment.yaml] Deployment wordpress-mysql [deployment.yaml] Service wordpress-mysql ``` ?> Refer to the for usage. In addition, you can use a kpt function such as `search-replace` to run a query on the package. For example, to search for resources that have a field with path `spec.selector.tier`: ```shell $ kpt fn eval wordpress -i search-replace:v0.1 -- 'by-path=spec.selector.tier' ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_completion_powershell.md

title: "operator-sdk completion powershell" Load powershell completions ``` operator-sdk completion powershell [flags] ``` ``` -h, --help help for powershell ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - Load completions for the specified shell
Project: Teleport (Provisioning / Security & Compliance)
File: flaky_test.md

name: Flaky Test about: Report a flaky unit or integration test title: "`TestName` flakiness" labels: flaky tests Before filing a new issue, search https://github.com/gravitational/teleport/issues?q=is%3Aissue+label%3A%22flaky+tests%22+ for the flaky test's name to see if the same issue has already been reported. If so, add a comment with the `Link(s) to logs` url (see section below). Double check the `Relevant snippet` to confirm that the specific failure is the same. If you've encountered a new failure for the same test, also copy-paste the `Relevant snippet` (see section below). If there's no existing issue for this test, continue to file a new one: Change `TestName` in the title to the name of the test that failed. Use `git blame` to try and figure out who is most responsible for the test, and assign them to this issue. Delete this entire section and continue. Update the link below with the similar link to the logs of the test run that failed, then delete this line. https://github.com/gravitational/teleport/actions/runs/<run-id>/jobs/<job-id> replace everything below here with your snippet Be extra helpful by adding the relevant snippet of the logs that show where the failure takes place. Typically ctrl+F searching for "Test:" will bring you to the right spot. If "Test:" doesn't work, try ctrl+F "Fail:". The example below shows what a typical failure looks like (though sometimes no such log will exist, for example in the case of a timeout). ``` tsh_test.go:667: Error Trace: tsh_test.go:667 Error: Received unexpected error: exit code 1 Test: TestSSHAccessRequest ```
Project: ClickHouse (App Definition and Development / Database)
File: anyheavy.md

slug: /en/sql-reference/aggregate-functions/reference/anyheavy sidebar_position: 103 Selects a frequently occurring value using the algorithm. If there is a value that occurs more than in half the cases in each of the querys execution threads, this value is returned. Normally, the result is nondeterministic. ``` sql anyHeavy(column) ``` Arguments `column` The column name. Example Take the data set and select any frequently occurring value in the `AirlineID` column. ``` sql SELECT anyHeavy(AirlineID) AS res FROM ontime ``` ``` text res 19690 ```
Project: YugabyteDB (App Definition and Development / Database)
File: apache-beam.md

title: Apache Beam linkTitle: Apache Beam description: Apache Beam menu: preview_integrations: identifier: apache-beam parent: data-integration weight: 571 type: docs is an open source, unified model for defining both batch and streaming data-parallel processing pipelines. Using one of the open source Beam SDKs, you build a program that defines the pipeline. The pipeline is then executed by one of Beams supported distributed processing back-ends, which include , , and . To use Apache Beam, ensure that you have YugabyteDB up and running. Download and install YugabyteDB by following the steps in . To run Apache Beam with YugabyteDB, do the following: Create a folder `apache-beam-test` as follows: ```sh mkdir apache-beam-test && cd apache-beam-test ``` Create a python virtual environment and activate it as follows: ```python python3 -m venv myenv source myenv/bin/activate ``` Install the latest Apache Beam Python SDK from Pypi using the following command: ```python pip install beam-nuggets ``` Create a python file, `democode.py` and add the following code to it: ```python import apache_beam as beam from apachebeam.options.pipelineoptions import PipelineOptions from beamnuggets.io import relationaldb records = [ {'name': 'Jan', 'num': 1}, {'name': 'Feb', 'num': 2}, {'name': 'Mar', 'num': 3}, {'name': 'Apr', 'num': 4}, {'name': 'May', 'num': 5}, ] sourceconfig = relationaldb.SourceConfiguration( drivername='postgresql', #postgresql+pg8000 host='127.0.0.1', port=5433, username=yugabyte, password='yugabyte', database='yugabyte', createifmissing=True # create the database if not there ) tableconfig = relationaldb.TableConfiguration( name='months_col01', createifmissing=True, primarykeycolumns=['num'] ) with beam.Pipeline(options=PipelineOptions()) as p: months = p | "Reading month records" >> beam.Create(records) months | 'Writing to DB table' >> relational_db.Write( sourceconfig=sourceconfig, tableconfig=tableconfig ) if name == "main": print('demo code ran successful') ``` Run `democode.py` as follows: ```python python democode.py ``` ```output demo code ran successful ``` You can also verify the changes from a as follows: ```sql select * from month_col01; ``` You can see the following output: ```output num | name --+ 5 | May 1 | Jan 4 | Apr 2 | Feb 3 | Mar (5 rows) ```
Project: Stolon (App Definition and Development / Database)
File: stolonctl_removekeeper.md

Removes keeper from cluster data Removes keeper from cluster data ``` stolonctl removekeeper [keeper uid] [flags] ``` ``` -h, --help help for removekeeper ``` ``` --cluster-name string cluster name --kube-context string name of the kubeconfig context to use --kube-namespace string name of the kubernetes namespace to use --kube-resource-kind string the k8s resource kind to be used to store stolon clusterdata and do sentinel leader election (only "configmap" is currently supported) --kubeconfig string path to kubeconfig file. Overrides $KUBECONFIG --log-level string debug, info (default), warn or error (default "info") --metrics-listen-address string metrics listen address i.e "0.0.0.0:8080" (disabled by default) --store-backend string store backend type (etcdv2/etcd, etcdv3, consul or kubernetes) --store-ca-file string verify certificates of HTTPS-enabled store servers using this CA bundle --store-cert-file string certificate file for client identification to the store --store-endpoints string a comma-delimited list of store endpoints (use https scheme for tls communication) (defaults: http://127.0.0.1:2379 for etcd, http://127.0.0.1:8500 for consul) --store-key string private key file for client identification to the store --store-prefix string the store base prefix (default "stolon/cluster") --store-skip-tls-verify skip store certificate verification (insecure!!!) --store-timeout duration store request timeout (default 5s) ``` - stolon command line client
Project: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_e2e.md

Generates a list of all tests and tags in that tests ``` sonobuoy e2e [flags] ``` ``` --context string Context in the kubeconfig to use. -f, --focus string Return tests which match this regular expression -h, --help help for e2e -i, --input string Determines the source of the test lists. Can be [online, offline, -]. If '-' is set, tests will be read from stdin. (default "online") --kubeconfig Kubeconfig Path to explicit kubeconfig file. -m, --mode string Print mode. Can be one of [tags, tagCounts, tests] (default "tests") -s, --skip string Do not return tests which match this regular expression --version ConformanceImageVersion Use default E2E image, but override the version. Default is 'auto', which will be set to your cluster's version if detected, erroring otherwise. 'ignore' will try version resolution but ignore errors. 'latest' will find the latest dev image/version upstream. ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Generate reports on your Kubernetes cluster by running plugins
Project: StarRocks (App Definition and Development / Database)
File: st_point.md

displayed_sidebar: "English" Returns the corresponding Point with the given X-coordinate and Y-coordinate. At the moment this value only makes sense on a spherical set. X/Y corresponds to longitude/latitude. Caution If you directly select ST_Point(), it may get stuck. ```Haskell POINT ST_Point(DOUBLE x, DOUBLE y) ``` ```Plain Text MySQL > SELECT STAsText(STPoint(24.7, 56.7)); ++ | stastext(stpoint(24.7, 56.7)) | ++ | POINT (24.7 56.7) | ++ ``` ST_POINT,ST,POINT
Project: YDB (App Definition and Development / Database)
File: operation-forget.md

Use the `ydb operation forget` subcommand to delete information about the specified long running operation from the list. The operation must be complete. General format of the command: ```bash {{ ydb-cli }} [global options...] operation forget <id> ``` `global options`: . `options`: . `id`: The ID of the long running operation. The ID contains characters that can be interpreted by your command shell. If necessary, use shielding, for example, `'<id>'` for bash. View a description of the command to delete information about the specified long running operation: ```bash {{ ydb-cli }} operation forget --help ``` {% include %} Delete the long running operation with the `ydb://buildindex/7?id=281489389055514` ID from the list: ```bash ydb -p db1 operation forget \ 'ydb://buildindex/7?id=281489389055514' ```
Project: KICS (Provisioning / Security & Compliance)
File: d6047119-a0b2-4b59-a4f2-127a36fb685b.md

title: Role With Privilege Escalation By Actions 'iam:PutGroupPolicy' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d6047119-a0b2-4b59-a4f2-127a36fb685b Query name: Role With Privilege Escalation By Actions 'iam:PutGroupPolicy' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role with privilege escalation by actions 'iam:PutGroupPolicy' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamrole" "cosmic" { name = "cosmic" } resource "awsiamrolepolicy" "testinline_policy" { name = "testinlinepolicy" role = awsiamrole.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:PutGroupPolicy", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: KusionStack (Provisioning / Automation & Configuration)
File: kusion_check.md

Check if KCL configurations in current directory ok to compile Check if KCL configurations in current directory ok to compile. ``` kusion check [flags] ``` ``` kusion check main.k kusion check main.k -D name=test -D age=18 kusion check main.k -Y settings.yaml kusion check main.k -w appops/demo/dev ``` ``` -D, --argument stringToString Specify the top-level argument (default []) -n, --disable-none Disable dumping None values -h, --help help for check -a, --override-AST Specify the override option -O, --overrides strings Specify the configuration override path and value -Y, --setting strings Specify the command line setting files -w, --workdir string Specify the work directory ``` - Kusion is the platform engineering engine of KusionStack
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_olm_status.md

title: "operator-sdk olm status" Get the status of the Operator Lifecycle Manager installation in your cluster ``` operator-sdk olm status [flags] ``` ``` -h, --help help for status --olm-namespace string namespace where OLM is installed (default "olm") --timeout duration time to wait for the command to complete before failing (default 2m0s) --version string version of OLM installed on cluster; if unsetoperator-sdk attempts to auto-discover the version ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - Manage the Operator Lifecycle Manager installation in your cluster
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.9.md

RabbitMQ `3.9.9` 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. Fixed an issue where node monitor could produce a false network partition when one of the cluster members was restarted GitHub issue: Message store resiliency improvements GitHub issue: Reduced log noise in certain scenarios where a new queue leader is elected GitHub issue: Queue leader rebalancing now logs less GitHub issue: `clusterformation.targetclustersizehint` is a new configuration setting that can be used to specify expected initial cluster size. This can be used by features, plugins or tools that expect a certain minimum number of clusters nodes to join during initial cluster formation GitHub issue: Metric rendering efficiency improvements (mostly latency) GitHub issue: TLS-enabled Prometheus endpoint listener port was not correctly stored internally GitHub issue: Persistent message count is now displayed correctly on individual queue pages GitHub issue: Restore compatibility with IE 11 GitHub issue: Corrected deletion of duplicate bindings between an exchange and a queue Contributed by @FalconerTC GitHub issue: Ra was Osiris was To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.9.tar.xz` instead of the source tarball produced by GitHub.
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: bug_report.md

name: Bug report about: Create a report to help us improve labels: bug <!-- Thanks for filing a bug report ! --> Problem <!-- A clear and concise description of what the bug is. --> <!-- including what currently happens and what you expected to happen. --> Steps <!-- The steps to reproduce the bug. --> Possible Solution(s) <!-- Not obligatory, but suggest a fix/reason for the bug, --> <!-- or ideas how to implement the addition or change --> Notes Output of `rustup --version`: Output of `rustup show`: Output of `tremor --version`:
Project: KICS (Provisioning / Security & Compliance)
File: 7384dfb2-fcd1-4fbf-91cd-6c44c318c33c.md

title: APT-GET Not Avoiding Additional Packages hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7384dfb2-fcd1-4fbf-91cd-6c44c318c33c Query name: APT-GET Not Avoiding Additional Packages Platform: Dockerfile Severity: <span style="color:#5bc0de">Info</span> Category: Supply-Chain URL: Check if any apt-get installs don't use '--no-install-recommends' flag to avoid installing additional packages.<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="2 3" FROM node:12 RUN apt-get install apt-utils RUN ["apt-get", "install", "apt-utils"] ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM node:12 RUN apt-get --no-install-recommends install apt-utils RUN ["apt-get", "apt::install-recommends=false", "install", "apt-utils"] ```
Project: YugabyteDB (App Definition and Development / Database)
File: create_function,create_procedure,alter_function,alter_procedure.grammar.md

```output.ebnf createfunction ::= CREATE [ OR REPLACE ] FUNCTION subprogramname ( [ argdeclwith_dflt [ , ... ] ] ) { RETURNS data_type | RETURNS TABLE ( { columnname datatype } [ , ... ] ) } { unalterablefnattribute | alterablefnonly_attribute | alterablefnandprocattribute } [ ... ] createprocedure ::= CREATE [ OR REPLACE ] PROCEDURE subprogramname ( [ argdeclwith_dflt [ , ... ] ] ) { unalterableprocattribute | alterablefnandprocattribute } [ ... ] alterfunction ::= ALTER FUNCTION subprogramname ( [ subprogram_signature ] ) { specialfnandprocattribute | { alterablefnandprocattribute | alterablefnonly_attribute } [ ... ] [ RESTRICT ] } alterprocedure ::= ALTER PROCEDURE subprogramname ( [ subprogram_signature ] ) { specialfnandprocattribute | alterablefnandprocattribute [ ... ] [ RESTRICT ] } ```
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_KinesisDataAnalytics.md

The following is an example for an Application Destination Lambda function that receives Amazon Kinesis Data Analytics event records as an input. To send Kinesis Data Analytics output records the Lambda function must be compliant with the (required input and return data models)[https://docs.aws.amazon.com/kinesisanalytics/latest/dev/how-it-works-output-lambda.html], so the handler returns a list of delivery statuses for each record. The following Lambda function receives Amazon Kinesis Data Analytics event record data as an input and writes some of the record data to CloudWatch Logs. For each entry it adds an element to the response slice, marking it delivered. When the logic considers the delivery to be failed the `events.KinesisAnalyticsOutputDeliveryFailed` value should be used for the response `Result` field. ```go package main import ( "context" "encoding/json" "fmt" "log" "github.com/aws/aws-lambda-go/events" "github.com/aws/aws-lambda-go/lambda" ) func handler(ctx context.Context, kinesisAnalyticsEvent events.KinesisAnalyticsOutputDeliveryEvent) (events.KinesisAnalyticsOutputDeliveryResponse, error) { var err error var responses events.KinesisAnalyticsOutputDeliveryResponse responses.Records = make([]events.KinesisAnalyticsOutputDeliveryResponseRecord, len(kinesisAnalyticsEvent.Records)) for i, record := range kinesisAnalyticsEvent.Records { responses.Records[i] = events.KinesisAnalyticsOutputDeliveryResponseRecord{ RecordID: record.RecordID, Result: events.KinesisAnalyticsOutputDeliveryOK, } dataBytes := record.Data dataText := string(dataBytes) fmt.Printf("%s Data = %s \n", record.RecordID, dataText) } return responses, err } func main() { lambda.Start(handler) } ```