cwielenb/CNCF-Dataset huggingface dataset:
Project: YDB (App Definition and Development / Database)
File: grpc-headers.md

{{ ydb-short-name }} uses the following gRPC metadata headers: gRPC headers which a client sends to {{ ydb-short-name }}: `x-ydb-database` - database `x-ydb-auth-ticket` - auth token from a credentials provider `x-ydb-sdk-build-info` - {{ ydb-short-name }} SDK build info `x-ydb-trace-id` - user-defined request ID. If not defined by client {{ ydb-short-name }} SDK generates automatically using format `x-ydb-application-name` - optional user-defined application name `x-ydb-client-capabilities` - supported client SDK capabilities (`session-balancer` and other) `x-ydb-client-pid` - client application process ID `traceparent` - OpenTelemetry trace ID () gRPC headers which {{ ydb-short-name }} sends to client with responses: `x-ydb-server-hints` - notifications from {{ ydb-short-name }} (such as `session-close` and other) `x-ydb-consumed-units` - consumed units on the current request
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.1.1-beta.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | Add user info in the YARN ClientToken* WARNING: No release note provided for this change. | Major | Provide testing support for DFSClient to drop RPC responses* Used for testing when NameNode HA is enabled. Users can use a new configuration property "dfs.client.test.drop.namenode.response.number" to specify the number of responses that DFSClient will drop in each RPC call. This feature can help testing functionalities such as NameNode retry cache. | Blocker | yarn proto definitions should specify package as 'hadoop.yarn'* WARNING: No release note provided for this change. | Blocker | RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION\_CONTEXT\_CALL\_ID is signed (-3)* WARNING: No release note provided for this change.
Project: ClickHouse (App Definition and Development / Database)
File: v22.7.5.13-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix TGZ packages. (). Backported in : Fix potential deadlock in WriteBufferFromS3 during task scheduling failure. (). Backported in : Fix rare bug with column TTL for MergeTree engines family: In case of repeated vertical merge the error `Cannot unlink file ColumnName.bin ... No such file or directory.` could happen. (). Backported in : Proxy resolver stop on first successful request to endpoint. (). Backported in : Fix potential dataloss due to a bug in AWS SDK (https://github.com/aws/aws-sdk-cpp/issues/658). Bug can be triggered only when clickhouse is used over S3. (). DNSResolver remove AIV4MAPPED, AIALL hints ().
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: CONTRIBUTING.md

Thank you so much for contributing to Cobra. We appreciate your time and help. Here are some guidelines to help you get started. Be kind and respectful to the members of the community. Take time to educate others who are seeking help. Harassment of any kind will not be tolerated. If you have questions regarding Cobra, feel free to ask it in the community Before filing an issue, please check the existing issues to see if a similar one was already opened. If there is one already opened, feel free to comment on it. If you believe you've found a bug, please provide detailed steps of reproduction, the version of Cobra and anything else you believe will be useful to help troubleshoot it (e.g. OS environment, environment variables, etc...). Also state the current behavior vs. the expected behavior. If you'd like to see a feature or an enhancement please open an issue with a clear title and description of what the feature is and why it would be beneficial to the project and its users. CLA: Upon submitting a Pull Request (PR), contributors will be prompted to sign a CLA. Please sign the CLA :slightlysmilingface: Tests: If you are submitting code, please ensure you have adequate tests for the feature. Tests can be run via `go test ./...` or `make test`. Since this is golang project, ensure the new code is properly formatted to ensure code consistency. Run `make all`. Fork the project. Download your fork to your PC (`git clone https://github.com/your_username/cobra && cd cobra`) Create your feature branch (`git checkout -b my-new-feature`) Make changes and run tests (`make test`) Add them to staging (`git add .`) Commit your changes (`git commit -m 'Add some feature'`) Push to the branch (`git push origin my-new-feature`) Create new pull request <!-- Links -->
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_alter_index.md

title: ALTER INDEX statement [YSQL] headerTitle: ALTER INDEX linkTitle: ALTER INDEX description: Use the `ALTER INDEX` statement to change the definition of an index. menu: preview: identifier: ddlalterindex parent: statements aliases: /preview/api/ysql/commands/ddlalterindex/ type: docs Use the `ALTER INDEX` statement to change the definition of an index. {{%ebnf%}} alter_index, alterindexaction, {{%/ebnf%}} Specify one of the following actions. Rename the index to the specified index name. {{< note title="Note" >}} Renaming an index is a non-blocking metadata change operation. {{< /note >}} Set the per-column statistics-gathering target for subsequent ANALYZE operations. It can only be used on index columns that are defined as an expression. Since expressions lack a unique name, we refer to them using the ordinal number of the index column. The value can be set in the range 0 to 10000. The default `-1` uses the system default statistics target (`defaultstatisticstarget`). ```sql yugabyte=# CREATE TABLE attmp (initial int4, a int4 default 3, b name,d float8,e float4); yugabyte=# CREATE INDEX attmp_idx ON attmp (a, (d + e), b); yugabyte=# ALTER INDEX attmp_idx ALTER COLUMN 0 SET STATISTICS 1000; ERROR: column number must be in range from 1 to 32767 LINE 1: ALTER INDEX attmp_idx ALTER COLUMN 0 SET STATISTICS 1000; yugabyte=# ALTER INDEX attmp_idx ALTER COLUMN 1 SET STATISTICS 1000; ERROR: cannot alter statistics on non-expression column "a" of index "attmp_idx" HINT: Alter statistics on table column instead. yugabyte=# ALTER INDEX attmp_idx ALTER COLUMN 2 SET STATISTICS 1000; yugabyte=# \d+ attmp_idx Index "public.attmp_idx" Column | Type | Key? | Definition | Storage | Stats target --+++++-- a | integer | yes | a | plain | expr | double precision | yes | (d + e) | plain | 1000 b | name | yes | b | plain | lsm, for table "public.attmp" ``` Asynchronously change the tablespace of an existing index. The tablespace change will immediately reflect in the config of the index, however the tablet move by the load balancer happens in the background. While the load balancer is performing the move it is perfectly safe from a correctness perspective to do reads and writes, however some query optimization that happens based on the data location may be off while data is being moved. ```sql yugabyte=# ALTER INDEX banktransactionsidx SET TABLESPACE eucentral1_tablespace; ``` ```output NOTICE: Data movement for index banktransactionsidx is successfully initiated. DETAIL: Data movement is a long running asynchronous process and can be monitored by checking the tablet placement in http://<YB-Master-host>:7000/tables ALTER INDEX ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.15.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Need configuration guides for Hadoop | Critical | documentation | Sameer Paranjpye | Arun C Murthy | | | dfs list operation is too expensive | Blocker | . | Hairong Kuang | dhruba borthakur | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | distcp throws a NullPointerException in the close() method of mapper class due to the Reporter becoming invalid | Critical | util | Riccardo Boscolo | Chris Douglas | | | libhdfs makefile wrongly sets up DT\_SONAME field of libhdfs.so | Critical | . | Arun C Murthy | Arun C Murthy | | | PositionCache was removed from FSDataInputStream, causes extremely bad MapFile performance | Blocker | fs | Johan Oskarsson | Doug Cutting | | | Regenerate entire hadoop website since site.xml was changed by HADOOP-1917 | Blocker | documentation | Arun C Murthy | Arun C Murthy | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | C and C++ files are missing Apache license header | Blocker | . | Owen O'Malley | Owen O'Malley |
Project: Flink (App Definition and Development / Streaming & Messaging)
File: sort-cluster-distribute-by.md

title: "Sort/Cluster/Distributed By" weight: 2 type: docs <!-- 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. --> Unlike which guarantees a total order of output, `SORT BY` only guarantees the result rows with each partition is in the user specified order. So when there's more than one partition, `SORT BY` may return result that's partially ordered. ```sql query: SELECT expression [ , ... ] FROM src sortBy sortBy: SORT BY expression colOrder [ , ... ] colOrder: ( ASC | DESC ) ``` colOrder it's used specified the order of returned rows. The default order is `ASC`. ```sql SELECT x, y FROM t SORT BY x; SELECT x, y FROM t SORT BY abs(y) DESC; ``` The `DISTRIBUTE BY` clause is used to repartition the data. The data with same value evaluated by the specified expression will be in same partition. ```sql distributeBy: DISTRIBUTE BY expression [ , ... ] query: SELECT expression [ , ... ] FROM src distributeBy ``` ```sql -- only use DISTRIBUTE BY clause SELECT x, y FROM t DISTRIBUTE BY x; SELECT x, y FROM t DISTRIBUTE BY abs(y); -- use both DISTRIBUTE BY and SORT BY clause SELECT x, y FROM t DISTRIBUTE BY x SORT BY y DESC; ``` `CLUSTER BY` is a short-cut for both `DISTRIBUTE BY` and `SORT BY`. The `CLUSTER BY` is used to first repartition the data based on the input expressions and sort the data with each partition. Also, this clause only guarantees the data is sorted within each partition. ```sql clusterBy: CLUSTER BY expression [ , ... ] query: SELECT expression [ , ... ] FROM src clusterBy ``` ```sql SELECT x, y FROM t CLUSTER BY x; SELECT x, y FROM t CLUSTER BY abs(y); ```
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: event-listener.md

The SeaTunnel provides a rich event listening feature that allows you to manage the status at which data is synchronized. This functionality is crucial when you need to listen job running status(`org.apache.seatunnel.api.event`). This document will guide you through the usage of these parameters and how to leverage them effectively. SeaTunnel Zeta<br/> Flink<br/> Spark<br/> The event API is defined in the `org.apache.seatunnel.api.event` package. `org.apache.seatunnel.api.event.Event` - The interface for event data. `org.apache.seatunnel.api.event.EventType` - The enum for event type. You can customize event handler, such as sending events to external systems `org.apache.seatunnel.api.event.EventHandler` - The interface for event handler, SPI will automatically load subclass from the classpath. `org.apache.seatunnel.api.source.SourceSplitEnumerator` - Attached event listener API to report events from `SourceSplitEnumerator`. ```java package org.apache.seatunnel.api.source; public interface SourceSplitEnumerator { interface Context { / Get the {@link org.apache.seatunnel.api.event.EventListener} of this enumerator. * @return */ EventListener getEventListener(); } } ``` `org.apache.seatunnel.api.source.SourceReader` - Attached event listener API to report events from `SourceReader`. ```java package org.apache.seatunnel.api.source; public interface SourceReader { interface Context { / Get the {@link org.apache.seatunnel.api.event.EventListener} of this reader. * @return */ EventListener getEventListener(); } } ``` `org.apache.seatunnel.api.sink.SinkWriter` - Attached event listener API to report events from `SinkWriter`. ```java package org.apache.seatunnel.api.sink; public interface SinkWriter { interface Context { / Get the {@link org.apache.seatunnel.api.event.EventListener} of this writer. * @return */ EventListener getEventListener(); } } ``` To use the event listening feature, you need to configure engine config. Example config in your config file(seatunnel.yaml): ``` seatunnel: engine: event-report-http: url: "http://example.com:1024/event/report" headers: Content-Type: application/json ``` You can define the implementation class of `org.apache.seatunnel.api.event.EventHandler` interface and add to the classpath to automatically load it through SPI. Support flink version: 1.14.0+ Example: `org.apache.seatunnel.api.event.LoggingEventHandler` You can define the implementation class of `org.apache.seatunnel.api.event.EventHandler` interface and add to the classpath to automatically load it through SPI.
Project: Stolon (App Definition and Development / Database)
File: stolonctl_failkeeper.md

Force keeper as "temporarily" failed. The sentinel will compute a new clusterdata considering it as failed and then restore its state to the real one. Force keeper as "temporarily" failed. It's just a one shot operation, the sentinel will compute a new clusterdata considering the keeper as failed and then restore its state to the real one. For example, if the force failed keeper is a master, the sentinel will try to elect a new master. If no new master can be elected, the force failed keeper, if really healthy, will be re-elected as master ``` stolonctl failkeeper [keeper uid] [flags] ``` ``` -h, --help help for failkeeper ``` ``` --cluster-name string cluster name --kube-context string name of the kubeconfig context to use --kube-namespace string name of the kubernetes namespace to use --kube-resource-kind string the k8s resource kind to be used to store stolon clusterdata and do sentinel leader election (only "configmap" is currently supported) --kubeconfig string path to kubeconfig file. Overrides $KUBECONFIG --log-level string debug, info (default), warn or error (default "info") --metrics-listen-address string metrics listen address i.e "0.0.0.0:8080" (disabled by default) --store-backend string store backend type (etcdv2/etcd, etcdv3, consul or kubernetes) --store-ca-file string verify certificates of HTTPS-enabled store servers using this CA bundle --store-cert-file string certificate file for client identification to the store --store-endpoints string a comma-delimited list of store endpoints (use https scheme for tls communication) (defaults: http://127.0.0.1:2379 for etcd, http://127.0.0.1:8500 for consul) --store-key string private key file for client identification to the store --store-prefix string the store base prefix (default "stolon/cluster") --store-skip-tls-verify skip store certificate verification (insecure!!!) --store-timeout duration store request timeout (default 5s) ``` - stolon command line client
Project: Meshery (Provisioning / Automation & Configuration)
File: skooner.md

layout: integration title: Skooner subtitle: Collaborative and visual infrastructure as code for Skooner image: /assets/img/integrations/skooner/icons/color/skooner-color.svg permalink: extensibility/integrations/skooner docURL: https://docs.meshery.io/extensibility/integrations/skooner description: integrations-category: Observability and Analysis integrations-subcategory: Monitoring registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] 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: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_kubectl.InvolvedObject.md

/ / InvolvedObject .InvolvedObject Trait that defines an involvedObject, e.g. for Events involvedObject: `Object` | Name | Type | | :-- | :- | | `apiVersion` | `string` | | `fieldPath?` | `string` | | `kind` | `string` | | `name` | `string` | | `namespace` | `string` | | `resourceVersion?` | `string` | | `uid?` | `string` |
Project: Sonobuoy (Provisioning / Security & Compliance)
File: aggregator-permissions.md

By default, the Sonobuoy aggregator is given very elevated permissions in order to successfully run the Kubernetes end-to-end tests. In some situations you may want to (or need to) limit the permissions of the aggregator so that the aggregator and the pods that it creates do not have such wide-reaching permissions. You can always customize the exact permissions of the ServiceAccount via editing `sonobuoy gen` output manually, but Sonobuoy also provides useful presets via the CLI flag, `--aggregator-permissions`. Allowable values are `[namespaced, clusterAdmin, clusterRead]`, `clusterAdmin` is default value. `clusterAdmin` is the default value. With this value Sonobuoy can do pretty much everything in the run, it does not implement any restrictions. Most of these are required for the e2e conformance tests to work since they create/destroy namespaces, pods etc. namespaceAdmin is the most restrictive preset permissions Sonobuoy provides and ensures that Sonobuoy and its plugins do not impact other namespaces at all. Due to these limitations there are a number of things to note: Sonobuoy does not create the namespace so it needs to already exist You must provide `--skip-preflight` to avoid Sonobuoy from complaining about the preexisting namespace The `e2e` plugin (conformance tests) will not work in this mode and won't even start up due to severely limited permissions Daemonset plugins will not work in this mode because Sonobuoy monitors them on a per-node basis. Since Sonobuoy can't query the list of nodes in the cluster, it can't properly monitor or gather results from them. At this time, Daemonset plugins will simply be ignored. `clusterRead` is a compromise between `namespaceAdmin` and `clusterAdmin`. It adds ability to GET any resource from the API so that the Sonobuoy queries work OK, it is able to get nodes so daemonsets run fine, and e2e tests can technically start. Sonobuoy can't create namespaces so e2e tests can't run in this mode in any useful manner either. However, this may be a more reasonable mode to run less intrusive, custom plugins in. In this mode Sonobuoy don't create the namespace either so it has to be created first and sonobuoy run with the `--skip-preflight` flag.
Project: CloudMatos (Provisioning / Security & Compliance)
File: README.md

Unless your use case requires public sharing to be turned on, we recommend turning on the block public sharing setting for your AWS Systems Manager (SSM) documents. Turning on this setting prevents unwanted access to your SSM documents. The block public sharing setting is an account level setting that can differ for each AWS Region Remediation Tool - Remediation Script - The below requirements are needed to execute remediation script pip packages python >= 3.6 boto3 >= 1.15.0 botocore >= 1.18.0 | Parameter | Comments | | | | | awsaccesskey | AWS Access key | | awssecretkey | AWS Secret key | | aws_region | AWS Region | Following command need to execute ```sh ansible-playbook playbook.yaml -e '{ "awsaccesskey": "xxxx", "awssecretkey": "xxxx", "aws_region": "xxxx" }' ``` ments | | | | | awsaccesskey | AWS Access key | | awssecretkey | AWS Secret key | | awsregion | The AWS region to use. If not specified then the value of the AWSREGION or EC2REGION environment variable, if any, is used. See http://docs.aws.amazon.com/general/latest/gr/rande.html#ec2region | | security_groups | security groups info | Following command need to execute ```sh ansible-playbook playbook.yml --extra-vars '{ "awssecretkey": "XXXXX", "awsaccesskey": "XXXXX", "aws_region": "XXXXX", "security_groups":[{ "GroupId":"sg-xxxxx", "IpPermissions":[{ "FromPort":"22 or 3306 etc.", "ToPort":"22 or 3306 etc.", "IpProtocol":"tcp", "Ipv6Ranges":[], "IpRanges":[{"CidrIp":"0.0.0.0/0"}] }] }] }' ```
Project: external-secrets (Provisioning / Security & Compliance)
File: onboardbase.md

Sync secrets from to Kubernetes using the External Secrets Operator. Create the Onboardbase API by opening the organization tab under your account settings: And view them under the team name in your Account settings Create an Onboardbase API secret with your API Key and Passcode value: ```sh HISTIGNORE='kubectl' \ kubectl create secret generic onboardbase-auth-secret \ --from-literal=API_KEY=VZYKYJNMMEMK \ --from-literal=PASSCODE=api-key-passcode ``` Then to create a generic `SecretStore`: ```yaml {% include 'onboardbase-generic-secret-store.yaml' %} ``` The below operations are possible with the Onboardbase provider: Let's explore each use case using a fictional `auth-api` Onboardbase project. To sync one or more individual secrets: ```yaml {% include 'onboardbase-fetch-secret.yaml' %} ``` To sync every secret from a config: ```yaml {% include 'onboardbase-fetch-all-secrets.yaml' %} ``` To filter secrets by `path` (path prefix), `name` (regular expression) or a combination of both: ```yaml {% include 'onboardbase-filtered-secrets.yaml' %} ```
Project: ArangoDB (App Definition and Development / Database)
File: httplib.md

+++ title = "The HTTP library" weight = 10 +++ Let us imagine a simple application: it fetches a HTTP page using a HTTP library, sends it through HTML tidy via the htmltidy library, and then writes it to disc using a filelib library. So three third party libraries, two using Outcome in incompatible ways, and the third being a C library just for kicks. Let us imagine that the HTTP library has the following public interface: {{% snippet "finale.cpp" "httplib" %}} The HTTP library is a mixed-failure design. Likely failures (HTTP status codes) are returned via `httplib::failure`, unlikely failures (e.g. out of memory) are returned via throw of the usual STL exception types. The sole API we bother describing is an implementation of HTTP GET. It fetches a URL, and either returns the contents or the failure reason why not.
Project: StarRocks (App Definition and Development / Database)
File: collations.md

displayed_sidebar: "English" `collations` contains the available collations. The following fields are provided in `collations`: | Field | Description | | | | | COLLATION_NAME | The collation name. | | CHARACTERSETNAME | The name of the character set with which the collation is associated. | | ID | The collation ID. | | IS_DEFAULT | Whether the collation is the default for its character set. | | IS_COMPILED | Whether the character set is compiled into the server. | | SORTLEN | This is related to the amount of memory required to sort strings expressed in the character set. |