cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: sql-feature-support.md

title: SQL feature support linkTitle: SQL feature support description: Summary of YugabyteDB's conformance to the SQL standard headcontent: YugabyteDB supports most standard SQL features. menu:

identifier: explore-ysql-language-feature-support parent: explore-ysql-language-features weight: 50 type: docs To understand which standard SQL features we support, refer to the following tables: | Data type | Supported | Documentation | | :-- | :-: | : | | `ARRAY` | | | | `BINARY` | | | | `BIT`,`BYTES` | | | | `BOOLEAN` | | | | `CHAR`, `VARCHAR`, `TEXT` | | | | `COLLATE` | | | | `DATE`, `TIME`, `TIMESTAMP`, `INTERVAL` | | | | `DEC`, `DECIMAL`, `NUMERIC` | | | | `ENUM` | | | | `FLOAT`, `REAL`, `DOUBLE PRECISION` | | | | `JSON`, `JSONB` | | | | `MONEY` | | | | `SERIAL`, `SMALLSERIAL`, `BIGSERIAL`| | | | `SMALLINT, INT, INTEGER, BIGINT` | | | | `INT4RANGE`, `INT8RANGE`, `NUMRANGE`, `TSRANGE`, `TSTZRANGE`, `DATERANGE` | | | | `UUID` | | | | `XML`| | | | `TSVECTOR` | | | | UDT(Base, Enumerated, Range, Composite, Array, Domain types) | | | | Operation | Supported | Documentation | | :-- | :-: | : | | Altering tables | (Partial) | | | Altering databases | | | | Altering a column's name | | | | Altering a column's default value | | | | Altering a column's data type | (Partial) | | | Adding columns | | | | Removing columns | | | | Adding constraints | | | | Removing constraints | | | | Altering indexes | | | | Adding indexes | | | | Removing indexes | | | | Adding a primary key | | | | Dropping a primary key | | | | Altering a primary key | | | | Adding user-defined schemas | | | | Removing user-defined schemas | | | | Altering user-defined schemas | | | | Feature | Supported | Documentation | | : | :-: | : | | Check | | | | Unique | | | | Not Null | | | | Primary Key | | | | Foreign Key | | | | Default Value | (Partial)| | | Deferrable Foreign Key constraints | (Partial) | | | Deferrable Primary Key and Unique constraints | | | | Exclusion constraints| | | | Component | Supported | Documentation | | :-- | :-: | : | | Indexes | | | | GIN indexes | | | | Partial indexes | | | | Expression indexes | | | | Multi-column indexes | | | | Covering indexes | | | | GiST indexes | | | | BRIN indexes | | | | B-tree indexes | | B-tree index is treated as an LSM index. | | Feature | Supported | Documentation | | : | :-: | : | | Transactions | | | | `BEGIN` | | | | `COMMIT` | | | | `ROLLBACK` | | | | `SAVEPOINT` | | | | `ROLLBACK TO SAVEPOINT` | | | | `PREPARE TRANSACTION (XA)` | | | Component | Supported | Details | | :-- | :-: | : | | Users | | | | Roles | | | | Object ownership | | | | Privileges | | | | Default privileges | | | | Row level security | | | | Column level security | | | | Component | Supported | Details | | :-- | :-: | : | | FROM, WHERE, GROUP BY, HAVING, DISTINCT, LIMIT/OFFSET, WITH queries| | | | EXPLAIN query plans| | | | JOINs (INNER/OUTER, LEFT/RIGHT) | | | | Expressions and Operators| | | | Common Table Expressions
Project: EJBCA Community (Provisioning / Security & Compliance)
File: LICENSE.md

Software License Agreement (BSD License) ======================================== Copyright 2014 Yahoo! Inc. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the Yahoo! Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL YAHOO! INC. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Normalize.css License ===================== Copyright (c) Nicolas Gallagher and Jonathan Neal Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: volumes.md

