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

displayed_sidebar: "English" Updates Hive and Hudi metadata cached in StarRocks. This statement is used in one of the following scenarios: External table: When using a Hive external table or Hudi external table to query data in Apache Hive or Apache Hudi, you can execute this statement to update the metadata of a Hive table or Hudi table cached in StarRocks. External catalog: When using a or to query data in Hive or Hudi, you can execute this statement to update the metadata of a Hive table or Hudi table cached in StarRocks. Hive external table: is created and stored in StarRocks. You can use it to query Hive data. Hudi external table: is created and stored in StarRocks. You can use it to query Hudi data. Hive table: is created and stored in Hive. Hudi table: is created and stored in Hudi. The following describes the syntaxes and parameters based on different cases: External table ```SQL REFRESH EXTERNAL TABLE table_name [PARTITION ('partition_name', ...)] ``` | Parameter | Required | Description | | -- | | | | table_name | Yes | The name of a Hive external table or Hudi external table. | | partition_name | No | The names of the partitions of a Hive table or Hudi table. Specifying this parameter updates the metadata of the partitions of the Hive table and Hudi table cached in StarRocks. | External catalog ```SQL REFRESH EXTERNAL TABLE table_name [PARTITION ('partition_name', ...)] ``` | Parameter | Required | Description | | - | | | | external_catalog | No | The name of a Hive catalog or Hudi catalog. | | db_name | No | The name of the database where a Hive table or Hudi table resides. | | table_name | Yes | The name of a Hive table or a Hudi table. | | partition_name | No | The names of the partitions of a Hive table or Hudi table. Specifying this parameter updates the metadata of the partitions of the Hive table and Hudi table cached in StarRocks. | Only users who have the `ALTER_PRIV` privilege can execute this statement to update the metadata of Hive tables and Hudi tables cached in StarRocks. Usage examples in different cases are as follows: Example 1: Update the cached metadata of the corresponding Hive table in StarRocks by specifying the external table `hive1`. ```SQL REFRESH EXTERNAL TABLE hive1; ``` Example 2: Update the cached metadata of the partitions of the corresponding Hudi table in StarRocks by specifying the external table `hudi1` and the partitions of the corresponding Hudi table. ```SQL REFRESH EXTERNAL TABLE hudi1 PARTITION ('date=2022-12-20', 'date=2022-12-21'); ``` Example 1: Update the cached metadata of `hive_table` in StarRocks. ```SQL REFRESH EXTERNAL TABLE hivecatalog.hivedb.hive_table; ``` Or ```SQL USE hivecatalog.hivedb; REFRESH EXTERNAL TABLE hive_table; ``` Example 2: Update the cached metadata of the partitions of `hudi_table` in StarRocks. ```SQL REFRESH EXTERNAL TABLE hudicatalog.hudidb.hudi_table PARTITION ('date=2022-12-20', 'date=2022-12-21'); ```
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: local-mode.md

sidebar_position: 2 Only for test. The most recommended way to use SeaTunnel Engine in the production environment is . Update the auto-increment to true in the $SEATUNNEL_HOME/config/hazelcast.yaml ```shell $SEATUNNELHOME/bin/seatunnel.sh --config $SEATUNNELHOME/config/v2.batch.config.template -e local ```
Project: KICS (Provisioning / Security & Compliance)
File: eeb4d37a-3c59-4789-a00c-1509bc3af1e5.md

title: User With Privilege Escalation By Actions 'iam:PutRolePolicy' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: eeb4d37a-3c59-4789-a00c-1509bc3af1e5 Query name: User With Privilege Escalation By Actions 'iam:PutRolePolicy' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: User with privilege escalation by actions 'iam:PutRolePolicy' 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 "awsiamuser" "cosmic" { name = "cosmic" } resource "awsiamuserpolicy" "testinline_policy" { name = "testinlinepolicy" user = awsiamuser.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:PutRolePolicy", ] Effect = "Allow" Resource = "*" }, ] }) } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" users = [awsiamuser.cosmic.name] roles = [awsiamrole.role.name] groups = [awsiamgroup.group.name] } ``` ```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: ClickHouse (App Definition and Development / Database)
File: v20.12.7.3-stable.md

Backported in : Uninitialized memory read was possible in encrypt/decrypt functions if empty string was passed as IV. This closes . (). Backported in : Fix rare bug when some replicated operations (like mutation) cannot process some parts after data corruption. Fixes . (). Backported in : Check if table function `view` is used in expression list and throw an error. This fixes . (). Backported in : Fix `LOGICALERROR` for `joinuse_nulls=1` when JOIN contains const from SELECT. (). Backported in : Add proper checks while parsing directory names for async INSERT (fixes SIGSEGV). ().
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: opening-pull-requests.md

