cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: into-outfile.md

slug: /en/sql-reference/statements/select/into-outfile sidebar_label: INTO OUTFILE `INTO OUTFILE` clause redirects the result of a `SELECT` query to a file on the client side. Compressed files are supported. Compression type is detected by the extension of the file name (mode `'auto'` is used by default). Or it can be explicitly specified in a `COMPRESSION` clause. The compression level for a certain compression type can be specified in a `LEVEL` clause. Syntax ```sql SELECT <exprlist> INTO OUTFILE filename [AND STDOUT] [APPEND | TRUNCATE] [COMPRESSION type [LEVEL level]] ``` `file_name` and `type` are string literals. Supported compression types are: `'none'`, `'gzip'`, `'deflate'`, `'br'`, `'xz'`, `'zstd'`, `'lz4'`, `'bz2'`. `level` is a numeric literal. Positive integers in following ranges are supported: `1-12` for `lz4` type, `1-22` for `zstd` type and `1-9` for other compression types. This functionality is available in the and . Thus a query sent via will fail. The query will fail if a file with the same file name already exists. The default is `TabSeparated` (like in the command-line client batch mode). Use clause to change it. If `AND STDOUT` is mentioned in the query then the output that is written to the file is also displayed on standard output. If used with compression, the plaintext is displayed on standard output. If `APPEND` is mentioned in the query then the output is appended to an existing file. If compression is used, append cannot be used. When writing to a file that already exists, `APPEND` or `TRUNCATE` must be used. Example Execute the following query using : ```bash clickhouse-client --query="SELECT 1,'ABC' INTO OUTFILE 'select.gz' FORMAT CSV;" zcat select.gz ``` Result: ```text 1,"ABC" ```
Project: Meshery (Provisioning / Automation & Configuration)
File: importing-application.md

layout: default title: Importing existing applications permalink: extensions/importing-an-application language: en abstract: Import your existing applications into Meshery. display-title: "false" list: include type: extensions category: meshmap Importing apps into Meshery Extension as Meshery Apps is a powerful feature that enables users to manage, operate, and observe their cloud native infrastructure more effectively. With this feature, users can easily import their app manifest and store it in the database. Step 1: Access the Extensions UI Note: You can import three types of application: Docker Compose, Helm Chart, Kubernetes Manifest. Step 2: Navigate to the Applications Tab and Select your Import Once you have accessed the Extension's UI, navigate to the Applications tab. In this tab you can see all your application with their "<b>Name</b>" and "<b>Date Modified</b>". From the top right of the table click on import application which opens import modal. <a href="{{ site.baseurl }}/assets/img/meshmap/application-tab.png"><img style="border-radius: 0.5%;" alt="Import-Application" style="width:800px;height:auto;" src="{{ site.baseurl }}/assets/img/meshmap/application-tab.png" /></a> Step 3: Import the Application You can import your application by select File Type from the options and clicking on the Browse button and selecting the file from your local machine or import in through URL Once you have selected the file, click on the Import button to import app into Meshery Extension. When you import a app into Extensions, it will create a Meshery App based on definition. This Meshery App will include all of the services, ports, and other parameters defined in the File. <a href="{{ site.baseurl }}/assets/img/meshmap/apps-modal.png"><img style="border-radius: 0.5%;" alt="Import-Application" style="width:800px;height:auto;" src="{{ site.baseurl }}/assets/img/meshmap/apps-modal.png" /></a> Once the Meshery Application has been created, you can use Meshery Extension to manage, operate and observe your cloud native infrastructure. You can also use Meshery Extension to deploy your Meshery Application to your infrastructure.
Project: FOSSA (Provisioning / Security & Compliance)
File: godep.md

Dep is an alternative toolchain for golang dependency management. Though go modules are the blessed form of dependency management, dep is exploring alternatives in the dependency management space, and hasn't been deprecated. `gopkglock`: Find all files named `Gopkg.lock` `gopkgtoml`: Find all files named `Gopkg.toml` We parse from Gopkg.lock. This is more comprehensive than GopkgToml, as it contains pinned versions of all of our direct and transitive dependencies. We also pick up on `source` locations from GopkgLock We parse from Gopkg.toml. `override`s are similar to .
Project: StarRocks (App Definition and Development / Database)
File: minutes_sub.md