`Volumes` can be mounted to , or containers. Following example shows how to mount a ConfigMap to an `udsource` vertex, an `udf` vertex and an `udsink` vertex. ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: my-pipeline spec: vertices: name: my-source volumes: name: my-udsource-config configMap: name: udsource-config source: udsource: container: image: my-source:latest volumeMounts: mountPath: /path/to/my-source-config name: my-udsource-config name: my-udf volumes: name: my-udf-config configMap: name: udf-config udf: container: image: my-function:latest volumeMounts: mountPath: /path/to/my-function-config name: my-udf-config name: my-sink volumes: name: my-udsink-config configMap: name: udsink-config sink: udsink: container: image: my-sink:latest volumeMounts: mountPath: /path/to/my-sink-config name: my-udsink-config ```
Project: Fluvio (App Definition and Development / Streaming & Messaging)
File: TEST_CASE.md

Local Non TLS ``` make RELEASE=true DEFAULTITERATION=5000 SERVERLOG=info smoke-test ``` Local TLS ``` make RELEASE=true DEFAULTITERATION=5000 SERVERLOG=info smoke-test-tls-root ``` K8 Non TLS ``` make RELEASE=true DEFAULTITERATION=5000 SERVERLOG=info smoke-test-k8 ``` K8 TLS ``` make RELEASE=true DEFAULTITERATION=5000 SERVERLOG=info smoke-test-k8-tls-root ``` Local Non TLS ``` make RELEASE=true DEFAULTITERATION=5000 DEFAULTSPU=2 SERVER_LOG=info smoke-test ``` Iteration: 5000, Record size: 5k Log size: 25M ``` flvt --local-driver -p 5000 --record-size 5000 --spu 2 --replication 2 ``` Create cluster ``` fluvio cluster start --spu 3 --local `` Create topic with replica 3 ``` fluvio topic create -r 3 topic ``` Identity a leader: ``` fluvio partition list ``` Produce a message ``` fluvio produce topic ``` ``` fluvio consume topic -B -d ``` Kill a leader SPU ``` ps -ef | grep fluvio ``` Verify that SPU is offline ``` fluvio spu list ``` 2nd SPU should take over, this should still work: ``` flvd consume topic -B -d ```
Project: ShardingSphere (App Definition and Development / Database)
File: show-plugins.en.md

+++ title = "SHOW PLUGINS OF SPI" weight = 1 +++ The `SHOW PLUGINS OF interfaceClass` syntax is used to query all the implementations of an interface. {{< tabs >}} {{% tab name="Grammar" %}} ```sql showPluginImplementations ::= 'SHOW' 'PLUGINS' 'OF' interfaceClass interfaceClass ::= string ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Columns | Description | |--|--| | type | type | | type_aliases | type aliases | | description | description | Query all the implementations for `org.apache.shardingsphere.sharding.spi.ShardingAlgorithm` interface ```sql SHOW PLUGINS OF 'org.apache.shardingsphere.sharding.spi.ShardingAlgorithm' ``` ```sql SHOW PLUGINS OF 'org.apache.shardingsphere.sharding.spi.ShardingAlgorithm'; +-+--+-+ | type | type_aliases | description | +-+--+-+ | MOD | | | | HASH_MOD | | | | VOLUME_RANGE | | | | BOUNDARY_RANGE | | | | AUTO_INTERVAL | | | | INTERVAL | | | | CLASS_BASED | | | | INLINE | | | | COMPLEX_INLINE | | | | HINT_INLINE | | | +-+--+-+ 10 rows in set (0.52 sec) ``` For some commonly used interface implementations, ShardingSphere provides syntax sugar functions to simplify operations. The currently provided syntax sugar are as follows: Show implementations of `org.apache.shardingsphere.sharding.spi.ShardingAlgorithm`: Show implementations of `org.apache.shardingsphere.infra.algorithm.loadbalancer.core.LoadBalanceAlgorithm`: Show implementations of `org.apache.shardingsphere.encrypt.spi.EncryptAlgorithm`: Show implementations of `org.apache.shardingsphere.mask.spi.MaskAlgorithm`: Show implementations of `org.apache.shardingsphere.shadow.spi.ShadowAlgorithm`: Show implementations of `org.apache.shardingsphere.keygen.core.algorithm.KeyGenerateAlgorithm`: `SHOW`, `PLUGINS`, `OF`
Project: Ansible (Provisioning / Automation & Configuration)
File: wider_discussion.md

Hi! Thanks very much for your submission to Ansible. It means a lot to us. We are interested in this idea and would like to see a wider discussion on it on one of our lists. Reasons for this include: INSERT REASONS! Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time. Can you please post on ansible-development list so we can talk about this idea with the wider group? <https://groups.google.com/forum/#!forum/ansible-devel> Matrix: #ansible-devel on For other alternatives, check this page for a more complete list of communication channels and their purposes: <https://docs.ansible.com/ansible/latest/community/communication.html> Thank you once again for this and your interest in Ansible!
Project: StreamSets (App Definition and Development / Streaming & Messaging)
File: README.md

<!-- Copyright 2016 StreamSets Inc. 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. See accompanying LICENSE file. --> Origin acting as MySql replication slave. It consumes events directly from MySql binary log using library . Events consumed from log are further enriched with columns names and converted to `Record` with appropriate data types. Origin works well with MySql servers with and without GTID enabled. GTID support Origin works both with GTID enabled and disabled. But if you change GTID mode on/off on the server - please reset origin, as it will not be able to parse offset correctly. Origin connects to mysql with `ssl=off`, if you need to change this - please change the source. Origin may produce more records than `maxBatchSize`, because individual `update/delete` events may affect many rows and they all are processed as one event. But mysql internally breaks statements affecting many rows to multiple events with moderate rows count in each. Origin can work with `binlogrowimage=MINIMAL`, but in this case it does not include default columns values for inserts. Origin does not check server's `serverId`, so its up to you to setup offset correctly when connecting to different server if GTID is off. When GTID is on - it does not matter. In case of server errors origin stops. If mysql connector cannot parse some event (it is known that this happens with `POINT` columns) - error is logged, but origin continues working. Known issue - if you start from beginning on first start and there very schema changes between first binlog event and current time - result may be unpredictable. The same issue happens if you stop origin, make changes to schema (drop a column for example) and then start origin. If it meets some event for table with changed schema - it may produce complete nonsense.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_delete.md

Delete a YugabyteDB Anywhere provider Delete a provider in YugabyteDB Anywhere ``` yba provider delete [flags] ``` ``` -n, --name string [Required] The name of the provider to be deleted. -c, --code string [Optional] Code of the provider. Allowed values: aws, gcp, azu, onprem, kubernetes. -f, --force [Optional] Bypass the prompt for non-interactive usage. -h, --help help for delete ``` ``` -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) ``` - Manage YugabyteDB Anywhere providers
Project: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_images_push.md

Pushes images to docker registry for a specific plugin ``` sonobuoy images push [flags] ``` ``` --context string Context in the kubeconfig to use. --custom-registry string Specify a registry to override the Sonobuoy and Plugin image registries. --dry-run If true, only print the image operations that would be performed. --e2e-repo string Specify a registry for KUBETESTREPO, overriding registries for test images. --e2e-repo-config string Specify a yaml file acting as KUBETESTREPO_LIST, overriding registries for test images. -h, --help help for push --kubeconfig Kubeconfig Path to explicit kubeconfig file. --kubernetes-version string Use default E2E image, but override the version. Default is 'auto', which will be set to your cluster's version if detected, erroring otherwise. 'ignore' will try version resolution but ignore errors. 'latest' will find the latest dev image/version upstream. -p, --plugin strings Describe which plugin's images to interact with (Valid plugins are 'e2e', 'systemd-logs'). (default [e2e,systemd-logs]) ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Manage images used in a plugin to facilitate running them in airgapped (or similar) environments. Supported plugins are: 'e2e'
Project: ClickHouse (App Definition and Development / Database)
File: v23.11.3.23-stable.md

