cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.1.0.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Improve handling of fetch failures when a tasktracker is not responding on HTTP* The TaskTracker now has a thread which monitors for a known Jetty bug in which the selector thread starts spinning and map output can no longer be served. If the bug is detected, the TaskTracker will shut itself down. This feature can be disabled by setting mapred.tasktracker.jetty.cpu.check.enabled to false. | Minor | move up to Jackson 1.8.8* WARNING: No release note provided for this change. | Blocker | Binary tarball does not preserve platform info for native builds, and RPMs fail to provide needed symlinks for libhadoop.so* This fix is marked "incompatible" only because it changes the bin-tarball directory structure to be consistent with the source tarball directory structure. The source tarball is unchanged. RPMs and DEBs now use an intermediate bin-tarball with an "${os.arch}" tag (like the packages themselves). The un-tagged bin-tarball is now multi-platform and retains the structure of the source tarball; it is in fact generated by target "tar", not by target "binary". Finally, in the 64-bit RPMs and DEBs, the native libs go in the "lib64" directory instead of "lib". | Critical | Create hadoop-client and hadoop-minicluster artifacts for downstream projects* Generate integration artifacts "org.apache.hadoop:hadoop-client" and "org.apache.hadoop:hadoop-minicluster" containing all the jars needed to use Hadoop client APIs, and to run Hadoop MiniClusters, respectively. Push these artifacts to the maven repository when mvn-deploy, along with existing artifacts.
Project: YDB (App Definition and Development / Database)
File: select_specific_columns.md

Select the data from the columns `seriesid`, `releasedate`, and `title`. At the same time, rename `title` to `seriestitle` and cast the type of `releasedate` from `Uint32` to `Date`. {% include %} ```sql SELECT seriesid, -- The names of columns (seriesid, release_date, title) -- are separated by commas. title AS series_title, -- You can use AS to rename columns -- or give a name to an arbitrary expression CAST(releasedate AS Date) AS releasedate FROM series; COMMIT; ```
Project: ClickHouse (App Definition and Development / Database)
File: v20.10.7.4-stable.md

Backported in : - Fix optimizedistributedgroupbysharding_key for query with OFFSET only. (). Backported in : Fix empty `system.stack_trace` table when server is running in daemon mode. (). Backported in : Fix possible segfault in `topK` aggregate function. This closes . (). Backported in : fixes fixes support convert MySQL prefix index for MaterializeMySQL CC: @tavplubix. (). Backported in : Fixed `std::outofrange: basic_string` in S3 URL parsing. (). Backported in : Fix `Unknown setting profile` error on attempt to set settings profile. (). Backported in : fixes fixes fix unique key convert crash in MaterializeMySQL database engine. (). Backported in : Fix key comparison between Enum and Int types. This fixes . (). Backported in : - Fixed issue when `clickhouse-odbc-bridge` process is unreachable by server on machines with dual IPv4/IPv6 stack; - Fixed issue when ODBC dictionary updates are performed using malformed queries and/or cause crashes; Possibly closes . ().
Project: Meshery (Provisioning / Automation & Configuration)
File: grafana-ui-server.md

layout: integration title: Grafana UI Server subtitle: Operational dashboards for your data with Grafana and Meshery image: /assets/img/integrations/grafana-ui-server/icons/color/grafana-ui-server-color.svg permalink: extensibility/integrations/grafana-ui-server docURL: https://docs.meshery.io/extensibility/integrations/grafana-ui-server description: integrations-category: Observability and Analysis integrations-subcategory: Monitoring registrant: Artifact Hub components: name: grafana-dashboard colorIcon: assets/img/integrations/grafana-ui-server/components/grafana-dashboard/icons/color/grafana-dashboard-color.svg whiteIcon: assets/img/integrations/grafana-ui-server/components/grafana-dashboard/icons/white/grafana-dashboard-white.svg description: featureList: [ "Centralize the analysis, visualization, and alerting for all of your data with Grafana.", "Meshery discovers your Grafana servers. Easily import existing Grafana dashboards and panels into Meshery", "Integrate your boards and panels and new insights and metrics" ] 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: Teleport (Provisioning / Security & Compliance)
File: preflight.md

