cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-show-partitions.md

layout: global title: SHOW PARTITIONS displayTitle: SHOW PARTITIONS license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. The `SHOW PARTITIONS` statement is used to list partitions of a table. An optional partition spec may be specified to return the partitions matching the supplied partition spec. ```sql SHOW PARTITIONS tableidentifier [ partitionspec ] ``` table_identifier* Specifies a table name, which may be optionally qualified with a database name. Syntax: `[ databasename. ] tablename` partition_spec* An optional parameter that specifies a comma separated list of key and value pairs for partitions. When specified, the partitions that match the partition specification are returned. Syntax: `PARTITION ( partitioncolname = partitioncolval [ , ... ] )` ```sql -- create a partitioned table and insert a few rows. USE salesdb; CREATE TABLE customer(id INT, name STRING) PARTITIONED BY (state STRING, city STRING); INSERT INTO customer PARTITION (state = 'CA', city = 'Fremont') VALUES (100, 'John'); INSERT INTO customer PARTITION (state = 'CA', city = 'San Jose') VALUES (200, 'Marry'); INSERT INTO customer PARTITION (state = 'AZ', city = 'Peoria') VALUES (300, 'Daniel'); -- Lists all partitions for table `customer` SHOW PARTITIONS customer; +-+ | partition| +-+ | state=AZ/city=Peoria| | state=CA/city=Fremont| |state=CA/city=San Jose| +-+ -- Lists all partitions for the qualified table `customer` SHOW PARTITIONS salesdb.customer; +-+ | partition| +-+ | state=AZ/city=Peoria| | state=CA/city=Fremont| |state=CA/city=San Jose| +-+ -- Specify a full partition spec to list specific partition SHOW PARTITIONS customer PARTITION (state = 'CA', city = 'Fremont'); ++ | partition| ++ |state=CA/city=Fremont| ++ -- Specify a partial partition spec to list the specific partitions SHOW PARTITIONS customer PARTITION (state = 'CA'); +-+ | partition| +-+ | state=CA/city=Fremont| |state=CA/city=San Jose| +-+ -- Specify a partial spec to list specific partition SHOW PARTITIONS customer PARTITION (city = 'San Jose'); +-+ | partition| +-+ |state=CA/city=San Jose| +-+ ```
Project: Trivy (Provisioning / Security & Compliance)
File: cks.md

The is offered by The Linux Foundation. It provides assurance that a CKS has the skills, knowledge, and competence on a broad range of best practices for securing container-based applications and Kubernetes platforms during build, deployment and runtime. CKA certification is required to sit for this exam. Supply chain security best Supply chain If you know of interesting resources, please start a PR to add those to the list.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_kubeblocks_compare.md

title: kbcli kubeblocks compare List the changes between two different version KubeBlocks. ``` kbcli kubeblocks compare version [OTHER-VERSION] [flags] ``` ``` kbcli kubeblocks compare 0.4.0 kbcli kubeblocks compare 0.4.0 0.5.0 ``` ``` --details show the different details between two kubeblocks version -h, --help help for compare ``` ``` --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: ArangoDB (App Definition and Development / Database)
File: implicit_failure_exception_move_constructor.md

+++ title = "`basicoutcome(failuretype<EP> &&)`" description = "Implicit exception-from-failure-type-sugar move constructor. Available if `predicate::enablecompatibleconversion<void, void, EP, void>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "tagged-constructors"] weight = 535 +++ Implicit exception-from-failure-type-sugar move constructor used to disambiguate the construction of the exception type. Calls {{% api "void onoutcomemoveconstruction(T *, U &&) noexcept" %}} with `this` and `failuretype<EP> &&`. Requires: `predicate::enablecompatibleconversion<void, void, EP, void>` is true. Complexity: Same as for the `exception_type` constructor which accepts `EP`. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: Metal³ (Provisioning / Automation & Configuration)
File: ironic-authentication.md

Because hosts under the control of Metal need to contact the Ironic API during inspection and provisioning, it is highly advisable to require authentication on this API, since the provisioned hosts running user workloads will remain connected to the provisioning network. The `baremetal-operator` supports connecting to Ironic configured with the following `auth_strategy` modes: `noauth` (no authentication) `http_basic` (HTTP ) Note that Keystone authentication methods are not yet supported. Authentication configuration is read from the filesystem, beginning at the root directory specified in the environment variable `METAL3AUTHROOT_DIR`. If this variable is empty or not specified, the default is `/opt/metal3/auth`. Within the root directory there is a separate subdirectory `ironic` for Ironic client configuration. This is the default, and will be chosen if the auth root directory does not exist. In this mode, the baremetal-operator does not attempt to do any authentication against the Ironic APIs. This mode is configured by files in each authentication subdirectory named `username` and `password`, and containing the Basic auth username and password, respectively.
Project: Confidential Containers (Provisioning / Security & Compliance)
File: README.md