sidebar_position: 1 sidebar_label: 2023 Fix invalid memory access in BLAKE3 (Rust) (). Normalize function names in CREATE INDEX (). Fix handling of unavailable replicas before first request happened (). Revert "Fix bug window functions: revert " (). Backported in :. (). Remove heavy rust stable toolchain (). Fix docker image for integration tests (fixes CI) (). Always use `pread` for reading cache segments ().
Project: ArangoDB (App Definition and Development / Database)
File: copy_assignment.md

+++ title = "`basicresult &operator=(const basicresult &)`" description = "Copy assignment. Constexpr, triviality and noexcept propagating." categories = ["operators", "assignment", "copy-assignment"] weight = 140 +++ Copy assignment. Requires: that `valuetype` and `errortype` both implement copy assignment. Complexity: If the `valuetype` for both is present, uses `valuetype`'s copy assignment operator, else either destructs or copy constructs `valuetype` as appropriate. `errortype`'s copy assignment operator is always used. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the object is left in a partially completed state, as per the normal rules for the same operation on a `struct`.
Project: YugabyteDB (App Definition and Development / Database)
File: append.md

title: APPEND linkTitle: APPEND description: APPEND menu: preview: parent: api-yedis weight: 2010 aliases: /preview/api/redis/append /preview/api/yedis/append type: docs `APPEND key string_value` This command appends a value to the end of the string that is associated with the given `key`. If the `key` already exists, the given `string_value` is appended to the end of the string value that is associated with the `key`. If the `key` does not exist, it is created and associated with an empty string. If the `key` is associated with a non-string value, an error is raised. Returns the length of the resulted string after appending. ```sh $ GET yugakey ``` ``` "Yuga" ``` ```sh $ APPEND yugakey "Byte" ``` ``` 8 ``` ```sh $ GET yugakey ``` ``` "Yugabyte" ``` , , , , , , ,
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_import_foreign_schema.md