This checklist is to be run prior to cutting the release branch. [ ] Bump Web UI dependencies [ ] Make a new docs/VERSION folder [ ] Update VERSION in Makefile to next dev tag [ ] Update TELEPORT_VERSION in assets/aws/Makefile [ ] Update `base-ref` to point to the new release branch in `.github/workflows/dependency-review.yaml` [ ] Update mentions of the version in examples/ and README.md [ ] Search code for DELETE IN and REMOVE IN comments and clean up if appropriate [ ] Update docs/faq.mdx "Which version of Teleport is supported?" section with release date and support info [ ] Update the CI buildbox image [ ] Update the `BUILDBOX_VERSION` in `build.assets/images.mk`. Commit and merge. [ ] Update `e/.github/workflows/build-buildboxes-cron.yaml` to uncomment final pre-release job and ensure it has the correct branch names (two places). Commit and merge.
Project: Druid (App Definition and Development / Database)
File: avro.md

id: avro title: "Apache Avro" <!-- ~ 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. --> This Apache Druid extension enables Druid to ingest and parse the Apache Avro data format as follows: for Kafka and Kinesis. for native batch ingestion. . The is deprecated. To use the Avro extension, add the `druid-avro-extensions` to the list of loaded extensions. See for more information. Druid supports most Avro types natively. This section describes some exceptions. Druid has two modes for supporting `union` types. The default mode treats unions as a single value regardless of the type of data populating the union. If you want to operate on individual members of a union, set `extractUnionsByType` on the Avro parser. This configuration expands union values into nested objects according to the following rules: Primitive types and unnamed complex types are keyed by their type name, such as `int` and `string`. Complex named types are keyed by their names, this includes `record`, `fixed`, and `enum`. The Avro null type is elided as its value can only ever be null. This is safe because an Avro union can only contain a single member of each unnamed type and duplicates of the same named type are not allowed. For example, only a single array is allowed, multiple records (or other named types) are allowed as long as each has a unique name. You can then access the members of the union with a like you would for other nested types. The extension returns `bytes` and `fixed` Avro types as base64 encoded strings by default. To decode these types as UTF-8 strings, enable the `binaryAsString` option on the Avro parser. The extension returns `enum` types as `string` of the enum symbol. You can ingest `record` and `map` types representing nested data with a on the parser. Druid does not currently support Avro logical types. It ignores them and handles fields according to the underlying primitive type.
Project: KICS (Provisioning / Security & Compliance)
File: d5ec2080-340a-4259-b885-f833c4ea6a31.md

title: Certificate RSA Key Bytes Lower Than 256 hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d5ec2080-340a-4259-b885-f833c4ea6a31 Query name: Certificate RSA Key Bytes Lower Than 256 Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: The certificate should use a RSA key with a length equal to or higher than 256 bytes<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3" name: upload a self-signed certificate community.aws.aws_acm: certificate: "{{ lookup('file', 'rsa1024.pem' ) }}" privateKey: "{{ lookup('file', 'key.pem' ) }}" nametag: mycert region: ap-southeast-2 ``` ```yaml title="Negative test num. 1 - yaml file" name: upload a self-signed certificate2 community.aws.aws_acm: certificate: "{{ lookup('file', 'rsa4096.pem' ) }}" privateKey: "{{ lookup('file', 'key.pem' ) }}" nametag: mycert region: ap-southeast-2 ```
Project: ArangoDB (App Definition and Development / Database)
File: co_tryv_failure_likely.md

