cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: SCHEMA.md

title: "Schema Patterns" <!-- 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. --> The samples on this page describe common patterns using Schemas. Schemas provide us a type-system for Beam records that is independent of any specific programming-language type. There might be multiple Java classes that all have the same schema (for example a Protocol-Buffer class or a POJO class), and Beam will allow us to seamlessly convert between these types. Schemas also provide a simple way to reason about types across different programming-language APIs. For more information, see the . {{< language-switcher java >}} Beam supports equijoins on schema `PCollections` of Schemas where the join condition depends on the equality of a subset of fields. Consider using if you have multiple collections that provide information about related things, and their structure is known. For example let's say we have two different collections with user data: one collection contains names and email addresses; the other collection contains names and phone numbers. We can join the two collections using the name as a common key and the other data as the associated values. After the join, we have one collection that contains all the information (email address and phone numbers) associated with each name. The following conceptual example uses two input collections to show the mechanism of . First, we define Schemas and User data. {{< highlight java >}} {{< code_sample "examples/java/src/test/java/org/apache/beam/examples/snippets/SnippetsTest.java" SchemaJoinPatternCreate >}} {{< /highlight >}} Then we create the `Pcollections` for user data and perform join on the two `PCollections` using a . {{< highlight java >}} {{< code_sample "examples/java/src/main/java/org/apache/beam/examples/snippets/Snippets.java" SchemaJoinPatternJoin >}} {{< /highlight >}} The result `Row` is of the type `Row: [Row(emailSchema), Row(phoneSchema)]`, and it can be converted to desired format as shown in the code snippet below. {{< highlight java >}} {{< code_sample "examples/java/src/main/java/org/apache/beam/examples/snippets/Snippets.java" SchemaJoinPatternFormat >}} {{< /highlight >}}
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-machine-inspect.1.md

% podman-machine-inspect 1 podman\-machine\-inspect - Inspect one or more virtual machines podman machine inspect [options] [name] ... Inspect one or more virtual machines Obtain greater detail about Podman virtual machines. More than one virtual machine can be inspected at once. The default machine name is `podman-machine-default`. If a machine name is not specified as an argument, then `podman-machine-default` will be inspected. Rootless only. Print results with a Go template. | Placeholder | Description | | - | | | .ConfigDir ... | Machine configuration directory location | | .ConnectionInfo ... | Machine connection information | | .Created ... | Machine creation time (string, ISO3601) | | .LastUp ... | Time when machine was last booted | | .Name | Name of the machine | | .Resources ... | Resources used by the machine | | .Rootful | Whether the machine prefers rootful or rootless container execution | | .Rosetta | Whether this machine uses Rosetta | | .SSHConfig ... | SSH configuration info for communicating with machine | | .State | Machine state | | .UserModeNetworking | Whether this machine uses user-mode networking | Print usage statement. Inspect the specified Podman machine. ``` $ podman machine inspect podman-machine-default ``` , April 2022, Originally compiled by Brent Baude <bbaude@redhat.com>
Project: Harbor (Provisioning / Container Registry)
File: 2-31-admin-role-view-project.md

Test 2-31 - Admin Role View Projects (DB Mode) ======= To verify that a user with system admin role can view all projects when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least two non-admin users are in Harbor. NOTE: The below non-admin user M should NOT be the same as the non-admin user in Test 2-21. Assign an non-admin user M with system admin role and act as an admin user. Repeat all steps in Test 2-21. A user with system admin role can perform all operations the same as the admin user. Same as Test 2-21. None
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-object-keys.md

