cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: belllabs.md

title: "Bell Labs" icon: /images/logos/powered-by/belllabs.png hasLink: "https://www.bell-labs.com/#gref" <!-- Licensed 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. -->
Project: ClickHouse (App Definition and Development / Database)
File: limit-by.md

slug: /en/sql-reference/statements/select/limit-by sidebar_label: LIMIT BY A query with the `LIMIT n BY expressions` clause selects the first `n` rows for each distinct value of `expressions`. The key for `LIMIT BY` can contain any number of . ClickHouse supports the following syntax variants: `LIMIT [offset_value, ]n BY expressions` `LIMIT n OFFSET offset_value BY expressions` During query processing, ClickHouse selects data ordered by sorting key. The sorting key is set explicitly using an clause or implicitly as a property of the table engine (row order is only guaranteed when using , otherwise the row blocks will not be ordered due to multi-threading). Then ClickHouse applies `LIMIT n BY expressions` and returns the first `n` rows for each distinct combination of `expressions`. If `OFFSET` is specified, then for each data block that belongs to a distinct combination of `expressions`, ClickHouse skips `offsetvalue` number of rows from the beginning of the block and returns a maximum of `n` rows as a result. If `offsetvalue` is bigger than the number of rows in the data block, ClickHouse returns zero rows from the block. :::note `LIMIT BY` is not related to . They can both be used in the same query. ::: If you want to use column numbers instead of column names in the `LIMIT BY` clause, enable the setting . Sample table: ``` sql CREATE TABLE limit_by(id Int, val Int) ENGINE = Memory; INSERT INTO limit_by VALUES (1, 10), (1, 11), (1, 12), (2, 20), (2, 21); ``` Queries: ``` sql SELECT * FROM limit_by ORDER BY id, val LIMIT 2 BY id ``` ``` text idval 1 10 1 11 2 20 2 21 ``` ``` sql SELECT * FROM limit_by ORDER BY id, val LIMIT 1, 2 BY id ``` ``` text idval 1 11 1 12 2 21 ``` The `SELECT * FROM limit_by ORDER BY id, val LIMIT 2 OFFSET 1 BY id` query returns the same result. The following query returns the top 5 referrers for each `domain, device_type` pair with a maximum of 100 rows in total (`LIMIT n BY + LIMIT`). ``` sql SELECT domainWithoutWWW(URL) AS domain, domainWithoutWWW(REFERRER_URL) AS referrer, device_type, count() cnt FROM hits GROUP BY domain, referrer, device_type ORDER BY cnt DESC LIMIT 5 BY domain, device_type LIMIT 100 ```
Project: Juju (Provisioning / Automation & Configuration)
File: lts-update-issues.md

LTS Update Issues ================= When we update ubuntu LTS versions we run into some issues updating tests. When updating from Trusty to Xenial we attempted to simplify future updates. There are still a few places that need modification when an LTS update happends. `grep -r LTS-dependent` at the top of the core repo to find the locations that are expected to require updates at the next LTS release. As of this writing that would be in the following files: cmd/juju/service/bundle_test.go provider/ec2/export_test.go provider/ec2/image_test.go testing/base.go There will likely be other locations by the next release, but this should provide a headstart.
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_create_foreign_table.md

title: CREATE FOREIGN TABLE statement [YSQL] headerTitle: CREATE FOREIGN TABLE linkTitle: CREATE FOREIGN TABLE description: Use the CREATE FOREIGN TABLE statement to create a foreign table. menu: v2.18: identifier: ddlcreateforeign_table parent: statements type: docs Use the `CREATE FOREIGN TABLE` command to create a foreign table. {{%ebnf%}} createforeigntable {{%/ebnf%}} Create a new foreign table named table_name. If table_name already exists in the specified database, an error will be raised unless the `IF NOT EXISTS` clause is used. The `COLLATE` clause can be used to specify a collation for the column. The `SERVER` clause can be used to specify the name of the foreign server to use. The `OPTIONS` clause specifies options for the foreign table. The permitted option names and values are specific to each foreign data wrapper. The options are validated using the FDWs validator function. Basic example. ```plpgsql yugabyte=# CREATE FOREIGN TABLE mytable (col1 int, col2 int) SERVER myserver OPTIONS (schema 'externalschema', table 'external_table'); ```
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at oss-conduct@uber.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at .
Project: ClickHouse (App Definition and Development / Database)
File: v21.4.4.30-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Now replicas that are processing the `ALTER TABLE ATTACH PART (). Backported in : Improved performance of `dictGetHierarchy`, `dictIsIn` functions. Added functions `dictGetChildren(dictionary, key)`, `dictGetDescendants(dictionary, key, level)`. Function `dictGetChildren` return all children as an array if indexes. It is a inverse transformation for `dictGetHierarchy`. Function `dictGetDescendants` return all descendants as if `dictGetChildren` was applied `level` times recursively. Zero `level` value is equivalent to infinity. Closes . (). Backported in : Added function `dictGetOrNull`. It works like `dictGet`, but return `Null` in case key was not found in dictionary. Closes . (). Backported in : Add aliases `simpleJSONExtract/simpleJSONHas` to `visitParam/visitParamExtract{UInt, Int, Bool, Float, Raw, String}`. Fixes . (). Backported in : Set `backgroundfetchespool_size` to 8 that is better for production usage with frequent small insertions or slow ZooKeeper cluster. (). Backported in : Raised the threshold on max number of matches in result of the function `extractAllGroupsHorizontal`. (). Backported in : Fixed a bug with unlimited wait for auxiliary AWS requests. (). Backported in : fixed `formatDateTime()` on `DateTime64` and "%C" format specifier fixed `toDateTime64()` for large values and non-zero scale. ... (). Backported in : Fix error `Cannot find column in ActionsDAG result` which may happen if subquery uses `untuple`. Fixes . (). Backported in : Remove non-essential details from suggestions in clickhouse-client. This closes . (). Backported in : Fixed `Table .inner_id... doesn't exist` error when selecting from Materialized View after detaching it from Atomic database and attaching back. (). Backported in : Some values were formatted with alignment in center in table cells in `Markdown` format. Not anymore. (). Backported in : Enable the bundled openldap on ppc64le ... ().
Project: Vald (App Definition and Development / Database)
File: index-manager.md

