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

layout: global title: LIST JAR displayTitle: LIST JAR 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. `LIST JAR` lists the JARs added by . ```sql LIST { JAR | JARS } file_name [ ... ] ``` ```sql ADD JAR /tmp/test.jar; ADD JAR /tmp/test_2.jar; LIST JAR; -- output for LIST JAR spark://192.168.1.112:62859/jars/test.jar spark://192.168.1.112:62859/jars/test_2.jar LIST JAR /tmp/test.jar /some/random.jar /another/random.jar; -- output spark://192.168.1.112:62859/jars/test.jar ```
Project: StarRocks (App Definition and Development / Database)
File: map_from_arrays.md

displayed_sidebar: "English" Creates a MAP value from the given pair of key item array and value item array. This function is supported from v3.1 onwards. ```Haskell MAP mapfromarrays(ARRAY keys, ARRAY values) ``` `keys`: uses to construct the keys of the result MAP. Make sure the elements of keys are unique. `values`: used to construct the values of the result MAP. Returns a MAP that is constructed from the input keys and values. Keys and values must have the same length, otherwise it will return an error. If key or value is NULL, this function returns NULL. The returned MAP value has distinct keys. ```Plaintext select mapfromarrays([1, 2], ['Star', 'Rocks']); +--+ | mapfromarrays([1, 2], ['Star', 'Rocks']) | +--+ | {1:"Star",2:"Rocks"} | +--+ ``` ```Plaintext select mapfromarrays([1, 2], NULL); +-+ | mapfromarrays([1, 2], NULL) | +-+ | NULL | +-+ select mapfromarrays([1,3,null,2,null],['ab','cdd',null,null,'abc']); +--+ | mapfromarrays([1, 3, NULL, 2, NULL], ['ab', 'cdd', NULL, NULL, 'abc']) | +--+ | {1:"ab",3:"cdd",2:null,null:"abc"} | +--+ ```
Project: YugabyteDB (App Definition and Development / Database)
File: hlen.md

title: HLEN linkTitle: HLEN description: HLEN menu: preview: parent: api-yedis weight: 2150 aliases: /preview/api/redis/hlen /preview/api/yedis/hlen type: docs `HLEN key` This command fetches the number of fields in the hash that is associated with the given `key`. If the `key` does not exist, 0 is returned. If the `key` is associated with non-hash data, an error is raised. Returns number of fields in the specified hash. ```sh $ HSET yugahash area1 "Africa" ``` ``` 1 ``` ```sh $ HSET yugahash area2 "America" ``` ``` 1 ``` ```sh $ HLEN yugahash ``` ``` 2 ``` , , , , , , , , , ,
Project: Chef InSpec (Provisioning / Security & Compliance)
File: integration-testing.md

Chef InSpec uses Test Kitchen for its integration testing. Our current testing uses Docker (kitchen-dokken) as our backend. You should install and have Docker running before you run any tests. To run a specific integration test use the following: ```bash bundle exec rake test:integration[OS_NAME] ``` Example: ```bash bundle exec rake test:integration[default-ubuntu-1604] ``` We run the test/integration/default profile at the end of each integration test in the verify stage. This confirms that our current code is compatible with test kitchen. Audit cookbook testing is handled in the audit cookbook repo. In addition, the audit cookbook restricts which InSpec gem can be installed, forcing the installation from Rubygems for Chef clients 15+. Since we need to test with the from-source inspec gem, we can't use that approach. Instead, we don't test using audit cookbook here.
Project: ArangoDB (App Definition and Development / Database)
File: implicit_failure_copy_constructor.md

+++ title = "`basicresult(const failuretype<T> &)`" description = "Implicit error-from-failure-type-sugar copy constructor. Available if `predicate::enablecompatibleconversion<void, T, void>` is true, or `T` is `void`. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "tagged-constructors"] weight = 520 +++ Implicit error-from-failure-type-sugar copy constructor used to disambiguate the construction of the error type. Note that if `T = void`, `errortype` will be default constructed. Calls {{% api "void onresultcopyconstruction(T *, U &&) noexcept" %}} with `this` and `const failure_type<T> &`. Requires: `predicate::enablecompatibleconversion<void, T, void>` is true, or `T` is `void`. Complexity: Same as for the `errortype` constructor which accepts `T`, or the `errortype` default constructor if `T` is `void`. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_SNS.md