title: IMPORT FOREIGN SCHEMA statement [YSQL] headerTitle: IMPORT FOREIGN SCHEMA linkTitle: IMPORT FOREIGN SCHEMA description: Use the IMPORT FOREIGN SCHEMA statement to import tables from a foreign schema. menu: v2.18: identifier: ddlimportforeign_schema parent: statements type: docs Use the `IMPORT FOREIGN SCHEMA` command to create foreign tables that represent tables in a foreign schema on a foreign server. The newly created foreign tables are owned by the user who issued the command. By default, all the tables in the foreign schema are imported. However, the user can specify which tables to import using the `LIMIT TO` and `EXCEPT` clauses. To use this command, the user must have `USAGE` privileges on the foreign server, and `CREATE` privileges on the target schema. {{%ebnf%}} importforeignschema {{%/ebnf%}} Create foreign tables (in local_schema) that represent tables in a foreign schema named remote_schema located on a foreign server named server_name. The `LIMIT TO` clause can be optionally used to specify which tables to import. All other tables will be ignored. The `EXCEPT` clause can be optionally used to specify which tables to not import. All other tables will be ignored.
Project: ManageIQ (Provisioning / Automation & Configuration)
File: CONTRIBUTING.md

Please read the before contributing. The guides contain our Ruby coding standards as well as general standards around commits, pull requests, and more. If you wish to contribute a translation of the project in your language, please read before contributing. Thanks for your contribution! All contributions to ManageIQ are licensed under the Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0.html). See for more details.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: cpp-flag.md

Set additional flags to pass to the C Preprocessor cpp(1). Containerfiles ending with a ".in" suffix is preprocessed via cpp(1). This option can be used to pass additional flags to cpp.Note: You can also set default CPPFLAGS by setting the BUILDAHCPPFLAGS environment variable (e.g., export BUILDAHCPPFLAGS="-DDEBUG").
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.136.md

layout: release date: 2023-09-07 tag: v0.6.136 Aggregate events by status. @MUzairS15 (#8669) Aabidsofi/k8s switcher @aabidsofi19 (#8663) K8s context switcher ping redirected notify to useNotification. @ShailikaS (#8681) Standard Toolbar and flexible Mui Data-tables @sudhanshutech (#8618) [UI] Connections: Status | #8657 @senali-d (#8660) Aabidsofi/k8s switcher @aabidsofi19 (#8663) K8s context switcher ping redirected notify to useNotification. @ShailikaS (#8681) [UI] Connections: Status | #8657 @senali-d (#8660) Bump github.com/cyphar/filepath-securejoin from 0.2.3 to 0.2.4 @dependabot (#8684) Email will not be sent without any failure @VaibhavMalik4187 (#8665) [CI] Fix for failing meshkit error utility workflow @suhail34 (#8659) [Docs] Logical Concepts: workspaces, env, designs @leecalcote (#8679) Leecalcote/docs/mesh @leecalcote (#8678) Thank you to our contributors for making this release possible: @MUzairS15, @ShailikaS, @VaibhavMalik4187, @aabidsofi19, @dependabot, @dependabot[bot], @leecalcote, @senali-d, @sudhanshutech, @suhail34, @theBeginner86 and l5io
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: CLI-001-cli-and-runtime-versioning.md

Accepted As we formally establish Dapr component version, we need to decide if we want to couple CLI versions with runtime versions. We'll keep CLI versioning and runtime versioning separate. CLI will pull down latest runtime binary during the init()* command. Version scheme is: major.minor.revision.build* for both CLI and runtime. This allows us each Dapr component to evolve independently.
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: resource-crds.md

The CustomResourceDefinition API resource allows you to define custom resources. Defining a CRD object creates a new custom resource with a name and schema that you specify. The Kubernetes API serves and handles the storage of your custom resource. . Monokle Desktop uses CRDs to recognize the Custom Resources that you're creating. All CRDs that registered in Monokle and installed on the cluster are visible on Cluster Definition section on Cluster Dashboard By default, any Custom Resource that does not have a CRD registered in Monokle Desktop, will show up in the Navigator under the "Unknown Resources" section. After registering a CRD, Monokle Desktop will do the following: Validate Custom Resources based on the schema provided by the CRD. Generate Form Editors based on the CRD schema. Enable Cluster interactions on the Custom Resources. There are 2 ways: Load the objects from a Cluster. Monokle Desktop will scan the resources and, if it finds a CRD, it will register it so it can later recognize the Custom Resources. Use the CRDs Schema panel from the Validation tab. This panel lists all the CRDs that are already registered in Monokle Desktop and you can register new CRDs by providing a URL pointing to YAML content.