cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.9.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | ReduceTask.ValueIterator should apply job configuration to Configurable values | Major | . | Andrzej Bialecki | Andrzej Bialecki | | | Hadoop streaming does not work with gzipped input | Major | . | Hairong Kuang | Hairong Kuang |
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.71.md

layout: release date: 2023-04-03 tag: v0.6.71 Run component updater to set k8s components as published @Revolyssup (#7459) [MeshModels] Add Core Application component in MeshModel @Abhishek-kumar09 (#7432) feat: rjsf upgrade, error Schema at the object field Template @harkiratsm (#7453) Issue#7392 , Updated Prerequisites for meshery docs. @hirentimbadiya (#7456) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Revolyssup, @harkiratsm, @hirentimbadiya and @leecalcote
Project: Druid (App Definition and Development / Database)
File: feature.md

name: Feature/Change about: A template for Druid feature and change descriptions title: "" labels: Feature/Change Description assignees: '' Please describe the feature or change with as much detail as possible. If you have a detailed implementation in mind and wish to contribute that implementation yourself, and the change that you are planning would require a 'Design Review' tag because it introduces or changes some APIs, or it is large and imposes lasting consequences on the codebase, please open a Proposal instead. Please provide the following for the desired feature or change: A detailed description of the intended use case, if applicable Rationale for why the desired feature/change would be beneficial
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-emrcontainers-controller.md

layout: integration title: AWS EMR Containers subtitle: Collaborative and visual infrastructure as code for AWS EMR Containers image: /assets/img/integrations/aws-emrcontainers-controller/icons/color/aws-emrcontainers-controller-color.svg permalink: extensibility/integrations/aws-emrcontainers-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-emrcontainers-controller description: integrations-category: Analytics integrations-subcategory: Analytics registrant: GitHub components: name: virtual-cluster colorIcon: assets/img/integrations/aws-emrcontainers-controller/components/virtual-cluster/icons/color/virtual-cluster-color.svg whiteIcon: assets/img/integrations/aws-emrcontainers-controller/components/virtual-cluster/icons/white/virtual-cluster-white.svg description: name: job-run colorIcon: assets/img/integrations/aws-emrcontainers-controller/components/job-run/icons/color/job-run-color.svg whiteIcon: assets/img/integrations/aws-emrcontainers-controller/components/job-run/icons/white/job-run-white.svg description: name: adopted-resource colorIcon: assets/img/integrations/aws-emrcontainers-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-emrcontainers-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: name: field-export colorIcon: assets/img/integrations/aws-emrcontainers-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-emrcontainers-controller/components/field-export/icons/white/field-export-white.svg description: 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: KubeZoo (Provisioning / Automation & Configuration)
File: developer-guide.md

There's a `Makefile` in the root folder. Here are some common options: Build KubeZoo binary `kube-zoo` ```bash make build ``` Build for specific architecture. (`amd64`,`arm`,`arm64`) ```bash GOOS=linux GOARCH=arm64 make build ``` Build all docker images for all supported architectures. ```bash make release ``` Build all docker images for specific architecture. ```bash make release ARCH=arm64 ``` Build kubezoo-e2e-test binary to test KubeZoo. ```bash make e2e ```
Project: Meshery (Provisioning / Automation & Configuration)
File: meshery-ui_bug.md

name: Meshery UI Bug Report about: Report a bug in Meshery's UI title: '[UI]' labels: component/ui, language/javascript, framework/react, kind/bug assignees: '' <!-- A brief description of what the problem is. (e.g. I need to be able to...) --> <!-- A brief description of the enhancement. --> <!-- Add screenshots, if applicable, to help explain your problem. --> Browser: Chrome Safari Firefox Host OS: Mac Linux Windows Meshery Server Version: stable-v Meshery Client Version: stable-v Platform: Docker Kubernetes Wireframes and in Figma Questions: and
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.23.0.md

title: v1.23.0 weight: 998977000 In the `Dockerfile`, replace the line `FROM golang:1.17 as builder` with `FROM golang:1.18 as builder` See for more details. Update the Makefile targets by adding `test -s $(LOCALBIN)/<binary-name> ||` before the instruction to download them, see: ```sh KUSTOMIZEINSTALLSCRIPT ?= "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh" .PHONY: kustomize kustomize: $(KUSTOMIZE) ## Download kustomize locally if necessary. $(KUSTOMIZE): $(LOCALBIN) test -s $(LOCALBIN)/kustomize || { curl -s $(KUSTOMIZEINSTALLSCRIPT) | bash -s -- $(subst v,,$(KUSTOMIZE_VERSION)) $(LOCALBIN); } .PHONY: controller-gen controller-gen: $(CONTROLLER_GEN) ## Download controller-gen locally if necessary. $(CONTROLLER_GEN): $(LOCALBIN) test -s $(LOCALBIN)/controller-gen || GOBIN=$(LOCALBIN) go install sigs.k8s.io/controller-tools/cmd/controller-gen@$(CONTROLLERTOOLSVERSION) .PHONY: envtest envtest: $(ENVTEST) ## Download envtest-setup locally if necessary. $(ENVTEST): $(LOCALBIN) test -s $(LOCALBIN)/setup-envtest || GOBIN=$(LOCALBIN) go install sigs.k8s.io/controller-runtime/tools/setup-envtest@latest ``` See for more details. In the `Makefile` file, replace `CONTROLLERTOOLSVERSION ?= v0.9.0` with `CONTROLLERTOOLSVERSION ?= v0.9.2` See for more details. In the `go.mod` file, ensure the following dependencies versions and run `go mod tidy`: ```go k8s.io/api v0.24.2 k8s.io/apimachinery v0.24.2 k8s.io/client-go v0.24.2 sigs.k8s.io/controller-runtime v0.12.2 ``` See for more details. In the `config/default/managerauthproxy_patch.yaml` file, replace `gcr.io/kubebuilder/kube-rbac-proxy:0.11.0` with `gcr.io/kubebuilder/kube-rbac-proxy:0.13.0` See and for more details. Upgrade kustomize versions from `v3.8.7` to `v4.5.5` WARNING If your project has customizations using kustomize you might be impacted by them. See its . (Note all changes are covered by its docs) Update the kustomize version in your Makefile: ensure that the value used for `KUSTOMIZE_VERSION` is `v4.5.5` In the `config/default/kustomization.yaml` file: a) Replace: ```yaml ``` With: ```yaml ``` b) Replace: `bases:` With: `resources:` (Valid Only for Ansible Projects) In the molecule/default, replace `--load_restrictor none .` with `--load-restrictor LoadRestrictionsNone` See for more details.
Project: Stolon (App Definition and Development / Database)
File: pitr_wal-g.md