title: jsonbobjectkeys() and jsonobjectkeys() [JSON] headerTitle: jsonbobjectkeys() and jsonobjectkeys() linkTitle: jsonbobjectkeys() description: Transform the list of key names in the supplied JSON object into a set (that is, table) of text values. menu: v2.18: identifier: jsonb-object-keys parent: json-functions-operators weight: 160 type: docs Purpose: Transform the list of key names in the supplied JSON object into a set (that is, table) of `text` values. Signature For the `jsonb` variant: ``` input value: jsonb return value: SETOF text ``` Notes: Each function in this pair requires that the supplied JSON value is an object. The returned keys are ordered alphabetically. ```plpgsql do $body$ declare object constant jsonb := '{"b": 1, "c": true, "a": {"p":1, "q": 2}}'; keys text[] := null; expected_keys constant text[] := array['a', 'b', 'c']; k text; n int := 0; begin for k in ( select jsonbobjectkeys(object) ) loop n := n + 1; keys[n] := k; end loop; assert keys = expected_keys, 'unexpected'; end; $body$; ```
Project: ClickHouse (App Definition and Development / Database)
File: odbc.md

slug: /en/sql-reference/table-functions/odbc sidebar_position: 150 sidebar_label: odbc Returns table that is connected via . ``` sql odbc(connectionsettings, externaldatabase, external_table) ``` Parameters: `connection_settings` Name of the section with connection settings in the `odbc.ini` file. `external_database` Name of a database in an external DBMS. `externaltable` Name of a table in the `externaldatabase`. To safely implement ODBC connections, ClickHouse uses a separate program `clickhouse-odbc-bridge`. If the ODBC driver is loaded directly from `clickhouse-server`, driver problems can crash the ClickHouse server. ClickHouse automatically starts `clickhouse-odbc-bridge` when it is required. The ODBC bridge program is installed from the same package as the `clickhouse-server`. The fields with the `NULL` values from the external table are converted into the default values for the base data type. For example, if a remote MySQL table field has the `INT NULL` type it is converted to 0 (the default value for ClickHouse `Int32` data type). Getting data from the local MySQL installation via ODBC This example is checked for Ubuntu Linux 18.04 and MySQL server 5.7. Ensure that unixODBC and MySQL Connector are installed. By default (if installed from packages), ClickHouse starts as user `clickhouse`. Thus you need to create and configure this user in the MySQL server. ``` bash $ sudo mysql ``` ``` sql mysql> CREATE USER 'clickhouse'@'localhost' IDENTIFIED BY 'clickhouse'; mysql> GRANT ALL PRIVILEGES ON . TO 'clickhouse'@'clickhouse' WITH GRANT OPTION; ``` Then configure the connection in `/etc/odbc.ini`. ``` bash $ cat /etc/odbc.ini [mysqlconn] DRIVER = /usr/local/lib/libmyodbc5w.so SERVER = 127.0.0.1 PORT = 3306 DATABASE = test USERNAME = clickhouse PASSWORD = clickhouse ``` You can check the connection using the `isql` utility from the unixODBC installation. ``` bash $ isql -v mysqlconn +-+ | Connected! | | | ... ``` Table in MySQL: ``` text mysql> CREATE TABLE `test`.`test` ( -> `intid` INT NOT NULL AUTOINCREMENT, -> `int_nullable` INT NULL DEFAULT NULL, -> `float` FLOAT NOT NULL, -> `float_nullable` FLOAT NULL DEFAULT NULL, -> PRIMARY KEY (`int_id`)); Query OK, 0 rows affected (0,09 sec) mysql> insert into test (`int_id`, `float`) VALUES (1,2); Query OK, 1 row affected (0,00 sec) mysql> select * from test; ++-+--+-+ | intid | intnullable | float | float_nullable | ++-+--+-+ | 1 | NULL | 2 | NULL | ++-+--+-+ 1 row in set (0,00 sec) ``` Retrieving data from the MySQL table in ClickHouse: ``` sql SELECT * FROM odbc('DSN=mysqlconn', 'test', 'test') ``` ``` text intidintnullablefloatfloat_nullable 1 0 2 0 ``` .
Project: YugabyteDB (App Definition and Development / Database)
File: explicit-locking.md

