cwielenb/CNCF-Dataset huggingface dataset:
Project: StarRocks (App Definition and Development / Database)
File: arrow-function.md

displayed_sidebar: "English" Queries an element that can be located by the `json_path` expression in a JSON object and returns a JSON value. The arrow function `->` is more compact and easier to use than the function. ```Haskell jsonobjectexpr -> json_path ``` `jsonobjectexpr`: the expression that represents the JSON object. The object can be a JSON column, or a JSON object that is produced by a JSON constructor function such as PARSE_JSON. `json_path`: the expression that represents the path to an element in the JSON object. The value of this parameter is a string. For information about the JSON path syntax that is supported by StarRocks, see . Returns a JSON value. If the element does not exist, the arrow function returns an SQL value of `NULL`. Example 1: Query an element that can be located by the `'$.a.b'` expression in the specified JSON object. ```plaintext mysql> SELECT parse_json('{"a": {"b": 1}}') -> '$.a.b'; -> 1 ``` Example 2: Use nested arrow functions to query an element. The arrow function in which another arrow function is nested queries an element based on the result that is returned by the nested arrow function. In this example, the root element $ is omitted from the `json_path` expression. ```plaintext mysql> SELECT parse_json('{"a": {"b": 1}}')->'a'->'b'; -> 1 ``` Example 3: Query an element that can be located by the `'a'` expression in the specified JSON object. In this example, the root element $ is omitted from the `json_path` expression. ```plaintext mysql> SELECT parse_json('{"a": "b"}') -> 'a'; -> "b" ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_grant-role.md

title: kbcli cluster grant-role Grant role to account ``` kbcli cluster grant-role [flags] ``` ``` kbcli cluster grant-role CLUSTERNAME --component COMPNAME --name USERNAME --role ROLENAME kbcli cluster grant-role CLUSTERNAME --name USERNAME --role ROLENAME kbcli cluster grant-role --instance INSTANCE --name USERNAME --role ROLENAME ``` ``` --component string Specify the name of component to be connected. If not specified, pick the first one. -h, --help help for grant-role -i, --instance string Specify the name of instance to be connected. --name string Required user name, please specify it. -r, --role string Role name should be one of [SUPERUSER, READWRITE, READONLY]. ``` ``` --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 ``` - Cluster command.
Project: StarRocks (App Definition and Development / Database)
File: str2date.md

displayed_sidebar: "English" Converts a string into a DATE value according to the specified format. If the conversion fails, NULL is returned. The format must be consistent with that described in . This function is equivalent to but has a different return type. ```Haskell DATE str2date(VARCHAR str, VARCHAR format); ``` `str`: the time expression you want to convert. It must be of the VARCHAR type. `format`: the format used to return the value. For the supported format, see . Returns a value of the DATE type. NULL is returned if `str` or `format` is NULL. ```Plain select str2date('2010-11-30 23:59:59', '%Y-%m-%d %H:%i:%s'); ++ | str2date('2010-11-30 23:59:59', '%Y-%m-%d %H:%i:%s') | ++ | 2010-11-30 | ++ 1 row in set (0.01 sec) ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: enable-ssl-self-signed.md

If you need to use an `https:` URL for local testing (i.e. if an OAuth provider requires a "secure" callback URL), you can use a self-signed certificate by following these steps. Generate a self-signed certificate and key for localhost and configure your system to trust it. The application is a helpful tool to accomplish this. Update `backend.baseUrl` in app-config.local.yaml to use an `https:` address. Add the certificate and key to `backend.https.certificate.cert` and `backend.https.certificate.cert`, respectively. ```yaml backend: baseUrl: https://localhost:7007 https: certificate: cert: | --BEGIN CERTIFICATE-- MIIDCTCCAfGgAwIBAgIUZ9VhZckcy690L ... --END CERTIFICATE-- key: $file: ./certs/localhost-key.pem ``` Start the backend with `NODEEXTRACA_CERTS=/absolute/path/to/cert.pem yarn start-backend` As with the backend instructions above, a trusted certificate and key are needed. Update `app.baseUrl` and `backend.cors.origin` in app-config.local.yaml to use an `https:` address. Add the certificate and key to `app.https.certificate.cert` and `app.https.certificate.cert`, respectively. ```yaml app: baseUrl: https://localhost:3000 https: certificate: cert: $file: ./certs/localhost.pem key: $file: ./certs/localhost-key.pem backend: cors: origin: https://localhost:3000 ``` and start the app with `yarn start`. Depending on what plugins are in use, you may need to override additional URLs to use `https` for those endpoints to work.
Project: LinuxKit (Provisioning / Automation & Configuration)
File: 2017-04-09.md