+++ title = "`BOOSTOUTCOMECOTRYVFAILURELIKELY(expr)/BOOSTOUTCOMECOTRYFAILURELIKELY(expr)`" description = "Evaluate from within a coroutine an expression which results in an understood type, continuing execution if successful, immediately returning `tryoperationreturn_as(X)` from the calling function if unsuccessful." +++ Evaluate from within a coroutine an expression which results in a type matching the following customisation points, continuing execution if successful, immediately returning {{% api "tryoperationreturn_as(X)" %}} from the calling function if unsuccessful: `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationhasvalue(X)" %}} `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationreturnas(X)" %}} `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationextractvalue(X)" %}} Default overloads for these customisation points are provided. See . The difference between the `BOOSTOUTCOMECOTRYV(expr)` and `BOOSTOUTCOMECOTRY(expr)` editions is that the latter will set a variable if two or more macro arguments are present (see {{% api "BOOSTOUTCOMECO_TRY(var, expr)" %}}). The former requires the `T` to be `void`. Hints are given to the compiler that the expression will be unsuccessful. If you expect success, you should use {{% api "BOOSTOUTCOMECO_TRYV(expr)" %}} instead. An internal temporary to hold the value of the expression is created, which generally invokes a copy/move. Overridable: Not overridable. Definition: Firstly the expression's temporary is bound to a uniquely named, stack allocated, `auto &&`. If that reference's bound object's `tryoperationhasvalue()` is false, immediately execute `return tryoperationreturnas(propagated unique reference);`, propagating the rvalue/lvalue/etc-ness of the original expression. Header: `<boost/outcome/try.hpp>`
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.34.md