title: Opening Pull Requests weight: 30 Changes to Operator SDK are submitted via to the relevant repository. Most PRs will be to the . Add for your change, and ensure they run and pass in CI. Add a if necessary. Add relevant . Rebase your commits on master and squash them into a single commit. Write a concise commit message that references the issue number. Push your commit to your fork and . Before a pull request can be merged, tests must pass in CI and it must be reviewed. A PR must be approved by 2 reviewers, one of which must be at least at least a reviewer and one of which must be at least an approver, per the . Please feel free to message the developers to get eyes on your PR, whether through @'ing on the PR itself, the #operator-sdk-dev channel on Kubernetes slack, or by attending the Operator SDK .
Project: KICS (Provisioning / Security & Compliance)
File: 55975007-f6e7-4134-83c3-298f1fe4b519.md

title: SQL Server Alert Email Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 55975007-f6e7-4134-83c3-298f1fe4b519 Query name: SQL Server Alert Email Disabled Platform: Terraform Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: SQL Server alert email should be enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "azurermmssqlserversecurityalert_policy" "positive1" { resourcegroupname = azurermresourcegroup.example.name servername = azurermsql_server.example.name state = "Enabled" storageendpoint = azurermstorageaccount.example.primaryblob_endpoint storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key disabled_alerts = [ "Sql_Injection", "Data_Exfiltration" ] retention_days = 20 } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="12" resource "azurermmssqlserversecurityalert_policy" "positive2" { resourcegroupname = azurermresourcegroup.example.name servername = azurermsql_server.example.name state = "Enabled" storageendpoint = azurermstorageaccount.example.primaryblob_endpoint storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key disabled_alerts = [ "Sql_Injection", "Data_Exfiltration" ] retention_days = 20 emailaccountadmins = false } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermmssqlserversecurityalert_policy" "negative" { resourcegroupname = azurermresourcegroup.example.name servername = azurermsql_server.example.name state = "Enabled" storageendpoint = azurermstorageaccount.example.primaryblob_endpoint storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key disabled_alerts = [ "Sql_Injection", "Data_Exfiltration" ] retention_days = 20 emailaccountadmins = true } ```
Project: YugabyteDB (App Definition and Development / Database)
File: dbeaver-ysql.md

title: Using DBeaver with YSQL headerTitle: Using DBeaver linkTitle: DBeaver description: Use the DBeaver multi-platform database tool to explore and query YugabyteDB YSQL. menu: v2.18: identifier: dbeaver-1-ysql parent: tools weight: 40 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../dbeaver-ysql/" class="nav-link active"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> <li > <a href="../dbeaver-ycql/" class="nav-link"> <i class="icon-cassandra" aria-hidden="true"></i> YCQL </a> </li> </ul> is a free multi-platform, cross-platform database tool for developers, SQL programmers, and database administrators. DBeaver supports various databases including PostgreSQL, MariaDB, MySQL, YugabyteDB. In addition, there are plugins and extensions for other databases that support the JDBC driver. supports non-JDBC data sources and allows you to explore Yugabyte YCQL tables. Before you can start using DBeaver with YSQL, you need to perform the following: Start YugabyteDB. For more information, see . Install JRE or JDK for Java 8 or later. Installers can be downloaded from , , or . Note that some of the installers include a JRE accessible only to DBeaver. Install DBeaver as follows: Download the distribution package for your OS from . Start the installation by following instructions in . You can create a connection as follows: Launch DBeaver. Navigate to Database > New Connection to open the Connect to database window shown in the following illustration. In the Select your database list, select YugabyteDB, and then click Next.\ \ Use Connection Settings to specify the following: Host: localhost Port: 5433 Database: replace the default value postgres with yugabyte . User: yugabyte Password: leave blank if YSQL authentication is not enabled. If enabled, add the password for yugabyte (default is yugabyte). Select Show all databases. Click Test Connection to verify that the connection is successful, as shown in the following illustration:\ \ DBeaver's Database Navigator should display Yugabyte - localhost. You can expand the list to see all databases available to the Yugabyte User, as shown in the following illustration: For sample databases to explore YugabyteDB using DBeaver, see .
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.1.2.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Add extra info to JH files | Major | . | Arun C Murthy | Zhijie Shen | | | Save memory by set capacity, load factor and concurrency level for ConcurrentHashMap in TaskInProgress | Major | mrv1 | yunjiong zhao | yunjiong zhao | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | DataNode#checkDiskError should not be called on network errors | Major | datanode | Rohit Kochar | Rohit Kochar | | | TestPipelinesFailover#testPipelineRecoveryStress fails sporadically | Major | test | Chris Nauroth | Chris Nauroth | | | JT can show the same job multiple times in Retired Jobs section | Minor | . | Arun C Murthy | Arun C Murthy | | | Syslog missing from Map/Reduce tasks | Major | tasktracker | Yesha Vora | Arun C Murthy | | | CapacityScheduler incorrectly utilizes extra-resources of queue for high-memory jobs | Major | capacity-sched | Sergey Tryuber | Sergey Tryuber | | | TestBalancerWithNodeGroup times out | Major | balancer & mover | Tsz Wo Nicholas Sze | Junping Du | | | Diagnostic logging while loading name/edits files | Major | namenode | Arpit Agarwal | Suresh Srinivas | | | Job failed because of JvmManager running into inconsistent state | Major | tasktracker | yunjiong zhao | yunjiong zhao | | | Ampersand in JSPUtil.java is not escaped | Minor | jobtracker | Bohou Li | Bohou Li | | | BlockDecompressorStream#decompress will throw EOFException instead of return -1 when EOF | Critical | . | Zhijie Shen | Zhijie Shen | | | Delegation Token renewal exception in jobtracker logs | Critical | . | Venkat Ranganathan | Venkat Ranganathan | | | MetricsDynamicMBeanBase has concurrency issues in createMBeanInfo | Critical | metrics | Liang Xie | Liang Xie | | | CombineInputFormat isn't thread safe affecting HiveServer | Major | . | Vinod Kumar Vavilapalli | Vinod Kumar Vavilapalli | | | JobTracker memory leak caused by CleanupQueue reopening FileSystem | Critical | jobtracker | Sandy Ryza | Sandy Ryza | | | Deadlock between RenewalTimerTask methods cancel() and run() | Major | . | Karthik Kambatla | Karthik Kambatla | | | fix hadoop.spec to add task-log4j.properties | Major | build | Giridharan Kesavan | Giridharan Kesavan | | | JVM reuse is incompatible with LinuxTaskController (and therefore incompatible with Security) | Critical | task-controller, tasktracker | George Datskos | sam liu | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | The eclipse-plugin cannot work in my environment | Minor | contrib/eclipse-plugin | huangxing | |
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: testing.md

