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

<!-- 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. --> To solve this challenge, you may build a pipeline that consists of the following steps: {{if (eq .Sdk "go")}} Add windowing `slidingWindowedItems := beam.WindowInto(s, window.NewSlidingWindows(5time.Second, 10time.Second), input)` `max := getMax(s, slidingWindowedItems)` `func getMax(s beam.Scope, input beam.PCollection) beam.PCollection { return stats.Max(s, input) }` {{end}} {{if (eq .Sdk "java")}} Add sliding windowing `rideTotalAmounts.apply( Window.<Double>into(SlidingWindows.of(Duration.standardSeconds(10)).every(Duration.standardSeconds(5))))` Write SerializableFunction which define max value: `.apply(Combine.globally((SerializableFunction<Iterable<Double>, Double>) input -> { Iterator<Double> iterator = input.iterator(); double firstValue = iterator.hasNext() ? iterator.next() : : -Double.MAX_VALUE; for (double i : input){ if(firstValue<i){ firstValue = i; } } return firstValue; }).withoutDefaults());` {{if (eq .Sdk "python")}} Add window `'window' >> beam.WindowInto(window.SlidingWindows(10, 5))` Define max value:`'Sum above cost' >> beam.CombineGlobally(max).without_defaults()`
Project: StarRocks (App Definition and Development / Database)
File: bitmap_to_binary.md