title: Explicit locking headerTitle: Explicit locking linkTitle: Explicit locking description: Explicit locking in YugabyteDB. headcontent: Row locking in YugabyteDB menu: v2.18: identifier: explore-transactions-explicit-locking-1-ysql parent: explore-transactions weight: 245 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../explicit-locking/" class="nav-link active"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> </ul> YugabyteDB's YSQL supports explicit row-level locking, similar to PostgreSQL. Explicit row-locks ensure that two transactions can never hold conflicting locks on the same row. When two transactions try to acquire conflicting lock modes, the semantics are dictated by YugabyteDB's policies. The following types of row locks are supported: `FOR UPDATE` `FOR NO KEY UPDATE` `FOR SHARE` `FOR KEY SHARE` The following example uses the `FOR UPDATE` row lock with the concurrency control policy. First, a row is selected for update, thereby locking it, and subsequently updated. A concurrent transaction should not be able to abort this transaction by updating the value of that row after the row is locked. {{% explore-setup-single %}} Create an sample table and populate it with sample data, as follows: ```sql yugabyte=# CREATE TABLE t (k VARCHAR, v VARCHAR); yugabyte=# INSERT INTO t VALUES ('k1', 'v1'); ``` Next, connect to the universe using two independent `ysqlsh` instances. You can connect both session `ysqlsh` instances to the same server or to different servers. Begin a transaction in the first session and perform a `SELECT FOR UPDATE` on the row in the table `t`. This locks the row for an update as a part of a transaction that has a very high priority (that is, in the `high priority bucket`, as explained in ): ```sql yugabyte=# BEGIN TRANSACTION ISOLATION LEVEL REPEATABLE READ; ``` ```output BEGIN ``` ```sql yugabyte=# SELECT * from t WHERE k='k1' FOR UPDATE; ``` ```output k | v -+- k1 | v1 (1 row) ``` Before completing the transaction, try to update the same key in your other session using a basic update statement, as follows: ```sql yugabyte=# UPDATE t SET v='v1.1' WHERE k='k1'; ``` ```output ERROR: All transparent retries exhausted. Operation failed. Try again: bb3aace4-5de2-41f9-981e-d9ca06671419 Conflicts with higher priority transaction: d4dadbf8-ca81-4bbd-b68c-067023f8ee6b ``` This operation fails because it conflicts with the row-level lock and as per `Fail-on-Conflict` concurrency control policy, the transaction aborts itself because it has a lower priority. Note that the error message appears after all have been exhausted. Finally, in the first session, update the row and commit the transaction, as follows: ```sql yugabyte=# UPDATE t SET v='v1.2' WHERE k='k1'; ``` ```output UPDATE 1 ``` ```sql yugabyte=# COMMIT; ``` ```output COMMIT ``` This should succeed.
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-300.md