To demonstrate confidential containers capabilities, we run a pod with SSH public key authentication. Compared to the execution of and login to a shell on a pod, an SSH connection is cryptographically secured and requires a private key. It cannot be established by unauthorized parties, such as someone who controls the node. The container image contains the SSH host key that can be used for impersonating the host we will connect to. Because this container image is encrypted, and the key to decrypting this image is only provided in measurable ways (e.g. attestation or encrypted initrd), and because the pod/guest memory is protected, even someone who controls the node cannot steal this key. If you would rather build the image with your own keys, skip to . The can be used to set up a compatible runtime. A demo image is provided at . It is encrypted with 's and as its key file. The private key for establishing an SSH connection to this container is given in . To use it with SSH, its permissions should be adjusted: `chmod 600 ccv0-ssh`. The host key fingerprint is `SHA256:wK7uOpqpYQczcgV00fGCh+X97sJL3f6G1Ku4rvlwtR0`. All keys shown here are for demonstration purposes. To achieve actually confidential containers, use a hardware trusted execution environment and do not reuse these keys. Continue at . The image built should be encrypted. To receive a decryption key at run time, the Confidential Containers project utilizes the . ```sh $ ssh-keygen -t ed25519 -f ccv0-ssh -P "" -C "" ``` generates an SSH key `ccv0-ssh` and the correspondent public key `ccv0-ssh.pub`. The provided expects `ccv0-sh.pub` to exist. Using Docker, you can build with ```sh $ docker build -t ccv0-ssh . ``` Alternatively, Buildah can be used (`buildah build` or formerly `buildah bud`). The SSH host key fingerprint is displayed during the build. A specifying the runtime is included. If you use a , you should replace the image specification with the image you built. The default tag points to an `amd64` image, an `s390x` tag is also available. With common CNI setups, on the same host, with the service running, you can connect via SSH with ```sh $ ssh -i ccv0-ssh root@$(kubectl get service ccv0-ssh -o jsonpath="{.spec.clusterIP}") ``` You will be prompted about whether the host key fingerprint is correct. This fingerprint should match the one specified above/displayed in the Docker build. `crictl`-compatible and configurations are also included, which forward the pod SSH port (22) to 2222 on the host (use the `-p` flag in SSH).
Project: StarRocks (App Definition and Development / Database)
File: unix_timestamp.md

displayed_sidebar: "English" Converts a DATE or DATETIME value into a UNIX timestamp. If no parameter is specified, this function converts the current time into a UNIX timestamp. The `date` parameter must be of the DATE or DATETIME type. For time before 1970-01-01 00:00:00 or after 2038-01-19 11:14:07, this function returns 0. For more information about the date format, see . This function may return different results for different time zones. For more information, see . ```Haskell BIGINT UNIX_TIMESTAMP() BIGINT UNIX_TIMESTAMP(DATETIME date) BIGINT UNIX_TIMESTAMP(DATETIME date, STRING fmt) ``` ```Plain Text MySQL > select unix_timestamp(); ++ | unix_timestamp() | ++ | 1558589570 | ++ MySQL > select unix_timestamp('2007-11-30 10:30:19'); ++ | unix_timestamp('2007-11-30 10:30:19') | ++ | 1196389819 | ++ MySQL > select unix_timestamp('2007-11-30 10:30-19', '%Y-%m-%d %H:%i-%s'); ++ | unix_timestamp('2007-11-30 10:30-19') | ++ | 1196389819 | ++ MySQL > select unix_timestamp('2007-11-30 10:30%3A19', '%Y-%m-%d %H:%i%%3A%s'); ++ |unix_timestamp('2007-11-30 10:30%3A19')| ++ | 1196389819 | ++ MySQL > select unix_timestamp('1969-01-01 00:00:00'); ++ | unix_timestamp('1969-01-01 00:00:00') | ++ | 0 | ++ ``` UNIX_TIMESTAMP,UNIX,TIMESTAMP
Project: KICS (Provisioning / Security & Compliance)
File: 953b3cdb-ce13-428a-aa12-318726506661.md

