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

title: Prepare the OpenShift environment headerTitle: Cloud prerequisites linkTitle: Cloud prerequisites description: Prepare the OpenShift environment for YugabyteDB Anywhere headContent: Prepare OpenShift for YugabyteDB Anywhere menu: v2.18_yugabyte-platform: identifier: prepare-environment-4-OpenShift parent: install-yugabyte-platform weight: 55 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li> <a href="../aws/" class="nav-link"> <i class="fa-brands fa-aws" aria-hidden="true"></i> AWS </a> </li> <li> <a href="../gcp/" class="nav-link"> <i class="fa-brands fa-google" aria-hidden="true"></i> GCP </a> </li> <li> <a href="../azure/" class="nav-link"> <i class="icon-azure" aria-hidden="true"></i> &nbsp;&nbsp; Azure </a> </li> <li> <a href="../kubernetes/" class="nav-link"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i> Kubernetes </a> </li> <li> <a href="../openshift/" class="nav-link active"> <i class="fa-brands fa-redhat" aria-hidden="true"></i> OpenShift </a> </li> <li> <a href="../on-premises/" class="nav-link"> <i class="fa-solid fa-building" aria-hidden="true"></i> On-premises </a> </li> </ul> To prepare the environment for OpenShift, you start by provisioning the OpenShift cluster. The recommended OpenShift Container Platform (OCP) version is 4.6, with backward compatibility assumed but not guaranteed. You should have 18 vCPU and 32 GB of memory available for testing YugabyteDB Anywhere. This can be three or more nodes equivalent to Google Cloud Platform's n1-standard-8 (8 vCPU, 30 GB memory). For more information and examples on provisioning OpenShift clusters on GCP, see the following: In addition, ensure that you have the following: The latest oc binary in your path. For more information, see . The latest kubectl 1.19.7 binary in your path. See for more information, or create a kubectl symlink pointing to oc. An admin user ClusterRole bound to it. Depending on your configuration, this user might be kube:admin. An authenticated user[^2] in the cluster which can create new projects[^3]. For testing purposes, you may configure an HTPasswd provider, as described in (specifically, in and ). ClusterRole bound to them, which enables them to create new projects.
Project: StarRocks (App Definition and Development / Database)
File: DROP_STORAGE_VOLUME.md

displayed_sidebar: "English" Drops a storage volume. Dropped storage volumes cannot be referenced anymore. This feature is supported from v3.1. CAUTION Only users with the DROP privilege on a specific storage volume can perform this operation. The default storage volume and the built-in storage volume `builtinstoragevolume` cannot be dropped. You can use to check whether a storage volume is the default storage volume. Storage volumes that are referenced by existing databases or cloud-native tables cannot be dropped. ```SQL DROP STORAGE VOLUME [ IF EXISTS ] <storagevolumename> ``` | Parameter | Description | | - | | | storagevolumename | The name of the storage volume to drop. | Example 1: Drop the storage volume `mys3volume`. ```Plain MySQL > DROP STORAGE VOLUME mys3volume; Query OK, 0 rows affected (0.01 sec) ```
Project: CockroachDB (App Definition and Development / Database)
File: performance-inquiry.md

name: 'Performance inquiry' title: '' about: 'You have a question about CockroachDB's performance and it is not a bug or a feature request' labels: 'C-question' What is your situation? Select all that apply: is there a difference between the performance you expect and the performance you observe? do you want to improve the performance of your app? are you surprised by your performance results? are you comparing CockroachDB with some other database? another situation? Please explain. Observed performance What did you see? How did you measure it? If you have already ran tests, include your test details here: which test code do you use? which SQL queries? Schema of supporting tables? how many clients per node? how many requests per client / per node? Application profile Performance depends on the application. Please help us understand how you use CockroachDB before we can discuss performance. Have you used other databases before? Or are you considering a migration? Please list your previous/other databases here. What is the scale of the application? how many columns per table? how many rows (approx) per table? how much data? how many clients? Requests / second? What is the query profile? is this more a OLTP/CRUD workload? Or Analytics/OLAP? Is this hybrid/HTAP? what is the ratio of reads to writes? which queries are grouped together in transactions? What is the storage profile? how many nodes? how much storage? how much data? replication factor? Requested resolution When/how would you consider this issue resolved? Select all that applies: I mostly seek information: data, general advice, clarification. I seek guidance as to how to tune my application or CockroachDB deployment. I want CockroachDB to be optimized for my use case.
Project: ShardingSphere (App Definition and Development / Database)
File: drop-readwrite-splitting-rule.en.md

