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

title: ALTER DATABASE statement [YSQL] headerTitle: ALTER DATABASE linkTitle: ALTER DATABASE description: Use the ALTER DATABASE statement to redefine the attributes of a database. menu: v2.18: identifier: ddlalterdb parent: statements type: docs Use the `ALTER DATABASE` statement to redefine the attributes of a database. {{%ebnf%}} alter_database, alterdatabaseoption {{%/ebnf%}} {{< note title="Note" >}} Some options in DATABASE are under development. {{< /note >}} Specify the name of the database to be altered. Specify `false` to disallow connections to this database. Default is `true`, which allows this database to be cloned by any user with `CREATEDB` privileges. Specify how many concurrent connections can be made to this database. Default of `-1` allows unlimited concurrent connections. S`true` This database can be cloned by any user with `CREATEDB` privileges. Specify `false` to Only superusers or the owner of the database can clone it.
Project: StarRocks (App Definition and Development / Database)
File: covar_pop.md

displayed_sidebar: "English" Returns the population covariance of two expressions. This function is supported from v2.5.10. It can also be used as a window function. ```Haskell COVAR_POP(expr1, expr2) ``` `expr1` and `expr2` must evaluate to TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT, DOUBLE, or DECIMAL. If `expr1` and `expr2` are table columns, this function calculates the population covariance of these two columns. Returns a DOUBLE value. The formula is as follows, where `n` represents the row count of the table: <!--$$ \frac{\sum{i=1}^{n} (xi - \bar{x})(y_i - \bar{y})}{n} $$--> A data row is counted only when the two columns in this row are non-null values. Otherwise, this data row is eliminated from the result. NULL is returned in any input is NULL. Suppose table `agg` has the following data: ```plaintext mysql> select * from agg; ++-+-+ | no | k | v | ++-+-+ | 1 | 10.00 | NULL | | 2 | 10.00 | 11.00 | | 2 | 20.00 | 22.00 | | 2 | 25.00 | NULL | | 2 | 30.00 | 35.00 | ++-+-+ ``` Calculate the population covariance of the `k` and `v` columns: ```plaintext mysql> select no,COVAR_POP(k,v) from agg group by no; ++-+ | no | covar_pop(k, v) | ++-+ | 1 | NULL | | 2 | 79.99999999999999 | ++-+ ```
Project: Timescale (App Definition and Development / Database)
File: MultiNodeDeprecation.md

Multi-node support has been deprecated. TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node support in 2.13 is available for PostgreSQL 13, 14 and 15. This decision was not made lightly, and we want to provide a clear understanding of the reasoning behind this change and the path forward. We began to work on multi-node support in 2018 and released the first version in 2020 to address the growing demand for higher scalability in TimescaleDB deployments. The distributed architecture of multi-node allowed for horizontal scalability of writes and reads to go beyond what a single node could provide. While we added many improvements since the initial launch, the architecture of multi-node came with a number of inherent limitations and challenges that have limited its adoption. Regrettably, only about 1% of current TimescaleDB deployments utilize multi-node, and the complexity involved in maintaining this feature has become a significant obstacle. Its not an isolated feature that can be kept in the product with very little effort since adding new features required extra development and testing to ensure they also worked for multi-node. As we've evolved our single-node product and expanded our cloud offering to serve thousands of customers, we've identified more efficient solutions to meet the scalability needs of our users. First, weve been able and will continue to make big improvements in the write and read performance of single-node. Weve scaled a single-node deployment to process 2 million inserts per second and have seen performance improvements of 10x for common queries. You can read a summary of the latest query performance improvements . And second, we are leveraging cloud technologies that have become very mature to provide higher scalability in a more accessible way. For example, our cloud offering uses object storage to deliver virtually . For those reasons, weve decided to focus our efforts on improving single-node and leveraging cloud technologies to solve for high scalability and as a result weve ended support for multi-node. We understand that this change may raise questions, and we are committed to supporting you through the transition. For current TimescaleDB multi-node users, please refer to our for a step-by-step guide to transition to a single-node configuration. Alternatively, you can continue to use multi-node up to version 2.13. However, please be aware that future versions will no longer include this functionality. If you have any questions or feedback, you can share them in the #multi-node channel in our .
Project: KICS (Provisioning / Security & Compliance)
File: 660360d3-9ca7-46d1-b147-3acc4002953f.md