Dynamic configuration is an important feature in the production environment, the Pulsar supports this feature, see `ServiceConfiguration.java`, when the field has `@FieldContext(dynamic = true)` means it is a dynamic configuration, and then we can use the `pulsar-admin` to update this field. The Pulsar has multiple pluggable plugins like authentication provider, authorization provider, and so on. In the plugin, we can get the Pulsar configurations and customized configurations, in some scenarios, we need to use the `pulsar-admin` to change the values of customized configuration, but the Pulsar doesn't support this operation. The goal of this PIP is to allow the `pulsar-admin` to update the values of customized configuration, and also use the listener to listen the customized configuration changes by `org.apache.pulsar.broker.service.BrokerService.registerConfigurationListener`. The `org.apache.pulsar.broker.service.BrokerService.dynamicConfigurationMap` holds the dynamic configurations, so we just to add the configurations that need to be dynamically configured to this map, and then we can use the `pulsar-admin` to update the values of these configurations. Users can only register custom configurations and only once. If multiple registrations are performed, an exception will be thrown. Add `void registerCustomDynamicConfiguration(String key, Predicate<String> validator)` to the `BrokerService.java`, ```java public void registerCustomDynamicConfiguration(String key, Predicate<String> validator) { if (dynamicConfigurationMap.containsKey(key)) { throw new IllegalArgumentException(key + " already exists in the dynamicConfigurationMap"); } ConfigField configField = ConfigField.newCustomConfigField(null); configField.validator = validator; dynamicConfigurationMap.put(key, configField); } ``` Example of using this feature in the plugin: ```java @Override public void initialize(PulsarService pulsarService) throws Exception { String myAuthIdKey = "my-auth-id"; myAuthIdValue = pulsarService.getConfiguration().getProperties().getProperty(myAuthIdKey); pulsarService.getBrokerService().registerCustomDynamicConfiguration(myAuthIdKey, null); pulsarService.getBrokerService().registerConfigurationListener(myAuthIdKey, (newValue) -> { // The `myAuthIdKey` value has changed myAuthIdValue = String.valueOf(newValue); }); } ``` Mailing List discussion thread: https://lists.apache.org/thread/ysnsnollgy1b6w1dsvmx1t1y2rz1tyd6 Mailing List voting thread: https://lists.apache.org/thread/cp4zdlz60md775ptzxbbj8bs2n2osfjb PR: https://github.com/apache/pulsar/pull/20884
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.18.md