+++ title = "DROP READWRITE_SPLITTING RULE" weight = 3 +++ The `DROP READWRITE_SPLITTING RULE` syntax is used to drop readwrite-splitting rule for specified database {{< tabs >}} {{% tab name="Grammar" %}} ```sql DropReadwriteSplittingRule ::= 'DROP' 'READWRITE_SPLITTING' 'RULE' ifExists? ruleName (',' ruleName)* ('FROM' databaseName)? ifExists ::= 'IF' 'EXISTS' ruleName ::= identifier databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted; `ifExists` clause is used for avoid `Readwrite-splitting rule not exists` error. Drop readwrite-splitting rule for specified database ```sql DROP READWRITESPLITTING RULE msgroup1 FROM readwritesplitting_db; ``` Drop readwrite-splitting rule for current database ```sql DROP READWRITESPLITTING RULE msgroup_1; ``` Drop readwrite-splitting rule with `ifExists` clause ```sql DROP READWRITESPLITTING RULE IF EXISTS msgroup_1; ``` `DROP`, `READWRITE_SPLITTING`, `RULE`
Project: YDB (App Definition and Development / Database)
File: access-management.md

{{ ydb-short-name }} supports authentication by username and password. A {{ ydb-short-name }} cluster has built-in groups that offer predefined sets of roles: Group | Description | `ADMINS` | Unlimited rights for the entire cluster schema. `DATABASE-ADMINS` | Rights to create and delete databases (`CreateDatabase`, `DropDatabase`). `ACCESS-ADMINS` | Rights to manage rights of other users (`GrantAccessRights`). `DDL-ADMINS` | Rights to alter the database schema (`CreateDirectory`, `CreateTable`, `WriteAttributes`, `AlterSchema`, `RemoveSchema`). `DATA-WRITERS` | Rights to change data (`UpdateRow`, `EraseRow`). `DATA-READERS` | Rights to read data (`SelectRow`). `METADATA-READERS` | Rights to read metadata without accessing data (`DescribeSchema` and `ReadAttributes`). `USERS` | Rights to connect to databases (`ConnectDatabase`). All users are added to the `USERS` group by default. The `root` user is added to the `ADMINS` group by default. You can see how groups inherit permissions below. For example, the `DATA-WRITERS` group includes all the permissions from `DATA-READERS`: To create, update, or delete a group, use the YQL operators: . . . {% note info %} When using the names of built-in groups in the `ALTER GROUP` commands, those names must be provided in the upper case. In addition, the names of built-in groups containing the "-" symbol must be surrounded with the backticks, for example: ``` ALTER GROUP `DATA-WRITERS` ADD USER myuser1; ``` {% endnote %} To create, update, or delete a user, use the YQL operators: . . .
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-pod-unpause.1.md

% podman-pod-unpause 1 podman\-pod\-unpause - Unpause one or more pods podman pod unpause [options] pod ... Unpauses all the paused processes in the containers of one or more pods. You may use pod IDs or names as input. Unpause all pods. Instead of providing the pod name or ID, unpause the last created pod. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines) Unpause pod with a given name: ``` podman pod unpause mywebserverpod ``` Unpause pod with a given ID: ``` podman pod unpause 860a4b23 ``` , , July 2018, Originally compiled by Peter Hunt <pehunt@redhat.com>
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.3.0.md

title: v1.3.0 weight: 998997000 If your project uses the `packagemanifests` make recipe, update your `PKGMANOPTS` variable to include `PKGFROMVERSION` instead of `FROM_VERSION`, ex: ```make PKGMANOPTS ?= $(PKGFROMVERSION) $(PKGCHANNELS) $(PKGISDEFAULTCHANNEL) ``` See for more details. In your go.mod file, update the `sigs.k8s.io/controller-runtime` version to v0.6.4 See for more details. The newly released go/v3 plugin has many new features and (breaking) changes incompatible with projects created by go/v2. You are not required to upgrade and your go/v2 project will continue to work with new operator-sdk versions. If you wish to upgrade, check out the upstream . Additionally, if using project version "3-alpha", you must update your `plugins` config field: Old: ```yaml plugins: go.sdk.operatorframework.io/v2-alpha: {} ``` New: ```yaml plugins: manifests.sdk.operatorframework.io/v2: {} scorecard.sdk.operatorframework.io/v2: {} ``` See for more details.
Project: YugabyteDB (App Definition and Development / Database)
File: extension-pgvector.md

title: pgvector extension headerTitle: pgvector extension linkTitle: pgvector description: Using the pgvector extension in YugabyteDB menu: stable: identifier: extension-pgvector parent: pg-extensions weight: 20 type: docs The PostgreSQL extension allows you to store and query vectors, for use in performing similarity searches. Note that YugabyteDB support for pgvector does not currently include . To enable the extension: ```sql CREATE EXTENSION vector; ``` Create a vector column with 3 dimensions: ```sql CREATE TABLE items (id bigserial PRIMARY KEY, embedding vector(3)); ``` Insert vectors: ```sql INSERT INTO items (embedding) VALUES ('[1,2,3]'), ('[4,5,6]'); ``` Get the nearest neighbors by L2 distance: ```sql SELECT * FROM items ORDER BY embedding <-> '[3,1,2]' LIMIT 5; ``` The extension also supports inner product (`<#>`) and cosine distance (`<=>`). Note: `<#>` returns the negative inner product because PostgreSQL only supports `ASC` order index scans on operators. Create a new table with a vector column: ```sql CREATE TABLE items (id bigserial PRIMARY KEY, embedding vector(3)); ``` Or add a vector column to an existing table: ```sql ALTER TABLE items ADD COLUMN embedding vector(3); ``` Insert vectors: ```sql INSERT INTO items (embedding) VALUES ('[1,2,3]'), ('[4,5,6]'); ``` Upsert vectors: ```sql INSERT INTO items (id, embedding) VALUES (1, '[1,2,3]'), (2, '[4,5,6]') ON CONFLICT (id) DO UPDATE SET embedding = EXCLUDED.embedding; ``` Update vectors: ```sql UPDATE items SET embedding = '[1,2,3]' WHERE id = 1; ``` Delete vectors: ```sql DELETE FROM items WHERE id = 1; ``` Get the nearest neighbors to a vector: ```sql SELECT * FROM items ORDER BY embedding <-> '[3,1,2]' LIMIT 5; ``` Get the nearest neighbors to a row: ```sql SELECT * FROM items WHERE id != 1 ORDER BY embedding <-> (SELECT embedding FROM items WHERE id = 1) LIMIT 5; ``` Get rows within a certain distance: ```sql SELECT * FROM items WHERE embedding <-> '[3,1,2]' < 5; ``` <!--Note: Combine with `ORDER BY` and `LIMIT` to use an index.--> Get the distance: ```sql SELECT embedding <-> '[3,1,2]' AS distance FROM items; ``` For inner product, multiply by -1 (`<#>` returns the negative inner product) ```sql SELECT (embedding <#> '[3,1,2]') * -1 AS inner_product FROM items; ``` For cosine similarity, use 1 - cosine distance: ```sql SELECT 1 - (embedding <=> '[3,1,2]') AS cosine_similarity FROM items; ``` Average vectors: ```sql SELECT AVG(embedding) FROM items; ``` Create a table with a vector column and a category column: ```sql CREATE TABLE items (id bigserial PRIMARY KEY, embedding vector(3), category_id int); ``` Insert multiple vectors belonging to the same category: ```sql INSERT INTO items (embedding, category_id) VALUES ('[1,2,3]', 1), ('[4,5,6]', 2), ('[3,4,5]', 1), ('[2,3,4]', 2); ``` Average groups of vectors belonging to the same category: ```sql SELECT categoryid, AVG(embedding) FROM items GROUP BY categoryid; ```
Project: Apollo (Provisioning / Automation & Configuration)
File: apollo-release-guide.md