The fifth weekly development report. Feel free to send PRs if you want to add to these reports (or correct them). Ilya @errordeveloper (Weave) has started working on . This also fits with the that Rolf is working on. The aim is to do both a desktop version and later a full production quality deployment with high availability. Dave @dave-tucker is working on CI, and the . Welcome everyone, looking forward to your contributions and working with you. Please open issues on github if you need help, or ask on #moby in the . Ian @ijc25 added a project, that incorporates his to run swarmkit standalone using just `containerd` rather than Docker. There were updates to okernel and miragesdk. We added a roadmap for the . Landlock is an eBPF based Linux Security Module being developed by @l0kod which promises to be an excellent match for containers. This was a busy week, with a lot of refactoring and rebasing. The `moby run` command got backend support for GCP from @dave-tucker and qemu from @thebsdbox . We stopped using the `riddler` tool and added a direct conversion from the yaml config to OCI for running system contaniners. More config options were added, and there is now . We stopped using some of the previous names to standardise on names closer to the underlying OCI field names, from @justincormack. @riyazdf added support for content trust settings in the yaml file and set up signing for the kernel, which will be rolled out to other images. @shykes suggested some section renames which we implemented, the initial containers that run once are now "onboot" and the long running ones are "services", which is much clearer. The `init` section was converted to a list, so `runc` and `containerd` can easily be updated independently. The issues with shared mounts, and allowing containers to mount on the host were hopefully all resolved in . switch to using `containerd` finally arm64 prototypes documentation preparation for Dockercon, finalizing demos there will be a talk by @justincormack on Moby (currently billed as containerd...) there will be a Docker Security talk with @riyazdf (`Secure Substrate: Least Privilege Container Deployment`) that will highlight Moby both these talks will have some time for demos there will be a session and lots of time to talk at the Thursday summit - get in touch if you need an invite. Please add topics you would like to talk about to via PR.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: install-kubeblocks-with-kbcli.md

title: Install KubeBlocks with kbcli description: Install KubeBlocks on the existing Kubernetes clusters keywords: [taints, affinity, tolerance, install, kbcli, KubeBlocks] sidebar_position: 3 sidebar_label: Install KubeBlocks The quickest way to try out KubeBlocks is to create a new Kubernetes cluster and install KubeBlocks using the playground. However, production environments are more complex, with applications running in different namespaces and with resource or permission limitations. This document explains how to deploy KubeBlocks on an existing Kubernetes cluster. Prepare an accessible Kubernetes cluster with the version 1.22 or above, and this cluster should meet the following requirements. <table> <tr> <th colspan="3">Resource Requirements</th> </tr > <tr> <td >Control Plane</td> <td colspan="2">It is recommended to create 1 node with 4 cores, 4GB memory and 50GB storage. </td> </tr > <tr > <td rowspan="4">Data Plane</td> <td> MySQL </td> <td>It is recommended to create at least 3 nodes with 2 cores, 4GB memory and 50GB storage. </td> </tr> <tr> <td> PostgreSQL </td> <td>It is recommended to create at least 2 nodes with 2 cores, 4GB memory and 50GB storage. </td> </tr> <tr> <td> Redis </td> <td>It is recommended to create at least 2 nodes with 2 cores, 4GB memory and 50GB storage. </td> </tr> <tr> <td> MongoDB </td> <td>It is recommended to create at least 3 nodes with 2 cores, 4GB memory and 50GB storage. </td> </tr> </table> The command `kbcli kubeblocks install` installs KubeBlocks in the `kb-system` namespace, or you can use the `--namespace` flag to specify one. ```bash kbcli kubeblocks install ``` If you want to install KubeBlocks with a specified version, follow the steps below. View the available versions. ```bash kbcli kubeblocks list-versions ``` Or you can view the available versions in . Specify a version with `--version` and run the command below. ```bash kbcli kubeblocks install --version=x.x.x ``` :::note By default, kbcli installs the latest release version and then when installing KubeBlocks, kbcli installs the matched version. Ensure that the major versions of kbcli and KubeBlocks match. For instance, you can install kbcli v0.6.1 and KubeBlocks v0.6.3, but mismatched versions like kbcli v0.5.0 and KubeBlocks v0.6.0 may result in errors. ::: Run the following command to check whether KubeBlocks is installed successfully. ```bash kbcli kubeblocks status ``` *Result* If the KubeBlocks Workloads are all ready, KubeBlocks has been installed successfully. ```bash KubeBlocks is deployed in namespace: kb-system,version: x.x.x KubeBlocks Workloads: NAMESPACE KIND NAME READY PODS CPU(CORES) MEMORY(BYTES) CREATED-AT kb-system Deployment kb-addon-snapshot-controller 1/1 N/A N/A Oct 13,2023 14:27 UTC+0800 kb-system Deployment kubeblocks 1/1 N/A N/A Oct 13,2023 14:26 UTC+0800 kb-system Deployment kubeblocks-dataprotection 1/1 N/A N/A Oct 13,2023 14:26 UTC+0800 ```
Project: CloudTTY (App Definition and Development / Application Definition & Image Build)
File: local-cluster-generate-kubeconfig.md