title: IAM Policies With Full Privileges hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 953b3cdb-ce13-428a-aa12-318726506661 Query name: IAM Policies With Full Privileges Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: IAM policies shouldn't allow full administrative privileges (for all resources)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8 21" AWSTemplateFormatVersion: "2010-09-09" Description: A sample template Resources: mypolicy: Type: AWS::IAM::Policy Properties: PolicyName: mygrouppolicy PolicyDocument: Version: '2012-10-17' Statement: Effect: Allow Action: ["*"] Resource: "*" Groups: myexistinggroup1 !Ref mygroup mypolicy2: Type: AWS::IAM::Policy Properties: PolicyName: mygrouppolicy PolicyDocument: Version: '2012-10-17' Statement: Effect: Allow Action: "*" Resource: "*" Groups: myexistinggroup1 !Ref mygroup ``` ```json title="Positive test num. 2 - json file" hl_lines="9 31" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "A sample template", "Resources": { "mypolicy": { "Type": "AWS::IAM::Policy", "Properties": { "PolicyName": "mygrouppolicy", "PolicyDocument": { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "*" ], "Resource": "*" } ] }, "Groups": [ "myexistinggroup1", "mygroup" ] } }, "mypolicy2": { "Type": "AWS::IAM::Policy", "Properties": { "PolicyName": "mygrouppolicy", "PolicyDocument": { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "*", "Resource": "*" } ] }, "Groups": [ "myexistinggroup1", "mygroup" ] } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Description: A sample template Resources: MyPolicy: Type: AWS::IAM::Policy Properties: PolicyName: mygrouppolicy PolicyDocument: Version: "2012-10-17" Statement: Effect: Allow Action: s3:GetObject s3:PutObject s3:PutObjectAcl Resource: arn:aws:s3:::myAWSBucket/* Groups: myexistinggroup1 !Ref mygroup ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "A sample template", "Resources": { "MyPolicy": { "Properties": { "PolicyName": "mygrouppolicy", "PolicyDocument": { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:GetObject", "s3:PutObject", "s3:PutObjectAcl" ], "Resource": "arn:aws:s3:::myAWSBucket/*" } ] }, "Groups": [ "myexistinggroup1", "mygroup" ] }, "Type": "AWS::IAM::Policy" } } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.51.md