displayed_sidebar: "English" Subtracts specified minutes from the date, accurate to the minute. ```Haskell DATETIME minutes_sub(DATETIME|DATE date, INT minutes); ``` `date`: the base date. It must be of the DATETIME or DATE type. `minutes`: the minutes to reduce. It must be of the INT type, it could be greater, equal or less than zero. Returns a DATETIME value. Returns NULL if either `date` or `minutes` is NULL. ```Plain Text select minutes_sub('2022-01-01 01:03:01', 2); ++ | minutes_sub('2022-01-01 01:03:01', 2) | ++ | 2022-01-01 01:01:01 | ++ select minutes_sub('2022-01-01 01:01:01', -1); +-+ | minutes_sub('2022-01-01 01:01:01', -1) | +-+ | 2022-01-01 01:02:01 | +-+ select minutes_sub('2022-01-01', 1); ++ | minutes_sub('2022-01-01', 1) | ++ | 2021-12-31 23:59:00 | ++ ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.31.0.md

title: v1.31.0 weight: 998969000 Update the `FROM` directive in the `Dockerfile` to have a version tag > `v1.30.0` Evaluate your dependency requirements. The change to Ansible 2.15.0 also included removal of some pre-installed Python modules. You may need to update your `Dockerfile` to `pip install` modules required by your operator. See for more details. In the `requirements.yml` file: Remove the `community.kubernetes` collection entry Update the version of the `operator_sdk.util` collection entry to `v0.5.0` In the `molecule/kind/molecule.yml` and `molecule/default/molecule.yml` files: Remove all instances of the `lint` field. For an example of the diff, see: https://github.com/operator-framework/operator-sdk/pull/6483/files#diff-f159b0d7ec17de90f5b5c297ce997254e6ea4001269167be25615c45c489539e See for more details. Update the `FROM` directive in the `Dockerfile` to use the base image `quay.io/operator-framework/ansible-operator:vX.Y.Z` where `vX.Y.Z` is > `v1.30.0` See for more details. The operator now requires the watch operation on secrets. When using a custom ServiceAccount for deployment, the following additional role is now required: ``` rules: apiGroups: "" resources: secrets verbs: watch ``` See for more details.
Project: ClickHouse (App Definition and Development / Database)
File: v23.4.5.22-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Split huge `RUN` in Dockerfile into smaller conditional. Install the necessary tools on demand in the same `RUN` layer, and remove them after that. Upgrade the OS only once at the beginning. Use a modern way to check the signed repository. Downgrade the base repo to ubuntu:20.04 to address the issues on older docker versions. Upgrade golang version to address golang vulnerabilities. (). Backported in : This a follow-up for , the cleanup was lost during refactoring. (). Fix broken index analysis when binary operator contains a null constant argument (). Fix reconnecting of HTTPS session when target host IP was changed (). Fix incorrect constant folding (). Fix type of LDAP server params hash in cache entry (). Fallback to parsing big integer from String instead of exception in Parquet format (). Do not apply projection if read-in-order was enabled. (). Fix fuzzer failure in ActionsDAG (). Increase max array size in group bitmap ().
Project: KICS (Provisioning / Security & Compliance)
File: 8a893e46-e267-485a-8690-51f39951de58.md

title: COS Node Image Not Used hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8a893e46-e267-485a-8690-51f39951de58 Query name: COS Node Image Not Used Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: The node image should be Container-Optimized OS(COS)<br> ```tf title="Positive test num. 1 - tf file" hl_lines="16" resource "googlecontainercluster" "positive1" { name = "my-gke-cluster" location = "us-central1" removedefaultnode_pool = true initialnodecount = 1 } resource "googlecontainernode_pool" "positive2" { project = "gcp_project" name = "primary-pool" region = "us-west1" cluster = googlecontainercluster.primary.name node_config { imagetype = "WINDOWSLTSC" } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecontainercluster" "negative1" { name = "my-gke-cluster" location = "us-central1" removedefaultnode_pool = true initialnodecount = 1 } resource "googlecontainernode_pool" "negative2" { project = "gcp_project" name = "primary-pool" region = "us-west1" cluster = googlecontainercluster.primary.name node_config { image_type = "COS" } } resource "googlecontainernode_pool" "negative3" { project = "gcp_project" name = "primary-pool2" region = "us-west1" cluster = googlecontainercluster.primary.name } resource "googlecontainernode_pool" "negative4" { project = "gcp_project" name = "primary-pool2" region = "us-west1" cluster = googlecontainercluster.primary.name node_config { imagetype = "COSCONTAINERD" } } ```
Project: ArangoDB (App Definition and Development / Database)
File: exception_lvalue.md

+++ title = "`exception_type &exception() &`" description = "Wide contract lvalue reference observer of the stored exception. Constexpr propagating." categories = ["observers"] weight = 785 +++ Wide contract lvalue reference observer of the stored exception. `NoValuePolicy::wideexceptioncheck()` is first invoked, then the reference to the exception is returned. As a valid default constructed exception is always present, no undefined behaviour occurs if `NoValuePolicy::wideexceptioncheck()` returns. Note that if `exception_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::wideexceptioncheck()`. Guarantees: None.
Project: Flink (App Definition and Development / Streaming & Messaging)
File: versions.md

title: Versions type: docs bookToc: false <!-- 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. --> An appendix of hosted documentation for all versions of Apache Flink. {{< all_versions >}}
Project: StarRocks (App Definition and Development / Database)
File: intersect_count.md

displayed_sidebar: "English" A function to find the intersection size (number of same elements) of two Bitmap values, without requiring the data distribution to be orthogonal. The first parameter is the Bitmap column, the second parameter is the dimension column used for filtering, and the third parameter is a variable-length parameter, meaning that different values of the filtering dimension column are taken. If there is no intersection, 0 is returned. ```Haskell BIGINT INTERSECTCOUNT(bitmapcolumn, columntofilter, filter_values) ``` `bitmap_column`: the bitmap column to be computed. `columntofilter`: the name of the column to be intersected. `filter_values`: the different values of the filtered dimension columns. Returns a value of the BIGINT type. Create an Aggregate table with a Bitmap column `user_id` and insert data. ```SQL CREATE TABLE `tbl` ( `dt` date NULL COMMENT "", `userid` bitmap BITMAPUNION NULL COMMENT "" ) ENGINE=OLAP AGGREGATE KEY(`dt`) COMMENT "OLAP" DISTRIBUTED BY HASH(`dt`); INSERT INTO `tbl` VALUES ('2020-10-01', to_bitmap(2)), ('2020-10-01', to_bitmap(3)), ('2020-10-01', to_bitmap(5)), ('2020-10-02', to_bitmap(2)), ('2020-10-02', to_bitmap(3)), ('2020-10-02', to_bitmap(4)), ('2020-10-03', to_bitmap(1)), ('2020-10-03', to_bitmap(5)), ('2020-10-03', to_bitmap(6)); SELECT dt, bitmaptostring(user_id) from tbl; +++ | dt | bitmaptostring(user_id) | +++ | 2020-10-02 | 2,3,4 | | 2020-10-03 | 1,5,6 | | 2020-10-01 | 2,3,5 | +++ ``` Calculate the number of same `user_id` corresponding to `'2020-10-01'` and `'2020-10-02'`. Two same elements (2 and 3) are found and the number `2` is returned. ```plaintext mysql> select intersectcount(userid, dt, '2020-10-01', '2020-10-02') from tbl where dt in ('2020-10-01', '2020-10-02'); +-+ | intersectcount(userid, dt, '2020-10-01', '2020-10-02') | +-+ | 2 | +-+ ``` Calculate the number of same `user_id` corresponding to `'2020-10-01'` and `'2020-10-03'`. One element `5` is found and the number `1` is returned. ```plaintext mysql> select intersectcount(userid, dt, '2020-10-01', '2020-10-03') from tbl where dt in ('2020-10-01', '2020-10-03'); +-+ | intersectcount(userid, dt, '2020-10-01', '2020-10-03') | +-+ | 1 | +-+ ```
Project: Redpanda (App Definition and Development / Streaming & Messaging)
File: pull_request_template.md

<!-- See https://github.com/redpanda-data/redpanda/blob/dev/CONTRIBUTING.md#pull-request-body for more details and examples of what is expected in a PR body. Content in this top section is REQUIRED. Describe, in plain language, the motivation behind the change (bug fix, feature, improvement) in this PR and how the included commits address it. Add the GitHub keyword `Fixes` to link to bug(s) this PR will fix, e.g. Fixes #ISSUE-NUMBER, Fixes #ISSUE-NUMBER, ... If this PR is a backport, link to the original with `Backport of PR`, e.g. Backport of PR #PR-NUMBER --> <!-- Checking at least one of the checkboxes is REQUIRED if this PR is not a backport. --> [ ] none - not a bug fix [ ] none - this is a backport [ ] none - issue does not exist in previous branches [ ] none - papercut/not impactful enough to backport [ ] v24.1.x [ ] v23.3.x [ ] v23.2.x <!-- If the changes in this PR do not need to be mentioned in the release notes, then don't add a sub-section and simply list `none`, e.g. none Otherwise, adding a sub-section or `none` is REQUIRED if the PR is not a backport PR. If this is a backport PR, adding contents to this section will override the release notes section inherited from the original PR to dev. Add one or more of the sub-sections with a short description bullet point of the change, e.g. Short description of the bug fix if this is a PR to `dev` branch. Short description of the feature. Explain how to configure. Short description of how this PR improves existing behavior. -->
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.37.0.md

Bump k8s.io/api from 0.29.0 to 0.29.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/808 Bump github.com/onsi/ginkgo/v2 from 2.14.0 to 2.15.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/810 Bump k8s.io/client-go from 0.29.0 to 0.29.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/811 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.36.0...v0.37.0
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.6.0.md

Add write function to deviceshifumqtt. by @hdy8200 in https://github.com/Edgenesis/shifu/pull/392 <BugFix>fix Indent of configmap on telemetryService by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/397 <BugFix>Close autoreconnect on opc ua to handle session full's bug by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/398 test: add TestCopyHeader by @180909 in https://github.com/Edgenesis/shifu/pull/393 chore: use `VersionFile` replace `version.txt` by @180909 in https://github.com/Edgenesis/shifu/pull/389 rebase v0.5.0 changes back to main by @tomqin93 in https://github.com/Edgenesis/shifu/pull/396 Update develop-on-mac-zh.md by @tianranhunda in https://github.com/Edgenesis/shifu/pull/388 @tianranhunda made their first contribution in https://github.com/Edgenesis/shifu/pull/388 @hdy8200 made their first contribution in https://github.com/Edgenesis/shifu/pull/392 Bump github.com/onsi/gomega from 1.24.0 to 1.24.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/381 Bump sigs.k8s.io/controller-runtime from 0.13.0 to 0.13.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/378 Bump k8s.io/client-go from 0.25.3 to 0.25.4 by @dependabot in https://github.com/Edgenesis/shifu/pull/385 Bump github.com/imdario/mergo from 0.3.12 to 0.3.13 by @dependabot in https://github.com/Edgenesis/shifu/pull/380 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.5.0...v0.6.0
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_drop_operator_class.md

title: DROP OPERATOR CLASS statement [YSQL] headerTitle: DROP OPERATOR CLASS linkTitle: DROP OPERATOR CLASS description: Use the DROP OPERATOR CLASS statement to remove an operator class. menu: v2.18: identifier: ddldropoperator_class parent: statements type: docs Use the `DROP OPERATOR CLASS` statement to remove an operator class. {{%ebnf%}} dropoperatorclass {{%/ebnf%}} See the semantics of each option in the . Basic example. ```plpgsql yugabyte=# CREATE OPERATOR CLASS myopclass FOR TYPE int4 USING btree AS OPERATOR 1 <, OPERATOR 2 <=; yugabyte=# DROP OPERATOR CLASS myopclass USING btree; ```
Project: Kapitan (Provisioning / Automation & Configuration)
File: 2023-01-16.md

author: Alessandro De Maria authorghuser: ademariag read_time: 10m date: 2022-12-04 The Kapicorp team is happy to to announce a new release of Kapitan. This release is yet another great bundle of features and improvements over the past year, the majority of which have been contributions from our community! Head over our on GitHub for a full list of features and contributors. If you missed it, have a look at our latest blog post here Please help us by visiting our page.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: configure-webhooks.md

Your Lagoon administrator will also give you the route to the `webhook-handler`. You will add this to your repository as an outgoing webhook, and choose which events to send to Lagoon. Typically, you will send all push and pull request events. In Lagoon it is possible to add a regular expression to determine which branches and pull requests actually result in a deploy, and your Lagoon administrator can set that up for you. For example, all branches that start with `feature-` could be deployed to Lagoon. <!-- markdown-link-check-disable --> ???+ Info "Info for amazee.io customers" If you are an amazee.io customer, the route to the webhook-handler is: . <!-- markdown-link-check-enable --> !!! danger Managing the following settings will require you to have a high level of access to these repositories, which will be controlled by your organization. If you cannot access these settings, please contact your systems administrator or the appropriate person within your organization. Proceed to Settings -&gt; Webhooks -&gt; `Add webhook` in your GitHub repository. The `Payload URL` is the route to the `webhook-handler` of your Lagoon instance, provided by your Lagoon administrator. Set `Content type` to `application/json`. Choose "`Let me select individual events`." Choose which events will trigger your webhook. We suggest that you send `Push` and `Pull request` events, and then filter further in the Lagoon configuration of your project. Make sure the webhook is set to `Active`. Click `Add webhook` to save your configuration. Navigate to Settings -&gt; Integrations in your GitLab repository. The `URL` is the route to the `webhook-handler` of your Lagoon instance, provided by your Lagoon administrator. Select the `Trigger` events which will send a notification to Lagoon. We suggest that you send `Push events` and `Merge request events`, and then filter further in the Lagoon configuration of your project. Click `Add webhook`to save your configuration. Navigate to Settings -&gt; Webhooks -&gt; Add new webhook in your repository. `Title` is for your reference. `URL` is the route to the `webhook-handler` of your Lagoon instance, provided by your Lagoon administrator. `Choose from a full list of triggers` and select the following: Repository Push Pull Request Created Updated Approved Approval removed Merged Declined Click `Save` to save the webhook configurations for Bitbucket.
Project: TiKV (App Definition and Development / Database)
File: PERFORMANCE_CRITICAL_PATH.md

There're many files whose functions are in the critical path of read or write requests. They're so important to the overall performance that any regression will directly impact user experience. We add a comment `#[PerformanceCriticalPath]` to highlight these critical files. Please note that this is the best-effort work and some files in critical path may not be marked. But if a file is marked, please pay special attention when you change its code. Here're some typical mistakes that should be avoided in the `#[PerformanceCriticalPath]` files: Unnecessary synchronous I/O. Here 'unnecessary' means it's not a MUST for serving the current user request. For example, ongcsnap() in peers.rs should spin off its I/O related work to background thread. Verbose logging with info or above log level. Global lock. Long tasks that do not have to be synchronous (Could be done in background thread instead). Below is the performance map that would help you to understand how read/write requests are executed inside TiKV:
Project: YDB (App Definition and Development / Database)
File: balancing-prefer-local.md

{% include %} Below are examples of the code for setting the "prefer the nearest data center" balancing algorithm option in different {{ ydb-short-name }} SDKs. {% list tabs %} Go (native) ```go package main import ( "context" "os" "github.com/ydb-platform/ydb-go-sdk/v3" "github.com/ydb-platform/ydb-go-sdk/v3/balancers" ) func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() db, err := ydb.Open(ctx, os.Getenv("YDBCONNECTIONSTRING"), ydb.WithBalancer( balancers.PreferLocalDC( balancers.RandomChoice(), ), ), ) if err != nil { panic(err) } defer db.Close(ctx) ... } ``` Go (database/sql) Client load balancing in the {{ ydb-short-name }} `database/sql` driver is performed only when establishing a new connection (in `database/sql` terms), which is a {{ ydb-short-name }} session on a specific node. Once the session is created, all queries in this session are passed to the node where the session was created. Queries in the same {{ ydb-short-name }} session are not balanced between different {{ ydb-short-name }} nodes. Example of the code for setting the "prefer the nearest data center" balancing algorithm option: ```go package main import ( "context" "database/sql" "os" "github.com/ydb-platform/ydb-go-sdk/v3" "github.com/ydb-platform/ydb-go-sdk/v3/balancers" ) func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() nativeDriver, err := ydb.Open(ctx, os.Getenv("YDBCONNECTIONSTRING"), ydb.WithBalancer( balancers.PreferLocalDC( balancers.RandomChoice(), ), ), ) if err != nil { panic(err) } defer nativeDriver.Close(ctx) connector, err := ydb.Connector(nativeDriver) if err != nil { panic(err) } db := sql.OpenDB(connector) defer db.Close() ... } ``` {% endlist %}