layout: release date: 2021-07-10 tag: v0.5.34 Reverted backup for empty meshconfig @metonymic-smokey (#3439) [mesheryctl] Fix for system login @piyushsingariya (#3433) Open API Docs #5 @piyushsingariya (#3368) Thank you to our contributors for making this release possible: @metonymic-smokey, @navendu-pottekkat, @piyushsingariya, @ramrodo and @utkarsh-pro
Project: YugabyteDB (App Definition and Development / Database)
File: yba_yb-db-version.md

Manage YugabyteDB version release Manage YugabyteDB version release ``` yba yb-db-version [flags] ``` ``` -h, --help help for yb-db-version ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - yba - Command line tools to manage your YugabyteDB Anywhere (Self-managed Database-as-a-Service) resources. - List YugabyteDB version releases
Project: StarRocks (App Definition and Development / Database)
File: user_defined_variables.md

displayed_sidebar: "English" This topic describes how to declare and use user-defined variables. StarRocks 2.5 and later versions support user-defined variables. These variables are used to store specific values that are referenced in later SQL statements, thereby simplifying the writing of SQL statements and avoiding duplicate computation. User-defined variables are variables, which can be created by the user and exist in the session. This means that no one can access user-defined variables that have been declared by another user, and when the session is closed these variables expire. StarRocks does not support using the SHOW statement to display existing user-defined variables. The following types of values cannot be declared as user-defined variables: BITMAP, HLL, PERCENTILE, and ARRAY. User-defined variables of the JSON type are converted to the STRING type for storage. ```Plain SET @var_name = expr [, ...]; ``` NOTE All variables must be preceded by a single at sign (@). Multiple variables can be declared in the same SET statement and need to be separated with commas (`,`). You can declare the same variable multiple times. The newly declared value overwrites the original value. If an undeclared variable is used, the value of the variable is `NULL` by default, and the NULL type is STRING. | Parameter | Required | Description | | - | | | | varname | Yes | The name of the user-defined variable. The naming conventions are as follows:<ul><li>The name can contain letters, digits (0-9), and underscores (\). </li><li>The name cannot exceed 64 characters in length.</li></ul>You can declare a string as a user-defined variable, such as @'my-var', @"my-var", and @\`my-var\`. User-defined variables of the STRING type can contain characters other than letters, digits, and underscores (_), such as periods (.). | | expr | Yes | The value of the user-defined variable. You can specify a number (such as 43) or a complex expression (such as the value returned by a SELECT statement) for this parameter. The data type of the variable is the same as the data type of the result returned by the expression. | Example 1: Declare a number as a user-defined variable. ```SQL SET @var = 43; ``` Example 2: Declare the value returned by a SELECT query as a user-defined variable. ```SQL SET @var = (SELECT SUM(v1) FROM test); ``` Example 3: Declare multiple user-defined variables in the same SET statement. ```SQL SET @v1=1, @v2=2; ``` Simplifies the writing of SQL statements. For example, when you execute the following SELECT statement, StarRocks parses `@var` as `1`. ```Plain SET @var = 1; SELECT @var, v1 from test; ``` Avoids duplicate computation. For example, when you execute the following SELECT statement, StarRocks parses `@var` as the result returned by the `select sum(c1) from tbl` command. ```Plain SET @var = (select sum(c1) from tbl); SELECT @var, v1 from test; ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: zillow.md

title: "Zillow" icon: /images/logos/powered-by/zillow.png hasNav: true hasLink: "https://www.zillow.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. -->
Project: KICS (Provisioning / Security & Compliance)
File: 94fbe150-27e3-4eba-9ca6-af32865e4503.md

title: User With Privilege Escalation By Actions 'glue:CreateDevEndpoint' And 'iam:PassRole' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 94fbe150-27e3-4eba-9ca6-af32865e4503 Query name: User With Privilege Escalation By Actions 'glue:CreateDevEndpoint' And 'iam:PassRole' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: User with privilege escalation by actions 'glue:CreateDevEndpoint' and 'iam:PassRole' 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 = [ "glue:CreateDevEndpoint", ] Effect = "Allow" Resource = "*" }, ] }) } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" users = [awsiamuser.cosmic.name] roles = [awsiamrole.role.name] groups = [awsiamgroup.group.name] policyarn = awsiam_policy.policy.arn } resource "awsiampolicy" "policy" { name = "test-policy" description = "A test policy" policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:PassRole", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```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: StarRocks (App Definition and Development / Database)
File: days_sub.md

displayed_sidebar: "English" Subtracts specified days from a date or datetime to get a new datetime. ```Haskell DATETIME days_sub(DATETIME|DATE d, INT n); ``` `d`: the date or datetime expression. `n`: the number of days to subtract from the `d`. Returns a value of the datetime type, NULL is returned if any parameter is NULL or invalid. NULL is returned if the result exceeds the range [0000-01-01 00:00:00, 9999-12-31 00:00:00]. ```Plain Text SELECT DAYS_SUB('2022-12-20 12:00:00', 10); +--+ | days_sub('2022-12-20 12:00:00', INTERVAL 10 DAY) | +--+ | 2022-12-10 12:00:00 | +--+ SELECT DAYS_SUB('2022-12-20 12:00:00', -10); ++ | days_sub('2022-12-20 12:00:00', INTERVAL -10 DAY) | ++ | 2022-12-30 12:00:00 | ++ SELECT DAYS_SUB('2022-12-20 12:00:00', 738874); ++ | days_sub('2022-12-20 12:00:00', INTERVAL 738874 DAY) | ++ | 0000-01-01 12:00:00 | ++ SELECT DAYS_SUB('2022-12-20 12:00:00', 738875); ++ | days_sub('2022-12-20 12:00:00', INTERVAL 738875 DAY) | ++ | NULL | ++ SELECT DAYS_SUB('2022-12-20 12:00:00', -2913550); +--+ | days_sub('2022-12-20 12:00:00', INTERVAL -2913550 DAY) | +--+ | 9999-12-31 12:00:00 | +--+ SELECT DAYS_SUB('2022-12-20 12:00:00', -2913551); +--+ | days_sub('2022-12-20 12:00:00', INTERVAL -2913551 DAY) | +--+ | NULL | +--+ ``` DAY,day
Project: StarRocks (App Definition and Development / Database)
File: keywords.md

displayed_sidebar: "English" This topic describes non-reserved keywords and reserved keywords. It provides a list of reserved keywords in StarRocks. Keywords in SQL statements, such as `CREATE` and `DROP`, have special meanings when parsed by StarRocks. Keywords are classified into non-reserved keywords and reserved keywords. Non-reserved keywords can be directly used as identifiers without special treatment, such as table names and column names. For example, `DB` is a non-reserved keyword. You can create a database named `DB`. ```SQL CREATE DATABASE DB; Query OK, 0 rows affected (0.00 sec) ``` Reserved keywords can be used as identifiers only after special treatment. For example, `LIKE` is a reserved keyword. If you want to use it to identify a database, enclose it in a pair of backticks (`). ```SQL CREATE DATABASE `LIKE`; Query OK, 0 rows affected (0.01 sec) ``` If it is not enclosed in backticks, an error is returned: ```SQL CREATE DATABASE LIKE; ERROR 1064 (HY000): Getting syntax error at line 1, column 16. Detail message: Unexpected input 'like', the most similar input is {a legal identifier}. ``` Following are StarRocks reserved keywords arranged in alphabetical order. You must enclose them in a pair of backticks (`) if you want to use them as identifiers. The reserved keywords may vary with StarRocks versions. ADD ALL ALTER ANALYZE AND ARRAY AS ASC BETWEEN BIGINT BITMAP BOTH BY CASE CHAR CHARACTER CHECK COLLATE COLUMN COMPACTION (v3.1 and later) CONVERT CREATE CROSS CUBE CURRENT_DATE CURRENT_TIME CURRENT_TIMESTAMP CURRENT_USER CURRENT_ROLE (v3.0 and later) DATABASE DATABASES DECIMAL DECIMALV2 DECIMAL32 DECIMAL64 DECIMAL128 DEFAULT DELETE DENSE_RANK DESC DESCRIBE DISTINCT DOUBLE DROP DUAL DEFERRED (v3.0 and later) ELSE EXCEPT EXISTS EXPLAIN FALSE FIRST_VALUE FLOAT FOR FORCE FROM FULL FUNCTION GRANT GROUP GROUPS GROUPING GROUPING_ID HAVING HLL HOST IF IGNORE IN INDEX INFILE INNER INSERT INT INTEGER INTERSECT INTO IS IMMEDIATE (v3.0 and later) JOIN JSON KEY KEYS KILL LAG LARGEINT LAST_VALUE LATERAL LEAD LEFT LIKE LIMIT LOAD LOCALTIME LOCALTIMESTAMP MAXVALUE MINUS MOD NTILE NOT NULL ON OR ORDER OUTER OUTFILE OVER PARTITION PERCENTILE PRIMARY PROCEDURE QUALIFY RANGE RANK READ REGEXP RELEASE RENAME REPLACE REVOKE RIGHT RLIKE ROW ROWS ROW_NUMBER SCHEMA SCHEMAS SELECT SET SET_VAR SHOW SMALLINT SYSTEM TABLE TERMINATED TEXT (v3.1 and later) THEN TINYINT TO TRUE UNION UNIQUE UNSIGNED UPDATE USE USING VALUES VARCHAR WHEN WHERE WITH
Project: KICS (Provisioning / Security & Compliance)
File: 4e1cc5d3-2811-4fb2-861c-ee9b3cb7f90b.md

title: API Gateway Without Security Policy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4e1cc5d3-2811-4fb2-861c-ee9b3cb7f90b Query name: API Gateway Without Security Policy Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: API Gateway should have a Security Policy defined and use TLS 1.2.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsapigatewaydomainname" "example" { domain_name = "api.example.com" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="3" resource "awsapigatewaydomainname" "example2" { domain_name = "api.example.com" securitypolicy = "TLS1_0" } ``` ```tf title="Negative test num. 1 - tf file" resource "awsapigatewaydomainname" "example4" { domain_name = "api.example.com" securitypolicy = "TLS1_2" } ```