displayed_sidebar: "English" Converts Bitmap values to a Binary string. bitmaptobinary is mainly used for exporting Bitmap data. The compression effect is better than . If you plan to export data directly to a binary file such as Parquet, this function is recommended. This function is supported from v3.0. ```Haskell VARBINARY bitmaptobinary(BITMAP bitmap) ``` `bitmap`: the Bitmap to convert, required. If the input value is invalid, an error is returned. Returns a value of the VARBINARY type. Example 1: Use this function with other bitmap functions. ```Plain mysql> select hex(bitmaptobinary(bitmapfromstring("0, 1, 2, 3"))); ++ | hex(bitmaptobinary(bitmapfromstring('0, 1, 2, 3'))) | ++ | 023A3000000100000000000300100000000000010002000300 | ++ 1 row in set (0.01 sec) mysql> select hex(bitmaptobinary(to_bitmap(1))); +-+ | hex(bitmaptobinary(to_bitmap(1))) | +-+ | 0101000000 | +-+ 1 row in set (0.01 sec) mysql> select hex(bitmaptobinary(bitmap_empty())); ++ | hex(bitmaptobinary(bitmap_empty())) | ++ | 00 | ++ 1 row in set (0.01 sec) ``` Example 2: Convert each value in a BITMAP column into a binary string. Create an Aggregate table `pageuv` where the `AGGREGATE KEY` is (`pageid`, `visitdate`). This table contains a BITMAP column `visitusers` whose values are to be aggregated. ```SQL CREATE TABLE `page_uv` (`page_id` INT NOT NULL, `visit_date` datetime NOT NULL, `visitusers` BITMAP BITMAPUNION NOT NULL ) ENGINE=OLAP AGGREGATE KEY(`pageid`, `visitdate`) DISTRIBUTED BY HASH(`page_id`) PROPERTIES ( "replication_num" = "3", "storage_format" = "DEFAULT" ); ``` Insert data into this table. ```SQL insert into page_uv values (1, '2020-06-23 01:30:30', to_bitmap(13)), (1, '2020-06-23 01:30:30', to_bitmap(23)), (1, '2020-06-23 01:30:30', to_bitmap(33)), (1, '2020-06-23 02:30:30', to_bitmap(13)), (2, '2020-06-23 01:30:30', to_bitmap(23)); select * from pageuv order by pageid; +++-+ | pageid | visitdate | visit_users | +++-+ | 1 | 2020-06-23 01:30:30 | NULL | | 1 | 2020-06-23 02:30:30 | NULL | | 2 | 2020-06-23 01:30:30 | NULL | +++-+ ``` Convert each value in the `visit_users` column into a binary-encoded string. ```Plain mysql> select pageid, hex(bitmaptobinary(visitusers)) from page_uv; +++ | pageid | hex(bitmaptobinary(visitusers)) | +++ | 1 | 0A030000000D0000000000000017000000000000002100000000000000 | | 1 | 010D000000 | | 2 | 0117000000 | +++ 3 rows in set (0.01 sec) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.6.md

layout: release date: 2020-9-3 tag: v0.4.6 General fixed bug for kuma adaptor @kumarabd (#1523) Docs/nupurthakur27/966 @NupurThakur27 (#1517) Kumarabd/bug/smi chip @kumarabd (#1520) ADDED SMI CONFORMANCE FEATURE @was-coder (#1518) feat: close drawer after clear all notification @PmcFizz (#1515) Features feat: Add pre-commit hook for lint @kushthedude (#1107)
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-prometheusservice-controller.md

layout: integration title: AWS Managed Service for Prometheus subtitle: Collaborative and visual infrastructure as code for AWS Managed Service for Prometheus image: /assets/img/integrations/aws-prometheusservice-controller/icons/color/aws-prometheusservice-controller-color.svg permalink: extensibility/integrations/aws-prometheusservice-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-prometheusservice-controller description: integrations-category: Observability and Analysis integrations-subcategory: Metrics registrant: GitHub components: name: field-export colorIcon: assets/img/integrations/aws-prometheusservice-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-prometheusservice-controller/components/field-export/icons/white/field-export-white.svg description: name: adopted-resource colorIcon: assets/img/integrations/aws-prometheusservice-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-prometheusservice-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: name: alert-manager-definition colorIcon: assets/img/integrations/aws-prometheusservice-controller/components/alert-manager-definition/icons/color/alert-manager-definition-color.svg whiteIcon: assets/img/integrations/aws-prometheusservice-controller/components/alert-manager-definition/icons/white/alert-manager-definition-white.svg description: name: workspace colorIcon: assets/img/integrations/aws-prometheusservice-controller/components/workspace/icons/color/workspace-color.svg whiteIcon: assets/img/integrations/aws-prometheusservice-controller/components/workspace/icons/white/workspace-white.svg description: name: logging-configuration colorIcon: assets/img/integrations/aws-prometheusservice-controller/components/logging-configuration/icons/color/logging-configuration-color.svg whiteIcon: assets/img/integrations/aws-prometheusservice-controller/components/logging-configuration/icons/white/logging-configuration-white.svg description: name: rule-groups-namespace colorIcon: assets/img/integrations/aws-prometheusservice-controller/components/rule-groups-namespace/icons/color/rule-groups-namespace-color.svg whiteIcon: assets/img/integrations/aws-prometheusservice-controller/components/rule-groups-namespace/icons/white/rule-groups-namespace-white.svg description: featureList: [ "No collection agents required", "Amazon Managed Service for Prometheus includes a remote write-compatible API that can ingest metrics from OpenTelemetry, Prometheus libraries, and existing Prometheus servers.", "Amazon Managed Service for Prometheus includes a query-compatible HTTP API that allows you to query metrics, metric labels, metric metadata, and time series metrics. " ] 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: ClickHouse (App Definition and Development / Database)
File: CONTRIBUTING.md

ClickHouse is an open project, and you can contribute to it in many ways. You can help with ideas, code, or documentation. We appreciate any efforts that help us to make the project better. Thank you! When you open your first pull-request to ClickHouse repo, a bot will invite you to accept ClickHouse Individual CLA (Contributor License Agreement). It is a simple few click process. For subsequent pull-requests the bot will check if you have already signed it and won't bother you again. Optionally, to make contributions even more tight legally, your employer as a legal entity may want to sign a ClickHouse Corporate CLA with ClickHouse, Inc. If you're interested to do so, contact us at . We have a for writing code for ClickHouse. Besides this guide, you can find and instructions on how to build ClickHouse in different environments. If you want to contribute to documentation, read the guide.
Project: ClickHouse (App Definition and Development / Database)
File: v23.9.5.29-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : In the setup plan started to appear in the logs. It should be only in the `runnergetall_tests.log` only. As well, send the failed infrastructure event to CI db. (). Backported in : Do not fetch changed submodules in the builder container. (). Select from system tables when table based on table function. (). Fix incomplete query result for UNION in view() function. (). Fix crash in case of adding a column with type Object(JSON) (). Fix segfault during Kerberos initialization (). Fix: RabbitMQ OpenSSL dynamic loading issue (). Fix crash in GCD codec in case when zeros present in data (). Fix crash in FPC codec (). Backported in :. (). Improve enrich image (). Rewrite jobs to use callable workflow (). Continue rewriting workflows to reusable tests (). Better exception messages ().
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_bench_delete.md

title: kbcli bench delete Delete a benchmark. ``` kbcli bench delete [flags] ``` ``` kbcli bench delete mybench ``` ``` -h, --help help for delete ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Run a benchmark.
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: state-managers-local-fs.md