The following is a sample class and Lambda function that receives Amazon SNS event record data as input, writes some of the record data to CloudWatch Logs, and responds with a 200 status and the same body as the request. (Note that anything written to stdout or stderr will be logged as CloudWatch Logs events.) ```go import ( "context" "fmt" "github.com/aws/aws-lambda-go/events" ) func handler(ctx context.Context, snsEvent events.SNSEvent) { for _, record := range snsEvent.Records { snsRecord := record.SNS fmt.Printf("[%s %s] Message = %s \n", record.EventSource, snsRecord.Timestamp, snsRecord.Message) } } ```
Project: StarRocks (App Definition and Development / Database)
File: hex_decode_binary.md

displayed_sidebar: "English" Decodes a hex encoded string to a binary. This function is supported from v3.0. ```Haskell hexdecodebinary(str); ``` `str`: the string to convert. The supported data type is VARCHAR. An empty binary is returned if any of the following situations occur: The length of the string is 0 or the number of characters in the string is an odd number. The string contains characters other than `[0-9]`, `[a-z]`, and `[A-Z]`. Returns a value of the VARBINARY type. ```Plain Text mysql> select hex(hexdecodebinary(hex("Hello StarRocks"))); ++ | hex(hexdecodebinary(hex('Hello StarRocks'))) | ++ | 48656C6C6F2053746172526F636B73 | ++ mysql> select hexdecodebinary(NULL); +--+ | hexdecodebinary(NULL) | +--+ | NULL | +--+ ``` HEXDECODEBINARY
Project: Beam (App Definition and Development / Streaming & Messaging)
File: tolist.md

title: "BatchElements" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.combiners" class="ToList" >}} {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHON_ToList" show="tolist" >}} {{< /playground >}}
Project: Meshery (Provisioning / Automation & Configuration)
File: fluentd.md

layout: integration title: Fluentd Operator subtitle: Collaborative and visual infrastructure as code for Fluentd Operator image: /assets/img/integrations/fluentd/icons/color/fluentd-color.svg permalink: extensibility/integrations/fluentd docURL: https://docs.meshery.io/extensibility/integrations/fluentd description: integrations-category: Observability and Analysis integrations-subcategory: Logging registrant: Artifact Hub components: featureList: [ "Fluent Operator provides great flexibility in building a logging layer based on Fluent Bit and Fluentd.", "Fluentd Management: Deploy and destroy Fluentd StatefulSet automatically.", "Custom Configuration: Select input/filter/output plugins via labels." ] howItWorks: "Fluent Bit will be deployed as a DaemonSet while Fluentd will be deployed as a StatefulSet. " howItWorksDetails: "Although both Fluent Bit and Fluentd can collect, process(parse and filter) and then forward log to the final destinations, still they have strengths in different aspects. Fluent Bit is a good choice as a logging agent because of its lightweight and efficiency, while Fluentd is more powerful to perform advanced processing on logs because of its rich plugins. Fluent Bit only mode: If you just need to collect logs and send logs to the final destinations, all you need is Fluent Bit. Fluent Bit + Fluentd mode: If you also need to perform some advanced processing on the logs collected or send to more sinks, then you also need Fluentd. Fluentd only mode: If you need to receive logs through networks like HTTP or Syslog and then process and send the log to the final sinks, you only need Fluentd. Fluent Operator includes CRDs and controllers for both Fluent Bit and Fluentd which allows you to config your log processing pipelines in the 3 modes mentioned above as you wish." language: en list: include type: extensibility category: integrations
Project: KICS (Provisioning / Security & Compliance)
File: 8c849af7-a399-46f7-a34c-32d3dc96f1fc.md