title: Testing linkTitle: Testing weight: 6 On all PRs, a suite of static and cluster tests is run against your changes in a CI environment. These tests can also be run locally, which is discussed . Static tests consist of , formatting, and doc link tests. Cluster tests consist of several test types: End-to-end (e2e): simulate the "happy path" usage of the `operator-sdk` binary and resulting operator project. Integration: test components of the `operator-sdk` binary and features of scaffolded projects that are bound to external projects, such as . Subcommand: ensure individual subcommands function as intended with a variety of input options. Always run tests before submitting a PR to reduce the number of needless CI errors. ```sh make test-static ``` ```sh make test-all ``` If running tests locally, access to a Kubernetes cluster of a is required. These tests require `KUBECONFIG` be set or kubeconfig file be present in a default location like `$HOME/.kube/config`. You will also need to set up an `envtest` environment for cluster tests. Follow for setup instructions. A local cluster is used for running tests. All the tests are run through the . Run `make help` for a full list of available tests.
Project: SlimToolkit (Provisioning / Security & Compliance)
File: CONDUCT.md

Cobra will follow a steady release cadence. Non breaking changes will be released as minor versions quarterly. Patch bug releases are at the discretion of the maintainers. Users can expect security patch fixes to be released within relatively short order of a CVE becoming known. For more information on security patch fixes see the CVE section below. Releases will follow . Users tracking the Master branch should expect unpredictable breaking changes as the project continues to move forward. For stability, it is highly recommended to use a release. We will maintain two major releases in a moving window. The N-1 release will only receive bug fixes and security updates and will be dropped once N+1 is released. Deprecation of Go versions or dependent packages will only occur in major releases. To reduce the change of this taking users by surprise, any large deprecation will be preceded by an announcement in the and an Issue on Github. Maintainers will make every effort to release security patches in the case of a medium to high severity CVE directly impacting the library. The speed in which these patches reach a release is up to the discretion of the maintainers. A low severity CVE may be a lower priority than a high severity one. Cobra maintainers will use GitHub issues and the as the primary means of communication with the community. This is to foster open communication with all users and contributors. Breaking changes are generally allowed in the master branch, as this is the branch used to develop the next release of Cobra. There may be times, however, when master is closed for breaking changes. This is likely to happen as we near the release of a new version. Breaking changes are not allowed in release branches, as these represent minor versions that have already been released. These version have consumers who expect the APIs, behaviors, etc, to remain stable during the lifetime of the patch stream for the minor release. Examples of breaking changes include: Removing or renaming exported constant, variable, type, or function. Updating the version of critical libraries such as `spf13/pflag`, `spf13/viper` etc... Some version updates may be acceptable for picking up bug fixes, but maintainers must exercise caution when reviewing. There may, at times, need to be exceptions where breaking changes are allowed in release branches. These are at the discretion of the project's maintainers, and must be carefully considered before merging. Maintainers will ensure the Cobra test suite utilizes the current supported versions of Golang. Changes to this document and the contents therein are at the discretion of the maintainers. None of the contents of this document are legally binding in any way to the maintainers or the users.
Project: KICS (Provisioning / Security & Compliance)
File: 8810968b-4b15-421d-918b-d91eb4bb8d1d.md