id: version-0.20.0-incubating-state-managers-local-fs title: Local File System sidebar_label: Local File System original_id: state-managers-local-fs <!-- 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. --> Heron can use the local file system as a state manager for storing various book keeping information. Use of local file system is recommended mainly for single node server and laptop. This configuration is ideal for deploying in edge devices. Heron developers can use this setting for developing and debugging various heron components in their laptop or server. You can make Heron aware of the ZooKeeper cluster by modifying the `statemgr.yaml` config file specific for the Heron cluster. You'll need to specify the following for each cluster: `heron.class.state.manager` Indicates the class to be loaded for local file system state manager. You should set this to `org.apache.heron.statemgr.localfs.LocalFileSystemStateManager` `heron.statemgr.connection.string` This should be `LOCALMODE` since it always localhost. `heron.statemgr.root.path` The root path in the local file system where state information is stored. We recommend providing Heron with an exclusive directory; if you do not, make sure that the following sub-directories are unused: `/tmanagers`, `/topologies`, `/pplans`, `/executionstate`, `/schedulers`. `heron.statemgr.localfs.is.initialize.file.tree` Indicates whether the nodes under root `/tmanagers`, `/topologies`, `/pplans`, `/executionstate`, and `/schedulers` need to created, if they are not found. Set it to `True`, if you could like Heron to create those directories. If those directories are already there, set it to `False`. The absence of this configuration implies `True`. Below is an example configuration (in `statemgr.yaml`) for a local file system running in `localhost`: ```yaml heron.class.state.manager: org.apache.heron.statemgr.localfs.LocalFileSystemStateManager heron.statemgr.connection.string: LOCALMODE heron.statemgr.root.path: ${HOME}/.herondata/repository/state/${CLUSTER} heron.statemgr.localfs.is.initialize.file.tree: True ```
Project: ShardingSphere (App Definition and Development / Database)
File: rules.en.md

+++ title = "Rules" weight = 3 +++ This section explains how to configure the ShardingSphere-Proxy rules. Rules configuration for ShardingSphere-Proxy is the same as ShardingSphere-JDBC. For details, please refer to . Unlike ShardingSphere-JDBC, the following rules need to be configured in ShardingSphere-Proxy's `global.yaml`: ```yaml sqlParser: sqlStatementCache: initialCapacity: 2000 maximumSize: 65535 parseTreeCache: initialCapacity: 128 maximumSize: 1024 ``` ```yaml transaction: defaultType: XA providerType: Atomikos ``` ```yaml sqlTranslator: type: useOriginalSQLWhenTranslatingFailed: ``` ```yaml sqlFederation: sqlFederationEnabled: true allQueryUseSQLFederation: false executionPlanCache: initialCapacity: 2000 maximumSize: 65535 ```
Project: secureCodeBox (Provisioning / Security & Compliance)
File: adr_0005.md

title: "ADR-0005: Buying separate marketing oriented webpage" sidebar_label: "ADR-0005" | <!-- --> | <!-- --> | |-|--| | Status: | DEPRECATED | | Date: | 2020-09-29 | | Author(s): | Daniel Patanin , Sven Strittmatter | :::info Deprecated since we did some optimizations by marketing specialists some months ago. ::: As our requirements about our homepage changed we no longer just want to give a simple overview about our project on our landing page as we did with our GatsbyJS based website, but furthermore we require a marketing oriented webpage additionally to our documentation site (for more on that see ). This marketing page should satisfy following aspects: Modern, ideally timeless, design Overview about the secureCodeBox Display of our projects advantages Offer for service (prizing) Encouragement for contacting us Encouragement for contributing Since there is no arguable reason to build such a one-pager ourselves, we should buy a ready to go solution for us. We are not aiming to invest extensive time neither in building such a page, nor in gaining the desired design and marketing expertise, and also not hiring experts on this field (all this would actually be more expensive and time consuming than buying a site). Some stores for such pages are: If we want to change the style or design someday, we probably could not reuse the bought template if it is not a minor change, thus would need to buy another template. We also would have to orient the presentation of the secureCodeBox around the template we decide on, but nowadays we have a ginormous variety to choose from.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: CHANGELOG-v2020.11.12.md