title: ElastiCache Without VPC hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8c849af7-a399-46f7-a34c-32d3dc96f1fc Query name: ElastiCache Without VPC Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: ElastiCache should be launched in a Virtual Private Cloud (VPC)<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awselasticachecluster" "positive1" { cluster_id = "cluster-example" engine = "memcached" node_type = "cache.m4.large" numcachenodes = 2 parametergroupname = awselasticacheparameter_group.default.id port = 11211 } ``` ```tf title="Negative test num. 1 - tf file" resource "awselasticachecluster" "negative1" { cluster_id = "cluster-example" engine = "memcached" node_type = "cache.m4.large" numcachenodes = 2 parametergroupname = awselasticacheparameter_group.default.id port = 11211 subnetgroupname = var.subnetgroupname } ```
Project: TDengine (App Definition and Development / Database)
File: 04-load-balance.md

title: Load Balance sidebar_label: Load Balance description: This document describes how TDengine implements load balancing. The load balance in TDengine is mainly about processing data series data. TDengine employes builtin hash algorithm to distribute all the tables, sub-tables and their data of a database across all the vgroups that belongs to the database. Each table or sub-table can only be handled by a single vgroup, while each vgroup can process multiple table or sub-table. The number of vgroup can be specified when creating a database, using the parameter `vgroups`. ```sql create database db0 vgroups 100; ``` The proper value of `vgroups` depends on available system resources. Assuming there is only one database to be created in the system, then the number of `vgroups` is determined by the available resources from all dnodes. In principle more vgroups can be created if you have more CPU and memory. Disk I/O is another important factor to consider. Once the bottleneck shows on disk I/O, more vgroups may downgrad the system performance significantly. If multiple databases are to be created in the system, then the total number of `vroups` of all the databases are dependent on the available system resources. It needs to be careful to distribute vgroups among these databases, you need to consider the number of tables, data writing frequency, size of each data row for all these databases. A recommended practice is to firstly choose a starting number for `vgroups`, for example double of the number of CPU cores, then try to adjust and optimize system configurations to find the best setting for `vgroups`, then distribute these vgroups among databases. Furthermode, TDengine distributes the vgroups of each database equally among all dnodes. In case of replica 3, the distribution is even more complex, TDengine tries its best to prevent any dnode from becoming a bottleneck. TDegnine utilizes the above ways to achieve load balance in a cluster, and finally achieve higher throughput. Once the load balance is achieved, after some operations like deleting tables or dropping databases, the load across all dnodes may become imbalanced, the method of rebalance will be provided in later versions. However, even without explicit rebalancing, TDengine will try its best to achieve new balance without manual interfering when a new database is created.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: build-context.md

Specify an additional build context using its short name and its location. Additional build contexts can be referenced in the same manner as we access different stages in COPY instruction. Valid values are: Local directory e.g. --build-context project2=../path/to/project2/src (This option is not available with the remote Podman client. On Podman machine setup (i.e macOS and Windows) path must exists on the machine VM) HTTP URL to a tarball e.g. --build-context src=https://example.org/releases/src.tar Container image specified with a container-image:// prefix, e.g. --build-context alpine=container-image://alpine:3.15, (also accepts docker://, docker-image://) On the Containerfile side, reference the build context on all commands that accept the from parameter. Heres how that might look: ```dockerfile FROM [name] COPY --from=[name] ... RUN --mount=from=[name] ``` The value of [name] is matched with the following priority order: Named build context defined with --build-context [name]=.. Stage defined with AS [name] inside Containerfile Image [name], either local or in a remote registry
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: delete-mongodb-cluster.md

title: Delete a MongoDB Cluster description: How to delete a MongoDB Cluster keywords: [mongodb, delete a cluster, delete protection] sidebar_position: 7 sidebar_label: Delete protection import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; :::note The termination policy determines how a cluster is deleted. Set the policy when creating a cluster. ::: | terminationPolicy | Deleting Operation | |:-- | :-- | | `DoNotTerminate` | `DoNotTerminate` blocks delete operation. | | `Halt` | `Halt` deletes workload resources such as statefulset, deployment workloads but keep PVCs. | | `Delete` | `Delete` deletes workload resources and PVCs but keep backups. | | `WipeOut` | `WipeOut` deletes workload resources, PVCs and all relevant resources included backups. | To check the termination policy, execute the following command. <Tabs> <TabItem value="kbcli" label="kbcli" default> ```bash kbcli cluster list mongodb-cluster ``` </TabItem> <TabItem value="kubectl" label="kubectl"> ```bash kubectl -n demo get cluster mongodb-cluster NAME CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS AGE mongodb-cluster mongodb mongodb-5.0 Delete Running 17m ``` </TabItem> </Tabs> Run the command below to delete a specified cluster. <Tabs> <TabItem value="kbcli" label="kbcli" default> ```bash kbcli cluster delete mongodb-cluster ``` </TabItem> <TabItem value="kubectl" label="kubectl"> If you want to delete a cluster and its all related resources, you can modify the termination policy to `WipeOut`, then delete the cluster. ```bash kubectl patch -n demo cluster mongodb-cluster -p '{"spec":{"terminationPolicy":"WipeOut"}}' --type="merge" kubectl delete -n demo cluster mongodb-cluster ``` </TabItem> </Tabs>
Project: userver (App Definition and Development / Streaming & Messaging)
File: http_server.md