is the successor of wal-e, which no longer seems to be in active development! This example shows how to do point in time recovery with stolon using correctly suggests to not put environment variables containing secret data (like aws secret keys) inside the `archive_command` since every user connected to postgres could read them. In its examples wal-g suggests to use the `envdir` command to set the wal-g required environment variables or (since some distribution don't have it) just use a custom script that sets them. Take the base backups using the `wal-g backup-push` command. For doing this you should set at least the `archivemode` and the `archivecommand` pgParameters in the cluster spec. Wal-g will be used as the archive command: ``` stolonctl update --patch '{ "pgParameters" : { "archivemode": "on", "archivecommand": "envdir /etc/wal-g.d/env wal-g wal-push %p" } }' ``` Note: looks like wal-g doesn't backups various config files like `postgresql.conf`, `pghba.conf`. While `pghba.conf` is currently generated by stolon, you'd like to keep the previous postgres parameters after the restore. For doing this there're two different ways: if you want to backup the `postgresql.conf` you should do this outside `wal-g`. To restore it you have to create a `dataRestoreCommand` that will restore it after the `wal-g backup fetch` command. if you don't want to backup/restore it than you can just set all the `pgParameters` inside the ``` stolonctl init '{ "initMode": "pitr", "pitrConfig": { "dataRestoreCommand": "envdir /etc/wal-g.d/env wal-g backup-fetch %d LATEST" , "archiveRecoverySettings": { "restoreCommand": "envdir /etc/wal-g.d/env wal-g wal-fetch \"%f\" \"%p\"" } } }' ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.14.md

RabbitMQ `3.11.14` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . It is now possible to limit the maximum number of virtual hosts that can be created in the cluster. Contributed by @SimonUnge (AWS). GitHub issue: It is now possible to limit how many shovels or federation links can run on a node using `rabbitmq.conf`: ``` ini runtime_parameters.limits.shovel = 10 runtime_parameters.limits.federation = 10 ``` Contributed by @illotum (AWS). GitHub issue: Quorum queues will now log if they could not apply policy changes, for example, because there was no quorum of replicas online, or the queue was going through a leader election. GitHub issue: could fail to elect a single active consumer (SAC) in certain consumer churn conditions. GitHub issue: `rabbitmqctl updatevhostmetadata` is a new command that can be used to update the description, default queue type, or tags of a virtual host: ``` shell rabbitmqctl updatevhostmetadata vh1 --tags qa,quorum,team3,project2 rabbitmqctl updatevhostmetadata vh1 --description "QA env 1 for issue 37483" rabbitmqctl updatevhostmetadata vh1 --description "QQs all the way" --default-queue-type "quorum" rabbitmqctl updatevhostmetadata vh1 --description "streaming my brain out" --default-queue-type "stream" ``` GitHub issue: It was impossible to return to a tab that had a filter expression that was not a valid regular expressions. Now such expressions will be used as regular text filters. GitHub issue: Several variables (`{username}`, `{vhost}` and JWT claims that are single string values) now can be used (expanded) in topic operation authorization. GitHub issue: The authorization backend could run into an exception when used in combination with other backends. GitHub issue: was upgraded to `2.12.1` To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.14.tar.xz` instead of the source tarball produced by GitHub.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.25.0.md

implement mysql and mssql design by @Yunxe in https://github.com/Edgenesis/shifu/pull/673 @Yunxe made their first contribution in https://github.com/Edgenesis/shifu/pull/673 Bump go.uber.org/zap from 1.24.0 to 1.25.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/666 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.24.0...v0.25.0
Project: ClickHouse (App Definition and Development / Database)
File: cluster.md

slug: /en/sql-reference/table-functions/cluster sidebar_position: 30 sidebar_label: cluster title: "cluster, clusterAllReplicas" Allows to access all shards (configured in the `remote_servers` section) of a cluster without creating a table. Only one replica of each shard is queried. `clusterAllReplicas` function same as `cluster`, but all replicas are queried. Each replica in a cluster is used as a separate shard/connection. :::note All available clusters are listed in the table. ::: Syntax ``` sql cluster(['clustername', db.table, shardingkey]) cluster(['clustername', db, table, shardingkey]) clusterAllReplicas(['clustername', db.table, shardingkey]) clusterAllReplicas(['clustername', db, table, shardingkey]) ``` Arguments `cluster_name` Name of a cluster that is used to build a set of addresses and connection parameters to remote and local servers, set `default` if not specified. `db.table` or `db`, `table` - Name of a database and a table. `sharding_key` - A sharding key. Optional. Needs to be specified if the cluster has more than one shard. Returned value The dataset from clusters. Using Macros `cluster_name` can contain macros substitution in curly brackets. The substituted value is taken from the section of the server configuration file. Example: ```sql SELECT * FROM cluster('{cluster}', default.example_table); ``` Usage and Recommendations Using the `cluster` and `clusterAllReplicas` table functions are less efficient than creating a `Distributed` table because in this case, the server connection is re-established for every request. When processing a large number of queries, please always create the `Distributed` table ahead of time, and do not use the `cluster` and `clusterAllReplicas` table functions. The `cluster` and `clusterAllReplicas` table functions can be useful in the following cases: Accessing a specific cluster for data comparison, debugging, and testing. Queries to various ClickHouse clusters and replicas for research purposes. Infrequent distributed requests that are made manually. Connection settings like `host`, `port`, `user`, `password`, `compression`, `secure` are taken from `<remote_servers>` config section. See details in . See Also
Project: StarRocks (App Definition and Development / Database)
File: SHOW_TABLES.md

displayed_sidebar: "English" Displays all tables in a StarRocks database or a database in an external data source, for example, Hive, Iceberg, Hudi, or Delta Lake. NOTE To view tables in an external data source, you must have the USAGE privilege on the external catalog that corresponds to that data source. ```sql SHOW TABLES [FROM <catalogname>.<dbname>] ``` | Parameter | Required | Description | | -- | -- | | | catalogname | No | The name of the internal catalog or an external catalog.<ul><li>If you do not specify this parameter or set it to `defaultcatalog`, tables in StarRocks databases are returned.</li><li>If you set this parameter to the name of an external catalog, tables in databases of an external data source are returned.</li></ul> You can run to view internal and external catalogs.| | db_name | No | The database name. If not specified, the current database is used by default. | Example 1: View tables in database `exampledb` of the `defaultcatalog` after connecting to the StarRocks cluster. The following two statements are equivalent. ```plain show tables from example_db; +-+ | Tablesinexample_db | +-+ | depts | | depts_par | | emps | | emps2 | +-+ show tables from defaultcatalog.exampledb; +-+ | Tablesinexample_db | +-+ | depts | | depts_par | | emps | | emps2 | +-+ ``` Example 2: View tables in the current database `example_db` after connecting to this database. ```plain show tables; +-+ | Tablesinexample_db | +-+ | depts | | depts_par | | emps | | emps2 | +-+ ``` Example 2: View tables in database `hudidb` of the external catalog `hudicatalog`. ```plain show tables from hudicatalog.hudidb; +-+ | Tablesinhudi_db | +-+ | hudisyncmor | | hudi_table1 | +-+ ``` Alternatively, you can run SET CATALOG to switch to the external catalog `hudicatalog` and then run `SHOW TABLES FROM hudidb;`. : Views all catalogs in a StarRocks cluster. : Views all databases in the internal catalog or an external catalog. : Switches between catalogs.
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: sup_elections.md

+++ title = "Leader Elections" date = 2020-10-26T19:05:42-07:00 draft = false gh_repo = "habitat" [menu] [menu.habitat] title = "Leader Elections" identifier = "habitat/supervisors/Leader Elections" parent = "habitat/supervisors" weight = 40 +++ The Chef Habitat Supervisor performs leader election natively for service groups that require one, such as leader-follower. Because Chef Habitat is an eventually-consistent distributed system, the role of the leader is different than in strongly-consistent systems. It only serves as the leader for application level semantics, e.g. a database write leader. The fact that a Supervisor is a leader has no bearing upon other operations in the Chef Habitat system, including rumor dissemination for configuration updates. It is not akin to a leader, through which writes must all be funneled. This allows for very high scalability of the Chef Habitat Supervisor ring. Services grouped using a leader need to have a minimum of three supervisors in order to break ties. It is also strongly recommended that you do not run the service group with an even number of members. Otherwise, in the event of a network partition with equal members on each side, both sides will elect a new leader, causing a full split-brain from which the algorithm cannot recover. Supervisors in a service group will warn you if you are using leader election and have an even number of supervisors. When a service group starts in a leader topology, it will wait until there are sufficient members to form a quorum (at least three). At this point, an election cycle can happen. Each Supervisor injects an election rumor into ring, targeted at the service group, with the exact same rumor, which demands an election and insists that the peer itself is the leader. This algorithm is known as . Every peer that receives this rumor does a simple lexicographic comparison of its GUID with the GUID of the peer contained in that rumor. The winner is the peer whose GUID is higher. The peer then adds a vote for the GUID of the winner, and shares the rumor with others, including the total number of votes of anyone who previously voted for this winner. An election ends when a candidate peer X gets a rumor back from the ring saying that it (X) is the winner, with all members voting. At this point, it sends out a rumor saying it is the declared winner, and the election cycle ends. For more information about the Bully algorithm, see by Hctor Garca-Molina.
Project: YugabyteDB (App Definition and Development / Database)
File: show_stmt.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="192" height="65" viewbox="0 0 192 65"><path class="connector" d="M0 22h15m58 0h30m54 0h20m-89 0q5 0 5 5v20q0 5 5 5h5m42 0h17q5 0 5-5v-20q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="58" height="25" rx="7"/><text class="text" x="25" y="22">SHOW</text><a xlink:href="../../../syntaxresources/grammardiagrams#name"><rect class="rule" x="103" y="5" width="54" height="25"/><text class="text" x="113" y="22">name</text></a><rect class="literal" x="103" y="35" width="42" height="25" rx="7"/><text class="text" x="113" y="52">ALL</text><polygon points="188,29 192,29 192,15 188,15" style="fill:black;stroke-width:0"/></svg>
Project: VoltDB (App Definition and Development / Database)
File: MakeChanges.md

Here is information and links to help you plan for changes on a live system. Most schema changes can be made online using CREATE or ALTER commands via SQLCMD. Using VoltDB has an overview of this, . There are a few types of schema changes that require taking the database offline following the process from Administrator's Guide. This is required only for the following types of schema changes: Changing the partitioning of a table that is not empty Adding a unique index to a table that is not empty You can load, replace or delete stored procedure Java code using the "load/remove classes" directives in sqlcmd. For more information, see the the "Class management directives" section in the in Using VoltDB. You can change the configuration of the following settings by editing the deployment.xml file and uploading it using the following command: voltadmin update deployment.xml If you do not have a copy of the latest deployment.xml file that is used by your database, you can retrieve it using the following command: voltdb get deployment Allowable changes include the following (see the in Using VoltDB): Security settings, including user accounts Import and export settings (including add or remove configurations, or toggle enabled=true/false) Database replication settings (except the DR cluster ID) Automated snapshots System settings: Heartbeat timeout Query Timeout Resource Limit Disk Limit Resource Limit Memory Limit Otherwise, you need to apply the change using a maintenance window process which involves taking a snapshot and then using the `voltdb init` command to initialize a new database instance initialized with the modified deployment.xml file, after which you can restart and restore the snapshot. See in Administrator's Guide. Specifically, you need to use this process to change: temp table limit paths ports command logging configuration any cluster attributes (e.g. K safety or sites per host). enable/disable HTTP interface
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.82.md

layout: release date: 2023-04-19 tag: v0.6.82 Add provider env variable in helm chart values.yaml @Revolyssup (#7570) Fixed issue #7533 @Freedisch (#7566) Adapter dud Platform detection fix & Error handling improvement @Azanul (#7564) include arrays in sorting when we encounter allOf, AnyOf, Allof @harkiratsm (#7574) fix: anyof, allof, schema sorting, captilization, uiSchema @harkiratsm (#7559) Update deprecated property "scrollFullHeight" from MUI Datables responsive options @MdSahil-oss (#7560) fix: undeploy later button @Udit-takkar (#7558) [UI/Server] Adapter deploy and undeploy switcher for docker host @Azanul (#7378) Updated EventStreamHandler for REST API docs @acald-creator (#7548) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Azanul, @Chadha93, @Freedisch, @MdSahil-oss, @Revolyssup, @Udit-takkar, @acald-creator, @harkiratsm and @leecalcote