Replace the version number in full under the Apollo project, e.g. 1.9.1-SNAPSHOT to 1.9.1. Be sure to replace the non-version number in the process. Each PR between two versions is recorded in , so you only need to extract it from CHANGES.md to write the release report. Release report reference: Version validation consists of three main areas of validation. Verification of newly introduced code changes, such as new features, bugfixes Apollo core main process validation, including: configuration release, dynamic push, grayscale push, etc. upgrade process validation, including: classic deployment mode, docker mode, k8s mode Pull the latest code from master git pull origin master Tag git tag ${new-version} Push tag git push origin tag ${new-version} Before packaging, check your local environment, mvn -v to make sure the java version is 1.8, e.g. the following output. mvn -v Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) Maven home: /usr/local/Cellar/maven/3.8.1/libexec Java version: 1.8.0301, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0301.jdk/Contents/Home/jre Default locale: zh_CN, platform encoding: UTF-8 OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" In the ${apollo_home}/scripts/ directory, execute. . /build.sh If the following error is reported. zsh: . /build.sh: bad interpreter: /bin/sh^M: no such file or directory Then you need to execute the following command to convert to unix brew install dos2unix dos2unix build.sh To calculate configservice checksum In the ${apollo_home}/apollo-configservice/target/ directory, execute. shasum apollo-configservice-${new-version}-github.zip > apollo-configservice-${new-version}-github.zip.sha1 Calculate adminservice checksum In the ${apollo_home}/apollo-adminservice/target/ directory, execute. shasum apollo-adminservice-${new-version}-github.zip > apollo-adminservice-${new-version}-github.zip.sha1 Calculate portal checksum In the ${apollo_home}/apollo-portal/target/ directory, execute. shasum apollo-portal-${new-version}-github.zip > apollo-portal-${new-version}-github.zip.sha1 Github create pre-release Fill out the Release Note & upload the package Publish via github workflow. Note: If you are releasing a SNAPSHOT version, use the default value snapshots. If you are releasing an official version (without SNAPSHOT), you need to change it to releases to make it work. Polling is used to allow PMC members to collaborate on verifying the content of a release and preventing problematic releases. The polling takes the form of a thread in Discussions, available at With the package packed in step 4.2, execute in the apollo root directory mvn docker:build -pl apollo-configservice,apollo-adminservice,apollo-portal Note: If you get an error, you may need to restart the local docker Publish via github workflow. cd helm package apollo-portal && helm package apollo-service mv *.tgz docs cd docs helm repo index . Create a pull request to merge the above products into the branch. Reference:
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: breaking-12283.en.md