layout: release date: 2021-08-29 tag: v0.5.51 [UI]fixed the overflowing RJSF form @warunicorn19 (#4030) [UI] Ability to maximize the Application and Pattern Editor @Abhishek-kumar09 (#4027) Limited Calls to ValidateVersion @Revolyssup (#4031) [UI] add default podname mapper @bariqhibat (#4029) [UI] Fixed Overlay cards in Meshery Performance @mani9896 (#3979) [UI] dashboard bug - check types for meshScan @bariqhibat (#4026) [CI] prevent upload to codecov on forks @iamsdas (#4008) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @DelusionalOptimist, @Revolyssup, @bariqhibat, @iamsdas, @leecalcote, @mani9896, @sudo-NithishKarthik and @warunicorn19
Project: SuperEdge (Provisioning / Automation & Configuration)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thanks for sending a pull request! If this is your first time, please read our contributor guidelines: https://github.com/superedge/superedge/blob/master/CONTRIBUTING.md --> What type of PR is this? What this PR does: Which issue(s) this PR fixes: Fixes # Special notes for your reviewer:
Project: in-toto (Provisioning / Security & Compliance)
File: PULL_REQUEST_TEMPLATE.md

Please fill in the fields below to submit a pull request. The more information that is provided, the better. Fixes issue #: Description of the changes being introduced by the pull request: Please verify and check that the pull request fulfills the following requirements: [ ] Tests have been added for the bug fix or new feature [ ] Docs have been added for the bug fix or new feature
Project: StarRocks (App Definition and Development / Database)
File: ADMIN_SET_PARTITION_VERSION.md

displayed_sidebar: "English" Sets a partition to a specific data version. Note that manually setting the partition version is a high-risk operation and is recommended only when problems occur in the cluster metadata. In normal circumstances, the version of a partition is consistent with that of the tablets within. :::tip This operation requires the SYSTEM-level OPERATE privilege. You can follow the instructions in to grant this privilege. ::: ```sql ADMIN SET TABLE <tablename> PARTITION ( <partitionname> | <partition_id> ) TO VERSION <version> ``` `table_name`: The name of the table to which the partition belongs. `partitionname`: The name of the partition. You need to specify a partition using either `partitionname` or `partitionid`. For non-partitioned tables, `partitionname` is the same as the table name. `partitionid`: The ID of the partition. You need to specify a partition using either `partitionname` or `partitionid`. For tables with the random bucketing strategy, you can only use `partitionid` to specify the partition. `version`: The version you want to set for the partition. Set the version of the non-partitioned table `t1` to `10`. ```sql ADMIN SET TABLE t1 PARTITION(t1) TO VERSION 10; ``` Set the version of partition `p1` in table `t2` to `10`. ```sql ADMIN SET TABLE t2 PARTITION(p1) TO VERSION 10; ``` Set the version of the partition whose ID is `123456` to `10`. `t3` is a table with the random bucketing strategy. ```sql ADMIN SET TABLE t3 PARTITION('123456') TO VERSION 10; ```
Project: ClickHouse (App Definition and Development / Database)
File: tinylog.md

slug: /en/engines/table-engines/log-family/tinylog toc_priority: 34 toc_title: TinyLog The engine belongs to the log engine family. See for common properties of log engines and their differences. This table engine is typically used with the write-once method: write data one time, then read it as many times as necessary. For example, you can use `TinyLog`-type tables for intermediary data that is processed in small batches. Note that storing data in a large number of small tables is inefficient. Queries are executed in a single stream. In other words, this engine is intended for relatively small tables (up to about 1,000,000 rows). It makes sense to use this table engine if you have many small tables, since its simpler than the engine (fewer files need to be opened).
Project: KICS (Provisioning / Security & Compliance)
File: afcb0771-4f94-44ed-ad4a-9f73f11ce6e0.md

title: Nifcloud ELB Listener Use HTTP Protocol hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: afcb0771-4f94-44ed-ad4a-9f73f11ce6e0 Query name: Nifcloud ELB Listener Use HTTP Protocol Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: The elb listener use http protocol<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifcloudelblistener" "positive" { elbid = nifcloudelb.positive.id instance_port = 80 protocol = "HTTP" lb_port = 80 } resource "nifcloud_elb" "positive" { availability_zone = "east-11" instance_port = 8080 protocol = "HTTP" lb_port = 8080 network_interface { networkid = "net-COMMONGLOBAL" isvipnetwork = true } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "nifcloudelblistener" "positive" { elbid = nifcloudelb.positive.id instance_port = 80 protocol = "HTTP" lb_port = 80 } resource "nifcloud_elb" "positive" { availability_zone = "east-11" instance_port = 8080 protocol = "HTTP" lb_port = 8080 network_interface { networkid = "net-COMMONGLOBAL" isvipnetwork = true } network_interface { networkid = "net-COMMONPRIVATE" } } ``` ```tf title="Negative test num. 1 - tf file" resource "nifcloudelblistener" "negative" { elbid = nifcloudelb.negative.id instance_port = 1443 protocol = "HTTPS" lb_port = 1443 } resource "nifcloud_elb" "negative" { availability_zone = "east-11" instance_port = 443 protocol = "HTTPS" lb_port = 443 network_interface { networkid = "net-COMMONGLOBAL" isvipnetwork = true } } ```
Project: SPIFFE (Provisioning / Key Management)
File: ANDREW_MOORE.md

I am grateful for the confidence given to have me on the SSC today, and hope I can continue to serve on the committee. Since February 2019 I have been leading SPIRE adoption and integrations at Uber across a hetereogeneous set of architectures, platforms, and cloud providers through every slice of our tech stack and devops. My experience with SPIRE is at large scale for both admin operations and workload interactions. While since last election I've been bumped down from the Number 3 contributor on SPIRE to Number 6, I actively push and drive for my own organization's resources to make their own contributions into the product, be it small observability changes or large feature sets such as LRU Cache. I have owned and driven multiple SPIFFE migrations across my organization, and will be continuing to do so for a long time to come. In the SPIFFE community, I can be seen giving user help, engaging with the `helm-charts` project, and working with the rest of SSC to discover and define what the optimal shape and processes of the committee itself are to best serve the community. GitHub Handle: @amoore877 Email Address: amoore877@gmail.com LinkedIn Profile: https://www.linkedin.com/in/andrew-moore-681b1114a Current Affiliation: Uber