Quality: HTTP - @ref QUALITY_TIERS "Platinum Tier". HTTPS - @ref QUALITY_TIERS "Golden Tier". WebSocket - @ref QUALITY_TIERS "Golden Tier". userver implements HTTP/HTTPS 1.1 and WebSocket server in `userver-core` library using @ref components::Server component. HTTP 1.1/1.0 support; HTTPS; @ref scripts/docs/en/userver/tutorial/websocket_service.md "WebSocket"; Body decompression with "Content-Encoding: gzip"; HTTP pipelining; Custom authorization @ref scripts/docs/en/userver/tutorial/auth_postgres.md ; Rate limiting via Congestion control and indiviadual handlers configuration; Requests-in-flight limiting; Requests-in-flight inspection via server::handlers::InspectRequests ; Body size / headers count / URL length / etc. limits; Streaming; @ref scripts/docs/en/userver/tutorial/multipart_service.md "File uploads and multipart/form-data" @ref scripts/docs/en/userver/deadline_propagation.md . @ref scripts/docs/en/userver/httpservermiddlewares.md "Middlewares" Interactive clients (e.g. web browser) might want to get at least first bytes of the HTTP response if the whole HTTP response is generated slowly. In this case the HTTP handler might want to use Streaming API and return HTTP response body as a byte stream rather than as a single-part blob. To enable Streaming API in your handler: 1) define HandleStreamRequest() method: ```cpp ... void HandleStreamRequest(const server::http::HttpRequest&, server::request::RequestContext&, server::http::ResponseBodyStream&) const override; ``` 2) Enable Streaming API in static config: ```yaml components_manager: components: handler-stream-api: response-body-stream: true ``` 3) Set dynamic config @ref USERVERHANDLERSTREAMAPIENABLED. 4) Write your handler code: @snippet core/functionaltests/basicchaos/httpclient_handlers.hpp HandleStreamRequest @ref components::Server "Server"
Project: KubeEdge (Provisioning / Automation & Configuration)
File: RELEASE.md

The `yaml` Project is released on an as-needed basis. The process is as follows: An issue is proposing a new release with a changelog since the last release All must LGTM this release An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION` The release issue is closed An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] kubernetes-template-project $VERSION is released`
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.0-rc.5k.md