Fixed the `resource_opts` configuration schema for the GCP PubSub Producer connector so that it contains only relevant fields. This affects the creation of GCP PubSub Producer connectors via HOCON configuration (`connectors.gcppubsubproducer.*.resource_opts`) and the HTTP APIs `POST /connectors` / `PUT /connectors/:id` for this particular connector type.
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: definewindow.md

The `DefineWindow` rule defines a temporal window specification. A window is a mechanism that caches, stores or buffers events for processing over a finite temporal range. The time range can be based on the number of events, the wall clock or other defined parameters. The named window can be instanciated via operations that support windows such as the `select` operation.
Project: Ansible (Provisioning / Automation & Configuration)
File: resolved.md

Hi! We have ascertained that the following PR/commits should resolve this question or problem for you. << INSERT SHA/PR LINK HERE >> This should be included newer releases starting with << RELEASE/the next [major] release(s) >>. Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time. The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved. See this page for a complete list of communication channels and their purposes: <https://docs.ansible.com/ansible/latest/community/communication.html> Thank you!
Project: Meshery (Provisioning / Automation & Configuration)
File: whereabouts.md

layout: integration title: Whereabouts subtitle: Collaborative and visual infrastructure as code for Whereabouts image: /assets/img/integrations/whereabouts/icons/color/whereabouts-color.svg permalink: extensibility/integrations/whereabouts docURL: https://docs.meshery.io/extensibility/integrations/whereabouts description: Whereabouts is a CNI IPAM plugin for Kubernetes clusters. It dynamically assigns IP addresses cluster-wide. Features both IPv4 and IPv6 addressing. integrations-category: Cloud Native Network integrations-subcategory: CNI registrant: GitHub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.55.md