RabbitMQ `3.10.18` is a maintenance release in the `3.10.x` . This series . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.3 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 and 24 versions older than 24.3 have reached . This release of RabbitMQ requires Erlang 24.3 or later versions. Nodes will fail to start on older Erlang releases. Erlang 25 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Reset and manually added nodes could start receiving stream replica data before its database was initialized, confusing all code paths that expected a blank node state. GitHub issue: Nodes could run into an exception with certain publishers that used QPid for client library. GitHub issue: `rabbitmqctl setpermissionsglobally` is a new command that sets up user permissions in all existing virtual hosts. GitHub issue: `rabbitmq-diagnostics cluster_status` now lists how many CPU cores are available to individual nodes, plus a total. GitHub issue: MQTT nodes did not correctly remove client IDs for clients connected to a node that was in the process of being removed from the cluster. GitHub issue: Due to a `$` sign escaping differences between Make and Bazel (the newly adopted build tool), default value of of `userdnpattern` setting was incorrect (had an extra `$`). GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.18.tar.xz` instead of the source tarball produced by GitHub.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.73.md

layout: release date: 2023-04-07 tag: v0.6.73 Refactor search on Meshmodels @Revolyssup (#7471) Use MeshModel interface for conversion of application to design-file @Abhishek-kumar09 (#7488) Add instructions for renewal of playground certificates @Revolyssup (#7492) Fix 500 error on Dry Run by handling unhandled errors @Revolyssup (#7489) Add documentation for setting up websocket in playground @Revolyssup (#7490) [relationship] nodes and namespaces could accept components from any model @Abhishek-kumar09 (#7485) [chore] fix remote provider api @theBeginner86 (#7486) Fix hyperlinks in Documentation Framework @goldfishdolphin (#7483) Changes in README.md @ShivangShandilya (#7461) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Revolyssup, @ShivangShandilya, @goldfishdolphin, @leecalcote and @theBeginner86
Project: ThreatMapper (Provisioning / Security & Compliance)
File: requirements.md

title: System Requirements The Management Console may be installed on a single Docker host or in a dedicated Kubernetes cluster: A Docker Host is suitable for small-scale deployments, managing up to several hundred production nodes A Kubernetes Cluster is suitable for small and large-scale deployments | Feature | Requirements (Docker) | Requirements (Kubernetes) | |-||-| | CPU: No of cores | 8 cores | 3 nodes, 4 cores each | | RAM | 16 GB | 3 nodes, 8 GB each | | Telemetry and data from Deepfence Sensors | Port 443 (configurable), firewalled | Port 443 (configurable), firewalled | | Administrative and API access | Port 443 (configurable), firewalled | Port 443 (configurable), firewalled | | Docker | *Version 20.10.18 (minimum version 18.06.0) | | Larger deployments, managing 250 or more production nodes, will require additional CPU and RAM resources. For enterprise-scale deployments, managing 1000+ production nodes, the ThreatMapper Console should be deployed on a Kubernetes cluster of 3 or more nodes.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.13-en.md

Add `limiter` update API . Avoid creating temporary zip files when syncing data directory during cluster startup . Refactor: move `/mqtt/systopics` to generic `/configs/systopics` . Refactor: use `POST` not `PUT` for `/users/{name}/change_pwd` . Add compression functions `zip`, `gzip`, `zip_compress` in Rule-Engine and corresponding decompression functions . Return `204` instead of `200` for `PUT /authenticator/:id` . Added the option to customize the clientid prefix of egress MQTT bridges. Ensure the default expiration time of `banned` is large enough . Trigger `message.dropped` hook when QoS2 message is resend by client with a same packet id, or 'awaiting_rel' queue is full . Fix shared subscription 'sticky' strategy . Prior to this change, a 'sticky' subscriber may continue to receive messages after unsubscribing. Add check to ensure that a given key is among the prepared statements on query in the mysql connector . Fix password leak to logs for connectors .
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thanks for sending a pull request! Here are some tips for you: Consider creating this PR as draft: https://github.com/kubevirt/kubevirt/blob/main/CONTRIBUTING.md#consider-opening-your-pull-request-as-draft Follow the instructions for writing a release note from k8s: https://git.k8s.io/community/contributors/guide/release-notes.md --> Before this PR: After this PR: <!-- (optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: --> Fixes # The following tradeoffs were made: The following alternatives were considered: Links to places where the discussion took place: <!-- optional: slack, other GH issue, mailinglist, ... --> <!-- optional --> This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR. Approvers are expected to review this list. was considered and is present (link) or not required [ ] PR: The PR description is expressive enough and will help future contributors and [ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required . New features and bug fixes require at least on e2e test was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change. was considered <!-- Write your release note: Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". If no release note is required, just write "NONE". --> ```release-note ```
Project: StarRocks (App Definition and Development / Database)
File: SET.md

displayed_sidebar: "English" Sets the specified system variables or user-defined variables for StarRocks. You can view the system variables of StarRocks using . For details about system variables, see . For details about user-defined variables, see . :::tip This operation does not require privileges. ::: ```SQL SET [ GLOBAL | SESSION ] <variablename> = <value> [, <variablename> = <value>] ... ``` | Parameter | Description | | - | | | Modifier:<ul><li>GLOBAL</li><li>SESSION</li></ul> | <ul><li>With a `GLOBAL` modifier, the statement sets the variables globally.</li><li>With a `SESSION` modifier, the statement sets the variables within the session. `LOCAL` is a synonym for `SESSION`.</li><li>If no modifier is present, the default is `SESSION`.</li></ul>For details about global and session variables, see .<br/>NOTE<br/>Only users with the ADMIN privilege can set the variables globally. | | variable_name | The name of the variable. | | value | The value of the variable. | Example 1: Set the `time_zone` to `Asia/Shanghai` within the session. ```Plain mysql> SET time_zone = "Asia/Shanghai"; Query OK, 0 rows affected (0.00 sec) ``` Example 2: Set the `execmemlimit` to `2147483648` globally. ```Plain mysql> SET GLOBAL execmemlimit = 2147483648; Query OK, 0 rows affected (0.00 sec) ``` Example 3: Set multiple global variables. Add the `GLOBAL` keyword before each variable. ```Plain mysql> SET GLOBAL execmemlimit = 2147483648, GLOBAL time_zone = "Asia/Shanghai"; Query OK, 0 rows affected (0.00 sec) ```