short-desc: Genetate kubeconfig for local cluster title: Genetate Kubeconfig For Local Cluster authors: "@calvin0327" reviewers: "@panpan0000" approvers: "" creation-date: 2022-06-16 last-updated: 2022-06-17 * * This document proposes a mechanism to generate kubeconfig by serviceaccount while we want to create a cloudshell to manage clusters deployed with cloudshell-operator. If we want to create a cloud shell for cluster that the `cloudshell-operator` is depoly on it. this is what we called local cluster. it's not friendly for users to generate kubeconfig and mount to pod of cloudshell manually. all actions can be done by `cloudshell-operator` for users. It can help users to generate kubeconfig automatically and mount it to pod of cloudshell, it's normal to use kubectl command to operate the local cluster. The user corresponding to kubeconfig has `admin` privileges. User can not support configmap info to field `spec.configmap` of cloudshell cr. If this field is empty and we assume that the user want to create cloudshell in the local cluster. `cloudshell-operator` will complete the following steps: We need to use operator ServiceAccount to generate kubeconfig, so operator needs to have sufficient permissions. ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: cloudtty-controller-manager rules: apiGroups: '*' resources: '*' verbs: '*' ``` Inside the cluster, use ServiceAccount to generate kubeconfig, load the `caData` and `token` under directory `/var/run/secrets/kubernetes.io/serviceaccount`. `Server` consists of the KUBERNETESSERVICEHOST and KUBERNETESSERVICEPORT environment variables. ```yaml apiVersion: v1 clusters: cluster: certificate-authority-data: {{ .CAData }} server: {{ .Server }} name: kubernetes contexts: context: cluster: kubernetes user: cloudtty-controller-manager name: cloudtty-controller-manager@kubernetes current-context: cloudtty-controller-manager@kubernetes kind: Config users: name: cloudtty-controller-manager user: token: {{ .Token }} ``` We will restore kubeconfig to configmap in the same namespace with cloudshell, and mount the configmap to pod of job and backfill configMap name to Cloudshell.
Project: CockroachDB (App Definition and Development / Database)
File: citations.md

This file contains citations for papers that contain the relational identities upon which the transformation rules are based. Some rules contain a "Citations" line which references one or more entries in this list of citations, in which further information, and in some cases proofs, can be found. [1] Galindo-Legaria, C.A. & Rosenthal, Arnon. (1997). Outerjoin Simplification and Reordering for Query Optimization. ACM Trans. Database Syst.. 22. 43-73. 10.1145/244810.244812. https://www.researchgate.net/publication/220225172OuterjoinSimplificationandReorderingforQuery_Optimization [2] M. M. Joshi and C. A. Galindo-Legaria. Properties of the GroupBy/Aggregate relational operator. Technical report, Microsoft, 2001. MSR-TR-2001-13. [3] Galindo-Legaria, C.A. & Joshi, Milind. (2001). Orthogonal Optimization of Subqueries and Aggregation. Sigmod Record. 30. 571-581. 10.1145/375663.375748. http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.563.8492&rep=rep1&type=pdf [4] Galindo-Legaria, C.A.. (2001). Parameterized queries and nesting equivalences. https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/tr-2000-31.pdf [5] Elhemali, Mostafa & Galindo-Legaria, C.A. & Grabs, Torsten & M. Joshi, Milind. (2007). Execution strategies for SQL subqueries. 993-1004. 10.1145/1247480.1247598. https://www.researchgate.net/profile/MostafaElhemali/publication/221213885ExecutionstrategiesforSQLsubqueries/links/584f631308aecb6bd8d02aa4/Execution-strategies-for-SQL-subqueries.pdf [6] Simmen, David & Shekita, Eugene & Malkemus, Timothy. (1996). Fundamental Techniques for Order Optimization. Sigmod Record. Volume 25 Issue 2, June 1996. Pages 57-67. https://cs.uwaterloo.ca/~gweddell/cs798/p57-simmen.pdf [7] Ahmed, Rafi & W. Lee, Allison & Witkowski, Andrew & Das, Dinesh & Su, Hong & Zat, Mohamed & Cruanes, Thierry. (2006). Cost-Based Query Transformation in Oracle.. 1026-1036. https://www.researchgate.net/publication/221311318Cost-BasedQueryTransformationin_Oracle z [8] Moerkotte, Guido & Fender, Pit & Eich, Marius. (2013). On the correct and complete enumeration of the core search space. Proceedings of the ACM SIGMOD International Conference on Management of Data. 493-504. 10.1145/2463676.2465314. https://www.researchgate.net/publication/262216932Onthecorrectandcompleteenumerationofthecoresearch_space [9] Denis Hirn and Torsten Grust. (2021). One WITH RECURSIVE is Worth Many GOTOs. In Proceedings of the 2021 International Conference on Management of Data (SIGMOD '21). Association for Computing Machinery, New York, NY, USA, 723735. https://doi.org/10.1145/3448016.3457272
Project: GraphScope (App Definition and Development / Database)
File: neo4j_eco.md

is a graph database management system that utilizes graph natively to store and process data. Unlike traditional relational databases that rely on relational schemas, Neo4j leverages the power of interconnected nodes and relationships, forming a highly flexible and expressive data model. GIE implements Neo4j's HTTP and TCP protocol so that the system can seamlessly interact with the Neo4j ecosystem, including development tools such as and . The following documentations will guide you through empowering the Neo4j ecosystem with GIE's distributed capability for large-scale graph. ```{toctree} arguments caption: GIE For Tinkerpop Ecosystem maxdepth: 2 neo4j/cypher_sdk neo4j/supported_cypher neo4j/llm_assistant ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.35.md