layout: release date: 2023-02-24 tag: v0.6.55 language: en Complete prettification flow @Revolyssup (#7185) Fix whitespacing issue @Revolyssup (#7182) Replace the older GetLatestReleaseTag function with meshkit function @Revolyssup (#7188) fix wrongly handled error causing panic in mesheryctl @Revolyssup (#7189) Disabled Signup button for the users who already have the extension/the capability to use meshmap @krishna9304 (#7177) Retained the expected behaviour for consecutive clicks on the K8sContextMenu icon and Settings icon respectively @krishna9304 (#7186) feat: rjsf dependency upgrade to v5 @harkiratsm (#7060) Fix NATS/MeshSync connectivity test @MUzairS15 (#5866) [chore] Improve Extension Proxy @theBeginner86 (#7184) [chore] Update Remote Provider URL for dev env @theBeginner86 (#7183) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @MUzairS15, @Revolyssup, @harkiratsm, @krishna9304, @leecalcote, @theBeginner86 and l5io
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: command.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: busybox spec: components: name: busybox type: webservice properties: image: busybox cmd: ["sleep", "86400"] traits: type: sidecar properties: name: sidecar-nginx image: nginx type: command properties: containers: containerName: busybox command: ["sleep", "8640000"] containerName: sidecar-nginx args: ["-q"] ```
Project: StarRocks (App Definition and Development / Database)
File: second.md

displayed_sidebar: "English" Returns the second part for a given date. The return value ranges from 0 to 59. The `date` parameter must be of the DATE or DATETIME type. ```Haskell INT SECOND(DATETIME date) ``` ```Plain Text MySQL > select second('2018-12-31 23:59:59'); +--+ |second('2018-12-31 23:59:59')| +--+ | 59 | +--+ ``` SECOND
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: secret.md

Give the container access to a secret. Can be specified multiple times. A secret is a blob of sensitive data which a container needs at runtime but is not stored in the image or in source control, such as usernames and passwords, TLS certificates and keys, SSH keys or other important generic strings or binary content (up to 500 kb in size). When secrets are specified as type `mount`, the secrets are copied and mounted into the container when a container is created. When secrets are specified as type `env`, the secret is set as an environment variable within the container. Secrets are written in the container at the time of container creation, and modifying the secret using `podman secret` commands after the container is created affects the secret inside the container. Secrets and its storage are managed using the `podman secret` command. Secret Options `type=mount|env` : How the secret is exposed to the container. `mount` mounts the secret into the container as a file. `env` exposes the secret as an environment variable. Defaults to `mount`. `target=target` : Target of secret. For mounted secrets, this is the path to the secret inside the container. If a fully qualified path is provided, the secret is mounted at that location. Otherwise, the secret is mounted to `/run/secrets/target` for linux containers or `/var/run/secrets/target` for freebsd containers. If the target is not set, the secret is mounted to `/run/secrets/secretname` by default. For env secrets, this is the environment variable key. Defaults to `secretname`. `uid=0` : UID of secret. Defaults to 0. Mount secret type only. `gid=0` : GID of secret. Defaults to 0. Mount secret type only. `mode=0` : Mode of secret. Defaults to 0444. Mount secret type only. Examples Mount at `/my/location/mysecret` with UID 1: ``` --secret mysecret,target=/my/location/mysecret,uid=1 ``` Mount at `/run/secrets/customtarget` with mode 0777: ``` --secret mysecret,target=customtarget,mode=0777 ``` Create a secret environment variable called `ENVSEC`: ``` --secret mysecret,type=env,target=ENVSEC ```