Vald Index Manager is the component that controls the indexing process of Vald Agent Pods in the same Vald cluster. Vald Index Manager has a unique and simple role in controlling the indexing timing for all Vald Agent pods in the Vald cluster. It requires `Vald Discoverer` to fulfill its responsibility. This chapter shows the main features to fulfill Vald Index Managers role. Vald Index Manager gets the IP addresses of each Vald Agent pod from Vald Discoverer when its container starts. In addition, when IP address changes, Vald Index Manager gets the new IP address from Vald Discoverer. Vald Index Manager uses these for the controlling indexing process. When Vald Agent Pod creates or saves indexes on its container memory, it blocks all searching requests from the user and returns an error instead of a search result. Stop-the-world happens when all Vald Agent pods run the function involved in the indexing operation, e.g., `createIndex`, simultaneously. Vald Index Manager manages the indexing process of all Vald Agent pods to prevent this event. Vald Index Manager uses a Vald Agent pods' IP address list from Vald Discoverer and index information, including the stored index count, uncommitted index count, creating index count, and saving index count, from each Vald Agent pod. The control process is Vald Index Manager sends `createIndex` requests for concurrency simultaneously, sends a new request when the job is finished and continues until it sends to all agents. At the end of each process, Vald Index Manager updates the index information from each Vald Agent pod. Vald Index Manager runs this process periodically by set time intervals. <div class="notice"> Concurrency means the number of Vald Agent pods for simultaneously sending requests for the indexing operation.<BR> When the Vald Agent pod has no uncommitted index or is running the indexing function already, it does not send the request. </div>
Project: Falco (Provisioning / Security & Compliance)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thanks for sending a pull request! Here are some tips for you: If this is your first time, please read our contributor guidelines in the https://github.com/falcosecurity/.github/blob/main/CONTRIBUTING.md file. Please label this pull request according to what type of issue you are addressing. Please add a release note! If the PR is unfinished while opening it specify a wip in the title before the actual title, for example, "wip: my awesome feature" --> What type of PR is this? Uncomment one (or more) `/kind <>` lines: /kind bug /kind cleanup /kind design /kind documentation /kind failing-test /kind feature /kind release <!-- Please remove the leading whitespace before the `/kind <>` you uncommented. --> Any specific area of the project related to this PR? Uncomment one (or more) `/area <>` lines: /area build /area engine /area tests /area proposals /area CI <!-- Please remove the leading whitespace before the `/area <>` you uncommented. --> What this PR does / why we need it: Which issue(s) this PR fixes: <!-- Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. If PR is `kind/failing-tests` or `kind/flaky-test`, please post the related issues/tests in a comment and do not use `Fixes`. --> Fixes # Special notes for your reviewer: Does this PR introduce a user-facing change?: <!-- If NO, just write "NONE" in the release-note block below. If YES, a release note is required, enter your release note in the block below. The convention is the same as for commit messages: https://github.com/falcosecurity/.github/blob/main/CONTRIBUTING.md#commit-convention If the PR introduces non-backward compatible changes, please add a line starting with "BREAKING CHANGE:" and describe what changed. For example, `BREAKING CHANGE: the API interface of the rule engine has changed`. Your note will be included in the changelog. --> ```release-note ```
Project: Meshery (Provisioning / Automation & Configuration)
File: rook.md