title: Cluster Labels Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8810968b-4b15-421d-918b-d91eb4bb8d1d Query name: Cluster Labels Disabled Platform: GoogleDeploymentManager Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Kubernetes Clusters must be configured with labels, which means the attribute 'resourceLabels' must be defined<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" resources: name: cluster type: container.v1.cluster properties: name: my-cluster ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: cluster type: container.v1.cluster properties: name: my-cluster resourceLabels: name: "wrench" ```
Project: Harbor (Provisioning / Container Registry)
File: 7-01-Proj-replication-rules-add.md

Test 7-01 - Create Replication Policy ======= To verify that admin user can create a replication rule. User guide This test requires that at least two Harbor instances are running and available. Login UI as admin user. In `Administration->Replications` page, create a new rule and fill in name and description. Choose a project by clicking the icon on the right of `Projects`. Add repository and tag filter. Choose an endpoint, create a new one if no endpoint exists. Select a triggering condition: Immediate/Manual/Scheduled, check/uncheck the `Delete remote images when locally deleted` if choosing `Immediate`. Check/uncheck the option `Replicate existing images immediately`. Save the rule. Repeat steps 1-8 under `Projects->Project_Name->Replication` page. In step8, a rule will be added. None
Project: StarRocks (App Definition and Development / Database)
File: array_difference.md

displayed_sidebar: "English" Calculates the difference between every two neighboring elements of an array by subtracting each element from its following element and returns an array that consists of the differences. ```SQL array_difference(input) ``` `input`: the array for which you want to calculate the differences between every two neighboring elements. Returns an array of the same data type and length as the array that you specify in the `input` parameter. Example 1: ```Plain mysql> SELECT array_difference([342, 32423, 213, 23432]); +--+ | array_difference([342,32423,213,23432]) | +--+ | [0,32081,-32210,23219] | +--+ ``` Example 2: ```Plain mysql> SELECT array_difference([342, 32423, 213, null, 23432]); +-+ | array_difference([342,32423,213,NULL,23432]) | +-+ | [0,32081,-32210,null,null] | +-+ ``` Example 3: ```Plain mysql> SELECT array_difference([1.2, 2.3, 3.2, 4324242.55]); +--+ | array_difference([1.2,2.3,3.2,4324242.55]) | +--+ | [0,1.1,0.9,4324239.35] | +--+ ``` Example 4: ```Plain mysql> SELECT array_difference([false, true, false]); +-+ | array_difference([FALSE, TRUE, FALSE]) | +-+ | [0,1,-1] | +-+ ```
Project: SuperEdge (Provisioning / Automation & Configuration)
File: CHANGELOG-0.2.md

- - lite-apiserver now handles certificate rotation automatically. (, ) Added 3 new caching storage options to lite-apiserver, including memory and local KV storage using Badger or Bolt. (, ) Added new StatefulsetGrid ServiceGroup resource for running statefulset workload. Headless service is supported for StatefulsetGrid. (, ) Added canary deployment support for DeploymentGrid and StatefulSetGrid workloads. (, ) Added reuse policy for lite-apiserver proxy. (, ) Fixed a bug in Tunnel that causes missing request body in HTTP POST forwarding. (, ) Fixed TCP proxy forwarding failure. (, ) Introduction to new StatefulsetGrid resource. Introduction to canary deployment for DeploymentGrid and StatefulSetGrid. Tunnel configuration guide and sample configs. Updated lite-apiserver architecture diagram and added usage example.
Project: KubeEdge (Provisioning / Automation & Configuration)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: cloudflare-worker.md

title: Cloudflare Worker Enforcement of OPA Policies Using Wasm software: cloudflare labels: layer: application category: serverless code: https://github.com/open-policy-agent/contrib/tree/master/wasm/cloudflare-worker tutorials: https://github.com/open-policy-agent/contrib/blob/master/wasm/cloudflare-worker/README.md docs_features: wasm-integration: note: | This example project in uses the to enforce policy at the edge of Cloudflare's network. Cloudflare Workers are a serverless platform that supports Wasm. This integration uses OPA's Wasm compiler to generate code enforced at the edge of Cloudflare's network.