title: Changelog | KubeDB description: Changelog menu: docs_{{.version}}: identifier: changelog-kubedb-v2020.11.12 name: Changelog-v2020.11.12 parent: welcome weight: 20201112 product_name: kubedb menuname: docs{{.version}} sectionmenuid: welcome url: /docs/{{.version}}/welcome/changelog-v2020.11.12/ aliases: /docs/{{.version}}/CHANGELOG-v2020.11.12/ Prepare for release v0.2.1 (#97) Set default resource requests = 1/2 * limits (#653) Fix serviceTemplate inline json (#652) Add MariaDB patch util Add MariaDB constants (#651) Prepare for release v0.15.1 (#551) Update KubeDB api (#550) Prepare for release v0.15.1 (#416) Update KubeDB api (#415) Prepare for release v0.15.1 (#205) Update NOTE.txt with helm 3 command (#203) Prepare for release v0.8.1 (#245) Update KubeDB api (#244) Prepare for release v0.8.1 (#320) Update KubeDB api (#319) Prepare for release v0.8.1 (#307) Update KubeDB api (#306) Prepare for release v0.15.1 (#351) Update KubeDB api (#350) Prepare for release v0.2.1 (#140) Update KubeDB api (#139) Update README.md Prepare for release v0.2.1 (#110) Update KubeDB api (#109) Prepare for release v0.15.1 (#426) Update KubeDB api (#425) Prepare for release v0.2.1 (#122) Update KubeDB api (#121) Prepare for release v0.8.1 (#264) Update KubeDB api (#263) Prepare for release v0.2.1 (#94) Update KubeDB api (#93)
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Configuration.md

title: Configuration layout: documentation documentation: true Storm has a variety of configurations for tweaking the behavior of nimbus, supervisors, and running topologies. Some configurations are system configurations and cannot be modified on topology by topology basis, whereas other configurations can be modified per topology. Every configuration has a default value defined in in the Storm codebase. You can override these configurations by defining a storm.yaml in the classpath of Nimbus and the supervisors. Finally, you can define a topology-specific configuration that you submit along with your topology when using . However, the topology-specific configuration can only override configs prefixed with "TOPOLOGY". Storm 0.7.0 and onwards lets you override configuration on a per-bolt/per-spout basis. The only configurations that can be overridden this way are: "topology.debug" "topology.max.spout.pending" "topology.max.task.parallelism" "topology.kryo.register": This works a little bit differently than the other ones, since the serializations will be available to all components in the topology. More details on . The Java API lets you specify component specific configurations in two ways: Internally: Override `getComponentConfiguration` in any spout or bolt and return the component-specific configuration map. Externally: `setSpout` and `setBolt` in `TopologyBuilder` return an object with methods `addConfiguration` and `addConfigurations` that can be used to override the configurations for the component. The preference order for configuration values is defaults.yaml < storm.yaml < topology specific configuration < internal component specific configuration < external component specific configuration. In almost all cases configuration for a bolt or a spout should be done through setters on the bolt or spout implementation and not the topology conf. In some rare cases, it may make sense to expose topology wide configurations that are not currently a part of or such as when writing a custom scheduler or a plugin to some part of storm. In those cases you can create your own class like Config but implements . Any `public static final String` field declared in this class will be treated as a config and annotations from the `org.apache.storm.validation.ConfigValidationAnnotations` class can be used to enforce what is stored in that config. To let the validator know about this class you need to treat the class like a service that will be loaded through a ServiceLoader for the Validated class and include a `META-INF/services/org.apache.storm.validation.Validated` file in your jar that holds the name of your Config class. Resources: : a listing of client configurations as well as a helper class for creating topology specific configurations : a listing of Storm Daemon configurations. : the default values for all configurations : explains how to create and configure a Storm cluster : lists useful configurations when running topologies on a cluster : lists useful configurations when using local mode
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: os-feature.md

Set the name of a required operating system feature for the image which is built. By default, if the image is not based on scratch, the base image's required OS feature list is kept, if the base image specified any. This option is typically only meaningful when the image's OS is Windows. If feature has a trailing `-`, then the feature is removed from the set of required features which is listed in the image.
Project: YDB (App Definition and Development / Database)
File: basic_aggregation.md

Find out the number of unique episodes within every season of every series. {% include %} ```sql SELECT series_id, season_id, COUNT(*) AS cnt -- Aggregation function COUNT returns the number of rows -- output by the query. -- Asterisk (*) specifies that COUNT -- counts the total number of rows in the table. -- COUNT(*) returns the number of rows in -- the specified table, preserving the duplicate rows. -- It counts each row separately. -- The result includes rows that contain null values. FROM episodes GROUP BY series_id, -- The query result will follow the listed order of columns. season_id -- Multiple columns are separated by a comma. -- Other columns can be listed after a SELECT only if -- they are passed to an aggregate function. ORDER BY series_id, season_id ; COMMIT; ```