layout: integration title: Rook subtitle: Collaborative and visual infrastructure as code for Rook image: /assets/img/integrations/rook/icons/color/rook-color.svg permalink: extensibility/integrations/rook docURL: https://docs.meshery.io/extensibility/integrations/rook description: integrations-category: Runtime integrations-subcategory: Cloud Native Storage registrant: Artifact Hub 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: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: google-kubernetes-engine.md

title: GKE Policy Automation software: kubernetes google-kubernetes-engine labels: category: containers layer: orchestration code: https://github.com/google/gke-policy-automation tutorials: https://github.com/google/gke-policy-automation/tree/main/gke-policies inventors: google docs_features: kubernetes: note: | The GKE Policy Automation project provides a set of policies for validating Kubernetes clusters running on GKE. Review the Tool and policy library for reviewing Google Kubernetes Engine clusters against best practices
Project: StarRocks (App Definition and Development / Database)
File: SHOW_CATALOGS.md

displayed_sidebar: "English" Query all catalogs in the current StarRocks cluster, including the internal catalog and external catalogs. NOTE SHOW CATALOGS returns external catalogs to users who have the USAGE privilege on that external catalog. If users or roles do not have this privilege on any external catalog, this command returns only the default_catalog. ```SQL SHOW CATALOGS ``` ```SQL +-+--+-+ | Catalog | Type | Comment | +-+--+-+ ``` The following table describes the fields returned by this statement. | Field | Description | | - | | | Catalog | The catalog name. | | Type | The catalog type. `Internal` is returned if the catalog is `default_catalog`. The corresponding catalog type is returned if the catalog is an external catalog, such as `Hive`, `Hudi`, or `Iceberg`. | | Comment | The comments of a catalog. StarRocks does not support adding comments to an external catalog. Therefore, the value is `NULL` for an external catalog. If the catalog is `defaultcatalog`, the comment is `An internal catalog contains this cluster's self-managed tables.` by default. `defaultcatalog` is the only internal catalog in a StarRocks cluster. | Query all catalogs in the current cluster. ```SQL SHOW CATALOGS\G row * Catalog: default_catalog Type: Internal Comment: An internal catalog contains this cluster's self-managed tables. row * Catalog: hudi_catalog Type: Hudi Comment: NULL row * Catalog: iceberg_catalog Type: Iceberg Comment: NULL ```
Project: KICS (Provisioning / Security & Compliance)
File: 9192e0f9-eca5-4056-9282-ae2a736a4088.md

title: Pod Security Policy Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9192e0f9-eca5-4056-9282-ae2a736a4088 Query name: Pod Security Policy Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Kubernetes Clusters must have Pod Security Policy controller enabled, which means there must be a 'podsecuritypolicy_config' with the 'enabled' attribute equal to true<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2 18" resource "googlecontainercluster" "positive1" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 timeouts { create = "30m" update = "40m" } } resource "googlecontainercluster" "positive2" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 podsecuritypolicy_config { enabled = false } timeouts { create = "30m" update = "40m" } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecontainercluster" "negative1" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 podsecuritypolicy_config { enabled = "true" } timeouts { create = "30m" update = "40m" } } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: spicule.md

title: "Spicule" icon: /images/logos/powered-by/spicule.png hasLink: "https://www.spicule.co.uk/posts/welcome" <!-- Licensed 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. -->
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_kubeblocks_config.md

title: kbcli kubeblocks config KubeBlocks config. ``` kbcli kubeblocks config [flags] ``` ``` kbcli kubeblocks config --set snapshot-controller.enabled=true ``` ``` -h, --help help for config --set stringArray Set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2) --set-file stringArray Set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2) --set-json stringArray Set JSON values on the command line (can specify multiple or separate values with commas: key1=jsonval1,key2=jsonval2) --set-string stringArray Set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2) -f, --values strings Specify values in a YAML file or a URL (can specify multiple) ``` ``` --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 ``` - KubeBlocks operation commands.
Project: ShardingSphere (App Definition and Development / Database)
File: 2FA.en.md

+++ title = "2FA" weight = 4 chapter = true +++ Two factor authentication (2FA) refers to the authentication method that combines both passport, and an object (credit card, SMS phone, token or biomarkers as fingerprint) to identify a user. To ensure the security of the committers account, we need you to enable 2FA to sign in and contribute codes on GitHub. More details, please refer to . To be noticed: If you do not enable 2FA, you will be removed from the project and unable to access our repositories and the fork from our private repository. For detailed operations, please refer to . After enabling 2FA, you need to sign in GitHub with the way of username/password + mobile phone authentication code. Tips: If you cannot download the APP through the page link, you can search and download Google Authenticator in APP Store. After enabling 2FA, you need to generate a private access Token to perform operations such as git submit and so on. At this time, you will use username + private access Token in replace of username + password to submit codes. For detailed operations, please refer to .
Project: Beam (App Definition and Development / Streaming & Messaging)
File: citibank.md

title: "CitiBank" icon: /images/logos/powered-by/citibank.png hasLink: "https://www.citi.com/" <!-- Licensed 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. -->