title: SQL DB Instance With SSL Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 660360d3-9ca7-46d1-b147-3acc4002953f Query name: SQL DB Instance With SSL Disabled Platform: GoogleDeploymentManager Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: Cloud SQL Database Instance should have SSL enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="5" resources: name: sql-instance type: sqladmin.v1beta4.instance properties: settings: tier: db-custom-1-3840 ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="7" resources: name: sql-instance type: sqladmin.v1beta4.instance properties: settings: tier: db-custom-1-3840 ipConfiguration: ipv4Enabled: true ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="9" resources: name: sql-instance type: sqladmin.v1beta4.instance properties: settings: tier: db-custom-1-3840 ipConfiguration: ipv4Enabled: true requireSsl: false ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: sql-instance type: sqladmin.v1beta4.instance properties: settings: tier: db-custom-1-3840 ipConfiguration: requireSsl: true ```
Project: ShardingSphere (App Definition and Development / Database)
File: 2022_09_02_First_Look_at_ShardingSphere_5.2.0_&_In-Person_Meetup_on_Massive_Data_Management_Practices.en.md

+++ title = "First Look at ShardingSphere 5.2.0 & In-Person Meetup on Massive Data Management Practices" weight = 72 chapter = true +++ One more day before ShardingSphere's first in-person meetup in Beijing on September 3, 2022. Join us to learn about the best practices and technical highlights of Apache ShardingSphere's latest release - version`5.2.0`. On Saturday, the first in-person Meetup of the ShardingSphere Community will be held in Beijing on Sep 3, 2022. Four technology experts from the developers community are invited to give you a detailed analysis of the following: How ShardingSphere can rapidly improve the data application ability of ordinary users driven by cloud scenarios. Comparison of data management effect between traditional data processing methods and ShardingSphere. Experience the ShardingSpheres ecosystem simple operation in response to diverse e-commerce scenarios. The community will reveal and demo Apache ShardingSphere v5.2.0 at this meetup. The latest version has taken a giant leap forward in terms of its features, performance, testing, documentation, examples, etc. Time: September 3, 2022 2PM-5PM CST Location: Multi-function Hall, 1st Floor, Intelligent Manufacturing Innovation Center, 32 Zhongguancun Street, Haidian District, Beijing ====================================== First Look at ShardingSphere 5.2.0 ====================================== New Features The `5.2.0` release brings the following new features: Data sharding and SQL audit. MySQL `SHOW PROCESSLIST` & `KILL` features. Specific DistSQL for data migration & heterogeneous migration. Best Practices -- Enhance user's ability to manage ShardingSphere Newly added features, including data sharding, SQL audit, and MySQL `SHOW PROCESSLIST` & `KILL`, can enhance users capability to manage ShardingSphere. Add heterogeneous database migration for users Specific DistSQL for data migration and heterogeneous migration is added. Data can be migrated from Oracle to PostgreSQL. Provide enhanced and complete cloud solutions Version 5.2.0 transfers Helm Charts from ShardingSphere repository to the shardingsphere-on-cloud sub-project, to provide more complete cloud solutions for ShardingSphere. Thanks to the practices and testing of the open source community and internal and external business systems, ShardingSphere can achieve stable and constant iterations. We will continue to help developers participate in building an open source ecosystem and apply cutting-edge technologies in the database field.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: fuzzy_mode_convert_table.md

| json type \ dest type | bool | int | uint | float |string| | | | | |--|--| | number | positive => true <br/> negative => true <br/> zero => false| 23.2 => 23 <br/> -32.1 => -32| 12.1 => 12 <br/> -12.1 => 0|as normal|same as origin| | string | empty string => false <br/> string "0" => false <br/> other strings => true | "123.32" => 123 <br/> "-123.4" => -123 <br/> "123.23xxxw" => 123 <br/> "abcde12" => 0 <br/> "-32.1" => -32| 13.2 => 13 <br/> -1.1 => 0 |12.1 => 12.1 <br/> -12.3 => -12.3<br/> 12.4xxa => 12.4 <br/> +1.1e2 =>110 |same as origin| | bool | true => true <br/> false => false| true => 1 <br/> false => 0 | true => 1 <br/> false => 0 |true => 1 <br/>false => 0|true => "true" <br/> false => "false"| | object | true | 0 | 0 |0|originnal json| | array | empty array => false <br/> nonempty array => true| [] => 0 <br/> [1,2] => 1 | [] => 0 <br/> [1,2] => 1 |[] => 0<br/>[1,2] => 1|original json|
Project: KICS (Provisioning / Security & Compliance)
File: eb3f9744-d24e-4614-b1ff-2a9514eca21c.md

title: Operation Object Parameters With 'body' And 'formatData' locations hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: eb3f9744-d24e-4614-b1ff-2a9514eca21c Query name: Operation Object Parameters With 'body' And 'formatData' locations Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: Operation object parameters should not have both 'body' and 'formatData' locations<br> ```json title="Positive test num. 1 - json file" hl_lines="17" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "limit2", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "object" } }, { "name": "minlimit", "in": "formatData", "description": "min records to return", "required": true } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "formatData", "description": "max records to return", "required": true } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="13" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response parameters: name: limit2 in: body description: max records to return required: true schema: type: object name: minlimit in: formatData description: min records to return required: true parameters: limitParam: name: limit in: formatData description: max records to return required: true ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "limit2", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "object" } }, { "name": "minlimit", "in": "body", "description": "min records to return", "required": true, "schema": { "type": "object" } } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "formatData", "description": "max records to return", "required": true } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response parameters: name: limit2 in: body description: max records to return required: true schema: type: object name: minlimit in: body description: min records to return required: true schema: type: object parameters: limitParam: name: limit in: formatData description: max records to return required: true ```
Project: secureCodeBox (Provisioning / Security & Compliance)
File: adr_0007.md

title: "ADR-0007: Proposal How to Mark Findings With Hashes to Find Duplicates" sidebar_label: "ADR-0007" | <!-- --> | <!-- --> | |-|-| | Status: | DRAFT | | Date: | 2020-11-25 | | Author(s): | Sven Strittmatter | NOTE: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . The secureCodeBox should support the possibility to find duplicate findings easily out of the box. One use case is that a user want to accept a existing finding and want to ignore the same finding in the future. The execution order of hooks is unspecified. The information if a findings hash is a duplicate MUST NOT be stored or maintained in the SCB S3 storage. The SCB MUST NOT remove findings: read-write-hooks may alter them, but never delete or filter them out. Maybe a read-hooks MAY decide to not store a finding into an external system. We generate a hash for each finding, so we can compare findings by the hash and identify duplicates. This hash MUST be mutable and MAY be altered by read-write-hooks because we dont want to introduce an exception to what a read-write-hooks can alter. The parser MUST generate the initial hash of a finding from some of its attributes (e.g. name, location, category ). Each scanner MUST define a default set of attributes used for the hashing. This set of hashed attributes MAY be overwritten. Each read-write-hook MUST update the hash as last step because the hook MAY change a hashed attribute. We implement the hashing step in the parser first with feature flag to evaluate this proposal. We dont need to introduce an ordering for the read-write-hooks. The duplicate detection/handling MUST be done in another service with its own data storage. This is because we have no stable hash until the read-hooks will be executed and these MUST NOT alter the data in SCB itself. But the read-hooks MAY decide to not store data into an external system.
Project: YugabyteDB (App Definition and Development / Database)
File: del.md

title: DEL linkTitle: DEL description: DEL menu: preview: parent: api-yedis weight: 2040 aliases: /preview/api/redis/del /preview/api/yedis/del type: docs Single-key request only. Requests with multiple keys are not yet supported. `DEL key` This command deletes the given `key`. If the `key` does not exist, it is ignored and not counted toward the total number of removed keys. Returns number of keys that were removed. ```sh $ SET yuga1 "America" ``` ``` "OK" ``` ```sh $ SET yuga2 "Africa" ``` ``` "OK" ``` ```sh $ DEL yuga1 ``` ``` 1 ``` ```sh $ DEL notakey ``` ``` 0 ``` ```sh $ DEL yuga1 yuga2 ``` ``` "ERR del: Wrong number of arguments" ``` , , , , , , , , , , ,
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: restart-mysql-cluster.md

title: Restart MySQL cluster description: How to restart a MySQL cluster keywords: [mysql, restart, restart a cluster] sidebar_position: 4 sidebar_label: Restart You can restart all pods of the cluster. When an exception occurs in a database, you can try to restart it. :::note All pods restart in the order of learner -> follower -> leader and the leader may change after the cluster restarts. ::: Restart a cluster. You can use `kbcli` or create an OpsRequest to restart a cluster. Option 1. (Recommended) Use kbcli Configure the values of `components` and `ttlSecondsAfterSucceed` and run the command below to restart a specified cluster. ```bash kbcli cluster restart <name> --components="mysql" \ --ttlSecondsAfterSucceed=30 ``` `components` describes the component name that needs to be restarted. `ttlSecondsAfterSucceed` describes the time to live of an OpsRequest job after the restarting succeeds. Option 2. Create an OpsRequest Run the command below to restart a cluster. ```bash kubectl apply -f - <<EOF apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: name: ops-restart spec: clusterRef: mysql-cluster type: Restart restart: componentName: mysql EOF ``` Check the cluster status to validate the restarting. ```bash kbcli cluster list mysql-cluster > NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME mysql-cluster default apecloud-mysql ac-mysql-8.0.30 Delete Running Jan 29,2023 14:29 UTC+0800 ``` STATUS=Restarting: it means the cluster restart is in progress. STATUS=Running: it means the cluster has been restarted.
Project: ShardingSphere (App Definition and Development / Database)
File: ecosystem.en.md

+++ title = "How to build database ecosystem with newSQL in a big-data environment" weight = 6 chapter = true +++ With the rapid development of the Internet, the scale of Internet data is also explosive growth. In this scenario, how to transform and upgrade the traditional database to meet the data needs of the new Internet? How to build an ecosystem of distributed database cluster with the help of NewSQL concept to meet the business needs of query performance, large amount of data storage, data security, elastic expansion, etc? This sharing will analyze these problems in detail and provide a relatively complete NewSQL solution. {{< bilibili BV19z411e743 >}}
Project: ClickHouse (App Definition and Development / Database)
File: deltasumtimestamp.md

slug: /en/sql-reference/aggregate-functions/reference/deltasumtimestamp sidebar_position: 141 title: deltaSumTimestamp Adds the difference between consecutive rows. If the difference is negative, it is ignored. This function is primarily for that store data ordered by some time bucket-aligned timestamp, for example, a `toStartOfMinute` bucket. Because the rows in such a materialized view will all have the same timestamp, it is impossible for them to be merged in the correct order, without storing the original, unrounded timestamp value. The `deltaSumTimestamp` function keeps track of the original `timestamp` of the values it's seen, so the values (states) of the function are correctly computed during merging of parts. To calculate the delta sum across an ordered collection you can simply use the function. Syntax ``` sql deltaSumTimestamp(value, timestamp) ``` Arguments `value` Input values, must be some type or type or a or . `timestamp` The parameter for order values, must be some type or type or a or . Returned value Accumulated differences between consecutive values, ordered by the `timestamp` parameter. Type: or or or . Example Query: ```sql SELECT deltaSumTimestamp(value, timestamp) FROM (SELECT number AS timestamp, AS value FROM numbers(1, 10)); ``` Result: ``` text deltaSumTimestamp(value, timestamp) 13 ```
Project: Kubescape (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: 'bug' assignees: '' <!-- A clear and concise description of what the bug is. --> OS: ` ` <!-- the OS + version youre running Kubescape on, e.g Ubuntu 22.04 LTS --> Version: ` ` <!-- the version that Kubescape reports when you run `kubescape version` --> <!-- Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error --> <!-- A clear and concise description of what you expected to happen. --> <!-- A clear and concise description of what happened. If applicable, add screenshots to help explain your problem. --> <!-- Add any other context about the problem here. -->
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_use_profile.md

title: "Command - devspace use profile" sidebar_label: devspace use profile Use a specific DevSpace profile ``` devspace use profile [flags] ``` ``` Use a specific DevSpace profile Example: devspace use profile production devspace use profile staging devspace use profile --reset ``` ``` -h, --help help for profile --reset Don't use a profile anymore ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```