layout: release date: 2022-04-08 tag: v0.6.0-rc.5k language: en [Bug] - Fixed Upstream URL Issue @adithyaakrishna (#5359) potential fix for dde icon @warunicorn19 (#5358) dde_css @warunicorn19 (#5356) Update ADOPTERS.md @samirparhi-dev (#5353) [CI] Workflow DDE @leecalcote (#5351) Changed Description @hershd23 (#5350) small changes in dde @warunicorn19 (#5347) added browse in dde @warunicorn19 (#5343) Bump @types/react-relay from 11.0.2 to 13.0.2 in /ui @dependabot (#5332) Bump babel-plugin-relay from 11.0.2 to 13.2.0 in /ui @dependabot (#5333) Bump @types/react-relay from 11.0.2 to 13.0.2 in /ui @dependabot (#5332) Bump babel-plugin-relay from 11.0.2 to 13.2.0 in /ui @dependabot (#5333) Bump github.com/99designs/gqlgen from 0.17.1 to 0.17.2 @dependabot (#5324) [CI] Upgrade setup-go version @alphaX86 (#5354) [CI] Docker Extension for Meshery workflow @leecalcote (#5352) [CI] DDE: Fix release channel logic @leecalcote (#5349) Updated Contributing-gitflow(Readme) @Nandani-Paliwal (#5313) Thank you to our contributors for making this release possible: @Nandani-Paliwal, @adithyaakrishna, @alphaX86, @dependabot, @hershd23, @l5io, @leecalcote, @samirparhi-dev and @warunicorn19
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: README.md

This plugin provides an integration with Azure Active Directory device flow. If no tokens are present in the kubectl configuration, it will prompt a device code which can be used to login in a browser. After login it will automatically fetch the tokens and store them in the kubectl configuration. In addition it will refresh and update the tokens in the configuration when expired. Create an Azure Active Directory Web App / API application for `apiserver` following these . The callback URL does not matter (just cannot be empty). Create a second Azure Active Directory native application for `kubectl`. The callback URL does not matter (just cannot be empty). On `kubectl` application's configuration page in Azure portal grant permissions to `apiserver` application by clicking on Required Permissions, click the Add button and search for the apiserver application created in step 1. Select "Access apiserver" under the DELEGATED PERMISSIONS. Once added click the Grant Permissions button to apply the changes. Configure the `apiserver` to use the Azure Active Directory as an OIDC provider with following options ``` --oidc-client-id="spn:APISERVERAPPLICATIONID" \ --oidc-issuer-url="https://sts.windows.net/TENANT_ID/" --oidc-username-claim="sub" ``` Replace the `APISERVERAPPLICATIONID` with the application ID of `apiserver` application Replace `TENANT_ID` with your tenant ID. For a list of alternative username claims that are supported by the OIDC issuer check the JSON response at `https://sts.windows.net/TENANT_ID/.well-known/openid-configuration`. Configure `kubectl` to use the `azure` authentication provider ``` kubectl config set-credentials "USER_NAME" --auth-provider=azure \ --auth-provider-arg=environment=AzurePublicCloud \ --auth-provider-arg=client-id=APPLICATION_ID \ --auth-provider-arg=tenant-id=TENANT_ID \ --auth-provider-arg=apiserver-id=APISERVERAPPLICATIONID ``` Supported environments: `AzurePublicCloud`, `AzureUSGovernmentCloud`, `AzureChinaCloud`, `AzureGermanCloud` Replace `USERNAME` and `TENANTID` with your user name and tenant ID Replace `APPLICATION_ID` with the application ID of your`kubectl` application ID Replace `APISERVERAPPLICATIONID` with the application ID of your `apiserver` application ID Be sure to also (create and) select a context that uses above user (Optionally) the AAD token has `aud` claim with `spn:` prefix. To omit that, add following auth configuration: ``` --auth-provider-arg=config-mode="1" ``` The access token is acquired when first `kubectl` command is executed ``` kubectl get pods To sign in, use a web browser to open the page https://aka.ms/devicelogin and enter the code DEC7D48GA to authenticate. ``` After signing in a web browser, the token is stored in the configuration, and it will be reused when executing further commands. The resulting username in Kubernetes depends on your . If you are using any authorization method you need to give permissions to that user, e.g. by binding the user to a role in the case of RBAC.
Project: ArangoDB (App Definition and Development / Database)
File: explicit_inplace_value_constructor_il.md

+++ title = "`explicit basicresult(inplacetypet<valuetypeifenabled>, std::initializerlist<U>, Args ...)`" description = "Explicit inplace value constructor. Available if `predicate::enableinplacevalueconstructor<std::initializerlist<U>, Args ...>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "inplace-constructors"] weight = 410 +++ Explicit inplace value constructor. Calls {{% api "void onresultinplaceconstruction(T *, inplacetypet<U>, Args &&...) noexcept" %}} with `this`, `inplacetype<valuetype>`, 'std::initializer_list<U>' and `Args ...`. Requires: `predicate::enableinplacevalueconstructor<std::initializerlist<U>, Args ...>` is true. Complexity: Same as for the `valuetype` constructor which accepts `std::initializerlist<U>, Args ...`. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the state of the Args is left indeterminate.