RabbitMQ `3.8.35` is a maintenance release. All users are recommended to upgrade to this release. RabbitMQ releases are distributed via , , and . This release and . explains what package repositories and tools can be used to provision modern Erlang versions. See the for general documentation on upgrades and for release notes of other releases. If upgrading from a `3.7.x` release, see upgrade and compatibility notes first. If upgrading from a `3.6.x` or older , first upgrade to and then to this version. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . Consul peer discovery now supports client-side TLS options, much like its Kubernetes and etcd peers. ``` ini cluster_formation.consul.scheme = https cluster_formation.consul.port = 8501 clusterformation.consul.ssloptions.cacertfile = /path/to/consul/generated/ca_certificate.pem clusterformation.consul.ssloptions.certfile = /path/to/client/certificate.pem clusterformation.consul.ssloptions.keyfile = /path/to/client/client_key.pem ``` GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.35.tar.xz` instead of the source tarball produced by GitHub.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: shm-size-systemd.md

Size of systemd-specific tmpfs mounts such as /run, /run/lock, /var/log/journal and /tmp. A unit can be b (bytes), k (kibibytes), m (mebibytes), or g (gibibytes). If the unit is omitted, the system uses bytes. If the size is omitted, the default is 64m. When size is 0, the usage is limited to 50% of the host's available memory.
Project: ClickHouse (App Definition and Development / Database)
File: merge_tree_settings.md

slug: /en/operations/system-tables/mergetreesettings title: mergetreesettings Contains information about settings for `MergeTree` tables. Columns: `name` () Setting name. `value` () Setting value. `changed` () Whether the setting was explicitly defined in the config or explicitly changed. `description` () Setting description. `min` (()) Minimum value of the setting, if any is set via . If the setting has no minimum value, contains . `max` (()) Maximum value of the setting, if any is set via . If the setting has no maximum value, contains . `readonly` () Shows whether the current user can change the setting: `0` Current user can change the setting. `1` Current user cant change the setting. `type` () Setting type (implementation specific string value). `is_obsolete` () - Shows whether a setting is obsolete. Example ```sql SELECT * FROM system.mergetreesettings LIMIT 4 FORMAT Vertical; ``` ```response Row 1: name: mincompressblock_size value: 0 changed: 0 description: When granule is written, compress the data in buffer if the size of pending uncompressed data is larger or equal than the specified threshold. If this setting is not set, the corresponding global setting is used. min: max: readonly: 0 type: UInt64 is_obsolete: 0 Row 2: name: maxcompressblock_size value: 0 changed: 0 description: Compress the pending uncompressed data in buffer if its size is larger or equal than the specified threshold. Block of data will be compressed even if the current granule is not finished. If this setting is not set, the corresponding global setting is used. min: max: readonly: 0 type: UInt64 is_obsolete: 0 Row 3: name: index_granularity value: 8192 changed: 0 description: How many rows correspond to one primary key value. min: max: readonly: 0 type: UInt64 is_obsolete: 0 Row 4: name: maxdigestionsizepersegment value: 268435456 changed: 0 description: Max number of bytes to digest per segment to build GIN index. min: max: readonly: 0 type: UInt64 is_obsolete: 0 4 rows in set. Elapsed: 0.009 sec. ```