Prostore

https://prostore.datamart.ru/docs_prostore
Admin
Prostore is a core software for data marts, enabling efficient data loading, reading,...
Tokens:1,946,969
Snippets:33,638
Trust Score:5.6
Update:1 year ago
Show doc for...
Tokens:
Raw
### Build and Install Kafka-Postgres Connector

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-6-1/getting_started/getting_started

This sequence of commands guides the user through cloning the `kafka-postgres-connector` repository, building it using Apache Maven, and preparing its configuration files. The `mvn clean install -DskipTests=true` command compiles and packages the connector, skipping tests for faster build. The final step emphasizes aligning the connector's configuration with the Prostore application's settings.

```Bash
# клонирование репозитория kafka-postgres-connector
git clone https://repository.datamart.ru/datamarts/kafka-postgres-connector ~/kafka-postgres-connector
# запуск сборки коннектора kafka-postgres средствами Apache Maven
cd ~/kafka-postgres-connector
mvn clean install -DskipTests=true
# приведение конфигурационных файлов kafka-postgres-writer и kafka-postgres-reader к виду,
# показанному ниже, чтобы значения параметров совпадали со значениями соответствующих параметров конфигурации Prostore
```

--------------------------------

### Build and Install Kafka-Postgres Connector

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-8/getting_started/getting_started

Instructions to clone the Kafka-Postgres connector repository from 'repository.datamart.ru' and build it using Apache Maven. The 'mvn clean install -DskipTests=true' command compiles the project and installs it into the local Maven repository, skipping tests.

```bash
# клонирование репозитория kafka-postgres-connector
git clone https://repository.datamart.ru/datamarts/kafka-postgres-connector ~/kafka-postgres-connector
# запуск сборки коннектора kafka-postgres средствами Apache Maven
cd ~/kafka-postgres-connector
mvn clean install -DskipTests=true
```

--------------------------------

### Build and Install Kafka-Postgres Connector

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-4/getting_started/getting_started

This section provides instructions to clone the `kafka-postgres-connector` repository, navigate into it, and build the connector using Apache Maven, skipping tests. It also mentions the need to adjust connector configuration files to match Prostore's settings.

```Bash
# клонирование репозитория kafka-postgres-connector
git clone https://github.com/datamarts/kafka-postgres-connector ~/kafka-postgres-connector
# запуск сборки коннектора kafka-postgres средствами Apache Maven
cd ~/kafka-postgres-connector
mvn clean install -DskipTests=true
# приведение конфигурационных файлов kafka-postgres-writer и kafka-postgres-reader к виду,
# показанному ниже, чтобы значения параметров совпадали со значениями соответствующих параметров конфигурации Prostore
```

--------------------------------

### Build and Install Kafka-Postgres Connector

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-10/deployment/getting_started/deployment_with_kafka/deployment_with_kafka

Steps to clone the kafka-postgres-connector repository from Datamart and build it using Apache Maven. The build process skips tests to expedite the installation, preparing the connector for deployment within the Prostore environment.

```bash
git clone https://repository.datamart.ru/datamarts/kafka-postgres-connector ~/kafka-postgres-connector
cd ~/kafka-postgres-connector
mvn clean install -DskipTests=true
```

--------------------------------

### PostgreSQL Database Setup for Prostore

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-4/getting_started/getting_started

These commands guide the setup of a PostgreSQL database for Prostore. It involves creating a superuser role with specified credentials (matching `adp:datasource:user` and `adp:datasource:password` in Prostore config), creating a database named 'test' (matching `env:name`), and reloading the PostgreSQL service to apply changes.

```Bash
# создание в СУБД Postgres SUPERUSER-пользователя c именем и паролем,
# указанными в конфигурации Prostore
# (значения параметров (adp:datasource:user) и (adp:datasource:password) соответственно)
cd /
sudo -u postgres psql -c 'CREATE ROLE dtm WITH LOGIN SUPERUSER'
sudo -u postgres psql -c "ALTER ROLE dtm WITH PASSWORD 'dtm'"
# создание базы данных с именем test, указанным в конфигурации Prostore (env: name)
sudo -u postgres psql -c 'CREATE DATABASE test'
# перезапуск сервиса Postgresql
sudo systemctl reload postgresql-13
```

--------------------------------

### Example CURL Request for Prostore /health/startup Endpoint

Source: https://prostore.datamart.ru/docs_prostore/_archive/v7-0/http_api/health/startup

A command-line example demonstrating how to make a GET request to the Prostore `/actuator/health/startup` endpoint using CURL to check the node's startup status.

```shell
curl -X 'GET' \
  'http://localhost:8080/actuator/health/startup'
```

--------------------------------

### Example Async Operation Start Response

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-12-2/http_api/openapi_spec/openapi_spec

This snippet shows a partial example of a response indicating the successful start of an asynchronous operation, including a unique request ID and a confirmation message.

```APIDOC
                  - name: name
                    type: VARCHAR
                    size: -1
                    nullable: true
                rows: 0
                statistics:
                  elapsedTotalMs: 34
                  elapsedDbMs: 20
            async:
              value:
                requestId: 2f8b7a67-a17e-4f71-a0f0-22249c005d5c
                message: Async operation started
      headers:
        x-request-id:
          $ref: '#/components/headers/x-request-id-required'
```

--------------------------------

### PostgreSQL Database Setup for Prostore

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-8/getting_started/getting_started

Commands to configure a PostgreSQL database for use with Prostore. This includes creating a SUPERUSER role with specified username and password (matching 'adp:datasource:user' and 'adp:datasource:password' in Prostore configuration), creating a database with the name specified in 'env: name' (e.g., 'test'), and reloading the PostgreSQL service.

```bash
# создание в СУБД Postgres SUPERUSER-пользователя c именем и паролем,
# указанными в конфигурации Prostore
# (значения параметров (adp:datasource:user) и (adp:datasource:password) соответственно)
cd /
sudo -u postgres psql -c 'CREATE ROLE dtm WITH LOGIN SUPERUSER'
sudo -u postgres psql -c "ALTER ROLE dtm WITH PASSWORD 'dtm'"
# создание базы данных с именем test, указанным в конфигурации Prostore (env: name)
sudo -u postgres psql -c 'CREATE DATABASE test'
# перезапуск сервиса Postgresql
sudo systemctl reload postgresql-13
```

--------------------------------

### Build and Install Kafka-Postgres Connector

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-2/getting_started/getting_started

This script outlines the steps to clone, build, and prepare the Kafka-Postgres connector. It involves cloning the repository from GitHub, navigating into the directory, and building the project using Apache Maven, skipping tests. The final step mentions configuring the `kafka-postgres-writer` and `kafka-postgres-reader` files to align with Prostore's configuration parameters.

```bash
# клонирование репозитория kafka-postgres-connector
git clone https://github.com/arenadata/kafka-postgres-connector ~/kafka-postgres-connector
# запуск сборки коннектора kafka-postgres средствами Apache Maven
cd ~/kafka-postgres-connector
mvn clean install -DskipTests=true
# приведение конфигурационных файлов kafka-postgres-writer и kafka-postgres-reader к виду,
# показанному ниже, чтобы значения параметров совпадали со значениями соответствующих параметров конфигурации Prostore
```

--------------------------------

### Build and Install Kafka-Postgres Connector

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-7/getting_started/getting_started

This snippet outlines the steps to build and install the Kafka-Postgres connector. It involves cloning the connector's Git repository, navigating into the directory, and then building the project using Apache Maven, skipping tests.

```bash
# клонирование репозитория kafka-postgres-connector
git clone https://repository.datamart.ru/datamarts/kafka-postgres-connector ~/kafka-postgres-connector
# запуск сборки коннектора kafka-postgres средствами Apache Maven
cd ~/kafka-postgres-connector
mvn clean install -DskipTests=true
```

--------------------------------

### Configure PostgreSQL Database for Prostore

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-10/deployment/getting_started/deployment_with_kafka/deployment_with_kafka

Commands to create a SUPERUSER role and a database in PostgreSQL, using credentials and database name specified in the Prostore configuration. This snippet also includes a command to reload the PostgreSQL service to apply changes.

```bash
cd /
sudo -u postgres psql -c 'CREATE ROLE dtm WITH LOGIN SUPERUSER'
sudo -u postgres psql -c "ALTER ROLE dtm WITH PASSWORD 'dtm'"
sudo -u postgres psql -c 'CREATE DATABASE test'
sudo systemctl reload postgresql-13
```

--------------------------------

### Prostore Application YAML Configuration

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-4/getting_started/getting_started

This YAML configuration file (`application.yml`) defines various parameters for the Prostore system, including logging levels, server ports, metrics exposure, active plugins, HTTP settings, environment name, state restoration, materialized view synchronization, metrics, data source configurations (EDML, Zookeeper), Kafka settings (producer, cluster, admin, status events, monitor), Vert.x thread pool sizes, cache settings, and delta rollback. It also includes specific configurations for the ADP (Analytic Data Platform) component, such as database connection details, MPP Writer, and MPP Reader URLs.

```YAML
logging:
  level:
    ru.datamart.prostore.query.execution: ${DTM_LOGGING_LEVEL:TRACE}

server:
  port: ${DTM_METRICS_PORT:8080}

management:
  endpoints:
    enabled-by-default: ${DTM_METRICS_ENABLED:true}
    web:
      exposure:
        include: ${DTM_METRICS_SCOPE:info, health, requests}

core:
  plugins:
    active: ${CORE_PLUGINS_ACTIVE:ADP}

  http:
    port: ${DTM_CORE_HTTP_PORT:9090}
    tcpNoDelay: ${DTM_CORE_HTTP_TCP_NO_DELAY:true}
    tcpFastOpen: ${DTM_CORE_HTTP_TCP_FAST_OPEN:true}
    tcpQuickAck: ${DTM_CORE_HTTP_TCP_QUICK_ACK:true}

  env:
    name: ${DTM_NAME:test}

  restoration:
    autoRestoreState: ${AUTO_RESTORE_STATE:true}

  matviewsync:
    periodMs: ${MATERIALIZED_VIEWS_SYNC_PERIOD_MS:5000}
    retryCount: ${MATERIALIZED_VIEWS_RETRY_COUNT:10}
    maxConcurrent: ${MATERIALIZED_VIEWS_CONCURRENT:2}

  metrics:
    enabled: ${DTM_CORE_METRICS_ENABLED:true}

  datasource:
    edml:
      defaultChunkSize: ${EDML_DEFAULT_CHUNK_SIZE:1000}
      pluginStatusCheckPeriodMs: ${EDML_STATUS_CHECK_PERIOD_MS:1000}
      firstOffsetTimeoutMs: ${EDML_FIRST_OFFSET_TIMEOUT_MS:15000}
      changeOffsetTimeoutMs: ${EDML_CHANGE_OFFSET_TIMEOUT_MS:10000}
    zookeeper:
      connection-string: ${ZOOKEEPER_DS_ADDRESS:localhost}
      connection-timeout-ms: ${ZOOKEEPER_DS_CONNECTION_TIMEOUT_MS:30000}
      session-timeout-ms: ${ZOOKEEPER_DS_SESSION_TIMEOUT_MS:86400000}
      chroot: ${ZOOKEEPER_DS_CHROOT:/adtm}

  kafka:
    producer:
      property:
        key.serializer: org.apache.kafka.common.serialization.StringSerializer
        value.serializer: org.apache.kafka.common.serialization.StringSerializer
    cluster:
      zookeeper:
        connection-string: ${ZOOKEEPER_KAFKA_ADDRESS:localhost}
        connection-timeout-ms: ${ZOOKEEPER_KAFKA_CONNECTION_TIMEOUT_MS:30000}
        session-timeout-ms: ${ZOOKEEPER_KAFKA_SESSION_TIMEOUT_MS:86400000}
        chroot: ${ZOOKEEPER_KAFKA_CHROOT:}
    admin:
      inputStreamTimeoutMs: ${KAFKA_INPUT_STREAM_TIMEOUT_MS:2000}
    status.event.publish:
      enabled: ${KAFKA_STATUS_EVENT_ENABLED:false}
    statusMonitor:
      statusUrl: ${STATUS_MONITOR_URL:http://localhost:9095/status}
      versionUrl: ${STATUS_MONITOR_VERSION_URL:http://localhost:9095/versions}

  vertx:
    blocking-stacktrace-time: ${DTM_VERTX_BLOCKING_STACKTRACE_TIME:1}
    pool:
      worker-pool: ${DTM_CORE_WORKER_POOL_SIZE:20}
      event-loop-pool: ${DTM_CORE_EVENT_LOOP_POOL_SIZE:20}
      task-pool: ${DTM_CORE_TASK_POOL_SIZE:20}
      task-timeout: ${DTM_CORE_TASK_TIMEOUT:86400000}

  cache:
    initialCapacity: ${CACHE_INITIAL_CAPACITY:100000}
    maximumSize: ${CACHE_MAXIMUM_SIZE:100000}
    expireAfterAccessMinutes: ${CACHE_EXPIRE_AFTER_ACCESS_MINUTES:99960}

  delta:
    rollback-status-calls-ms: ${DELTA_ROLLBACK_STATUS_CALLS_MS:2000}

adp:
  datasource:
    user: ${ADP_USERNAME:dtm}
    password: ${ADP_PASS:dtm}
    host: ${ADP_HOST:localhost}
    port: ${ADP_PORT:5432}
    poolSize: ${ADP_MAX_POOL_SIZE:3}
    executorsCount: ${ADP_EXECUTORS_COUNT:3}
    fetchSize: ${ADP_FETCH_SIZE:1000}
    preparedStatementsCacheMaxSize: ${ADP_PREPARED_CACHE_MAX_SIZE:256}
    preparedStatementsCacheSqlLimit: ${ADP_PREPARED_CACHE_SQL_LIMIT:2048}
    preparedStatementsCache: ${ADP_PREPARED_CACHE:true}

  mppw:
    restStartLoadUrl: ${ADP_REST_START_LOAD_URL:http://localhost:8096/newdata/start}
    restStopLoadUrl: ${ADP_REST_STOP_LOAD_URL:http://localhost:8096/newdata/stop}
    restVersionUrl: ${ADP_MPPW_CONNECTOR_VERSION_URL:http://localhost:8096/versions}
    kafkaConsumerGroup: ${ADP_KAFKA_CONSUMER_GROUP:adp-load}

  mppr:
    restLoadUrl: ${ADP_MPPR_QUERY_URL:http://localhost:8094/query}
    restVersionUrl: ${ADP_MPPR_CONNECTOR_VERSION_URL:http://localhost:8094/versions}
```

--------------------------------

### Configure PostgreSQL for Prostore Application

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-6-1/getting_started/getting_started

These commands set up a PostgreSQL database for the Prostore application. It involves creating a superuser role ('dtm') with a specified password ('dtm'), which should match the `adp:datasource:user` and `adp:datasource:password` in the Prostore configuration. A database named 'test' is also created, corresponding to the `env: name` parameter in the Prostore configuration. Finally, the PostgreSQL service is reloaded to apply the changes.

```Bash
# создание в СУБД Postgres SUPERUSER-пользователя c именем и паролем,
# указанными в конфигурации Prostore
# (значения параметров (adp:datasource:user) и (adp:datasource:password) соответственно)
cd /
sudo -u postgres psql -c 'CREATE ROLE dtm WITH LOGIN SUPERUSER'
sudo -u postgres psql -c "ALTER ROLE dtm WITH PASSWORD 'dtm'"
# создание базы данных с именем test, указанным в конфигурации Prostore (env: name)
sudo -u postgres psql -c 'CREATE DATABASE test'
# перезапуск сервиса Postgresql
sudo systemctl reload postgresql-13
```

--------------------------------

### CURL Example: Get DDL without Authorization Token

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-9/http_api/schema/ddl

Demonstrates how to make a GET request to the DDL endpoint for a logical entity without providing an authorization token. The example includes an 'x-request-id' header for request tracking.

```bash
curl -X 'GET' \
  'http://localhost:9090/api/v1/datamarts/marketing/entities/sales/ddl' \
  -H 'x-request-id: 2b2b7f18-136e-4fee-95ab-21887cdbe7b5'
```

--------------------------------

### CURL Example: Get Delta Information With Authorization Token

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-5/rest_api/deltas/by_num

Example CURL command to retrieve delta information from the Prostore API endpoint `/datamarts/{datamart}/deltas/{deltaNum}`, including an `Authorization: Bearer` token for authenticated requests.

```bash
curl -X 'GET' \
  'http://localhost:9090/api/v1/datamarts/marketing/deltas/12' \
  -H 'x-request-id: cb93bc6a-54a3-4a1f-a2cb-f575c8c6d777' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c'
```

--------------------------------

### BEGIN DELTA SQL+ Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-5/working_with_system/other_features/default_db_set-up/default_db_set-up

Reference for the `BEGIN DELTA` SQL+ command in Prostore.

```SQL
BEGIN DELTA
```

--------------------------------

### CURL Example: Get Delta Information Without Token

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-5/rest_api/deltas/by_num

Example CURL command to retrieve delta information from the Prostore API endpoint `/datamarts/{datamart}/deltas/{deltaNum}` without including an authorization token, demonstrating basic request structure.

```bash
curl -X 'GET' \
  'http://localhost:9090/api/v1/datamarts/marketing/deltas/12' \
  -H 'x-request-id: cb93bc6a-54a3-4a1f-a2cb-f575c8c6d777'
```

--------------------------------

### Show Prostore Configuration

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-4/working_with_system/other_features/default_db_set-up/default_db_set-up

Displays the current configuration parameters and settings of the Prostore system.

```APIDOC
CONFIG_SHOW
```

--------------------------------

### API Response Examples for Asynchronous Query Results

Source: https://prostore.datamart.ru/docs_prostore/http_api/openapi_spec/openapi_spec

Provides examples of successful query results, including a full result set, an empty result set, and an asynchronous operation start confirmation. These examples illustrate the structure of data returned from query operations.

```APIDOC
          examples:
            ResultSet:
              value:
                queryId: '12345'
                result:
                  - name: test
                    id: 0
                  - name: test1
                    id: 1
                metadata:
                  - name: id
                    type: BIGINT
                    size: null
                    nullable: false
                  - name: name
                    type: VARCHAR
                    size: -1
                    nullable: true
                rows: 2
                statistics:
                  elapsedTotalMs: 34
                  elapsedDbMs: 20
            ResultSet (empty):
              value:
                queryId: null
                result: []
                metadata:
                  - name: id
                    type: BIGINT
                    size: null
                    nullable: false
                  - name: name
                    type: VARCHAR
                    size: -1
                    nullable: true
                rows: 0
                statistics:
                  elapsedTotalMs: 34
                  elapsedDbMs: 20
            async:
              value:
                requestId: 2f8b7a67-a17e-4f71-a0f0-22249c005d5c
                message: Async operation started
```

--------------------------------

### Example cURL Request for Latest Deltas API

Source: https://prostore.datamart.ru/docs_prostore/_archive/v7-1/http_api/deltas/latest

This example demonstrates how to make a GET request to the /api/v1/datamarts/marketing/deltas/latest endpoint using cURL, including an optional x-request-id header.

```Bash
curl -X 'GET' \
  'http://localhost:9090/api/v1/datamarts/marketing/deltas/latest' \
  -H 'x-request-id: ee91d2d8-5465-46ed-9f8d-02c71a99a08c'
```

--------------------------------

### Create a New Prostore Database

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-4/working_with_system/other_features/default_db_set-up/default_db_set-up

Defines and initializes a new database within the Prostore environment, preparing it for data storage and management.

```APIDOC
CREATE DATABASE
```

--------------------------------

### CREATE DATABASE SQL+ Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-5/working_with_system/other_features/default_db_set-up/default_db_set-up

Reference for the `CREATE DATABASE` SQL+ command in Prostore.

```SQL
CREATE DATABASE
```

--------------------------------

### Example: Get Statistics for Single Entity (No Authorization)

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-9/http_api/statistics/get_statistics

Demonstrates a `curl` command to retrieve statistics for a specific logical entity (`sales` in `marketing` datamart) without an authorization token, including an `x-request-id` header.

```bash
curl -X 'GET' \
  'http://localhost:9090/api/v1/datamarts/marketing/entities/sales/statistics' \
  -H 'x-request-id: 7cf843da-fef7-45cf-8d81-cdccfc57b662'
```

--------------------------------

### PostgreSQL Database Setup for Prostore

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-2/getting_started/getting_started

This script provides commands to configure a PostgreSQL database for Prostore. It includes creating a SUPERUSER role with a specified username and password (matching `adp:datasource:user` and `adp:datasource:password` in Prostore's configuration) and creating a database named 'test' (matching `env:name` in Prostore's configuration). Finally, it reloads the PostgreSQL service.

```bash
# создание в СУБД Postgres SUPERUSER-пользователя c именем и паролем,
# указанными в конфигурации Prostore
# (значения параметров (adp:datasource:user) и (adp:datasource:password) соответственно)
cd /
sudo -u postgres psql -c 'CREATE ROLE dtm WITH LOGIN SUPERUSER'
sudo -u postgres psql -c "ALTER ROLE dtm WITH PASSWORD 'dtm'"
# создание базы данных с именем test, указанным в конфигурации Prostore (env: name)
sudo -u postgres psql -c 'CREATE DATABASE test'
# перезапуск сервиса Postgresql
sudo systemctl reload postgresql-13
```

--------------------------------

### CONFIG_SHOW Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-12-2/working_with_data/download_to_kafka/path_to_kafka_topic/path_to_kafka_topic

Displays the current configuration settings of the Prostore system. This command provides insights into various operational parameters and their values.

```APIDOC
CONFIG_SHOW
```

--------------------------------

### Example: Get Statistics for Single Entity (With Authorization)

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-9/http_api/statistics/get_statistics

Illustrates a `curl` command to retrieve statistics for a specific logical entity (`sales` in `marketing` datamart) using a JWT bearer token for authorization, along with an `x-request-id` header.

```bash
curl -X 'GET' \
  'http://localhost:9090/api/v1/datamarts/marketing/entities/sales/statistics' \
  -H 'x-request-id: 91e6032f-f00d-4e37-822d-6170179e15d0' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c'
```

--------------------------------

### Example Prostore JDBC Connection String

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-4/working_with_system/connection/connection_via_code/connection_via_code

A concrete example of a Prostore JDBC URL with specific host, port, and logical database, demonstrating how to form the connection string and establish the connection.

```java
String url = "jdbc:prostore://10.92.3.3:9092/demo";
Connection conn = DriverManager.getConnection(url, null, null);
```

--------------------------------

### BEGIN DELTA SQL+ Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-7/working_with_system/connection/connection

Documentation for the BEGIN DELTA SQL+ command in Prostore, used to start a new delta transaction.

```SQL
BEGIN DELTA
```

--------------------------------

### CURL Example: Get DDL with Authorization Token

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-9/http_api/schema/ddl

Illustrates how to make a GET request to the DDL endpoint for a logical entity, including both an 'x-request-id' and an 'Authorization: Bearer' header with a JWT token for authenticated access.

```bash
curl -X 'GET' \
  'http://localhost:9090/api/v1/datamarts/marketing/entities/sales/ddl' \
  -H 'x-request-id: 2b2b7f18-136e-4fee-95ab-21887cdbe7b5' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c'
```

--------------------------------

### Execute GET Request with CURL to Datamart API

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-1-1/rest_api/deltas/latest_ok

This snippet demonstrates how to perform a GET request using CURL to retrieve the latest delta status for the 'marketing' datamart. It includes a custom 'x-request-id' header for tracing purposes.

```curl
curl -X 'GET' \
  'http://localhost:9090/api/v1/datamarts/marketing/deltas/latest/ok' \
  -H 'x-request-id: e5d28c37-2b8e-4d1e-8ea3-fc8cf211367b'
```

--------------------------------

### CREATE TABLE SQL+ Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-5/working_with_system/other_features/default_db_set-up/default_db_set-up

Reference for the `CREATE TABLE` SQL+ command in Prostore.

```SQL
CREATE TABLE
```

--------------------------------

### Example: Create Table DDL Script

Source: https://prostore.datamart.ru/docs_prostore/http_api/openapi_spec/openapi_spec

An example of a SQL DDL script for creating a table named `ALL_TYPES_TRANSACTIONS` with various column types and primary key constraints. This script is typically returned by the 'Get Entity DDL script' API.

```SQL
CREATE TABLE TESTDB.ALL_TYPES_TRANSACTIONS (TRANSACTION_ID BIGINT NOT NULL, ACCOUNT_ID BIGINT NOT NULL, DOUBLE_COL DOUBLE NULL, FLOAT_COL FLOAT NULL, VARCHAR_COL VARCHAR(36) NULL, BOOLEAN_COL BOOLEAN NULL, INT_COL INT NULL, BIGINT_COL BIGINT NULL, DATE_COL DATE NULL, TIMESTAMP_COL TIMESTAMP(6) NULL, TIME_COL TIME(5) NULL, UUID_COL UUID NULL, CHAR_COL CHAR(10) NULL, INT32_COL INT32 NULL, LINK_COL LINK NULL, PRIMARY KEY (TRANSACTION_ID, ACCOUNT_ID)) DISTRIBUTED BY (ACCOUNT_ID) DATASOURCE_TYPE (ADB, ADG, ADP, ADQM)
```

--------------------------------

### API Schema and Examples for Asynchronous Query Status

Source: https://prostore.datamart.ru/docs_prostore/http_api/openapi_spec/openapi_spec

Outlines the schema for checking the status of an asynchronous query, including its current state, associated datamart, table, query, and timestamps for start and error. Examples show both running and error states for a query.

```APIDOC
    async-query-status:
      description: ResultSet
      content:
        application/json:
          schema:
            type: object
            properties:
              status:
                type: string
              statusCode:
                type: integer
              datamart:
                type: string
              table:
                type: string
              topic:
                type: string
                nullable: true
              query:
                type: string
              startTime:
                type: string
              errorTime:
                type: string
                nullable: true
              errorCause:
                type: string
                nullable: true
            required:
              - status
              - statusCode
              - datamart
              - table
              - topic
              - query
              - startTime
              - errorTime
              - errorCause
          examples:
            query-status-run:
              value:
                status: running
                statusCode: 0
                datamart: testdb
                table: tbl
                topic: testdb_topic
                query: INSERT INTO testdb.tbl SELECT * FROM testdb.upload_tbl
                startTime: '2023-09-04 16:06:28'
                errorTime: null
                errorCause: null
            query-status-error:
              value:
                status: error
                statusCode: 2
                datamart: testdb
                table: tbl
                topic: null
                query: INSERT INTO testdb.tbl SELECT * FROM testdb.tbl2
                startTime: '2023-09-04 16:13:45'
                errorTime: '2023-09-04 16:13:46'
```

--------------------------------

### Show Prostore Configuration Settings

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-12-2/about/main_concepts/external_system/external_system

Displays the current configuration settings and parameters for the Prostore system.

```APIDOC
CONFIG_SHOW
```

--------------------------------

### API Schema for Query Status and Examples

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-12-2/http_api/openapi_spec/openapi_spec

Defines the structure for query status responses, including query ID, datamart, table, status, status code, and start time. Provides example values for running and error states.

```APIDOC
datamart:
  type: string
table:
  type: string
status:
  type: string
statusCode:
  type: integer
startTime:
  type: string
required:
  - id
  - datamart
  - table
  - status
  - statusCode
  - startTime
examples:
  queries-list:
    value:
      - id: 2f8b7a67-a17e-4f71-a0f0-22249c005d5c
        datamart: testdb
        table: tbl
        status: running
        statusCode: 0
        startTime: '2023-09-04 16:06:28'
      - id: c0a8b9e8-34d0-4e2b-b35c-c7e6c812de45
        datamart: testdb
        table: tbl
        status: error
        statusCode: 2
        startTime: '2023-09-04 16:13:45'
```

--------------------------------

### SQL: Get Local Timestamp (LOCALTIMESTAMP) in ADB/ADP

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-0/reference/sql_support/sql_support

Illustrates how to retrieve the current local timestamp using the LOCALTIMESTAMP function, with optional precision. Supported data sources are ADB and ADP. Examples show getting the timestamp directly or casting it to a TIMESTAMP data type.

```SQL
SELECT LOCALTIMESTAMP FROM table1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIMESTAMP AS TIMESTAMP) FROM table1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT LOCALTIMESTAMP(3) FROM table1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIMESTAMP(3) AS TIMESTAMP) FROM table1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

--------------------------------

### PostgreSQL Database Setup for Prostore

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-7/getting_started/getting_started

This snippet provides shell commands to configure a PostgreSQL database for the Prostore application. It includes creating a superuser role with a specified username and password, creating a database, and reloading the PostgreSQL service. The credentials and database name are expected to match the Prostore configuration.

```bash
# создание в СУБД Postgres SUPERUSER-пользователя c именем и паролем,
# указанными в конфигурации Prostore
# (значения параметров (adp:datasource:user) и (adp:datasource:password) соответственно)
cd /
sudo -u postgres psql -c 'CREATE ROLE dtm WITH LOGIN SUPERUSER'
sudo -u postgres psql -c "ALTER ROLE dtm WITH PASSWORD 'dtm'"
# создание базы данных с именем test, указанным в конфигурации Prostore (env: name)
sudo -u postgres psql -c 'CREATE DATABASE test'
# перезапуск сервиса Postgresql
sudo systemctl reload postgresql-13
```

--------------------------------

### SQL: Get Local Time (LOCALTIME) in ADB/ADP

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-0/reference/sql_support/sql_support

Demonstrates how to retrieve the current local time using the LOCALTIME function, with optional precision. Supported data sources are ADB and ADP. Examples include getting the time directly or casting it to a TIME data type.

```SQL
SELECT LOCALTIME FROM table1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIME AS TIME) FROM table1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT LOCALTIME(3) FROM table1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIME(3) AS TIME) FROM table1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

--------------------------------

### CONFIG_SHOW Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-12-2/sql_plus_requests/create_proxy_table/create_proxy_table

Displays the current configuration settings of the Prostore system.

```APIDOC
CONFIG_SHOW
```

--------------------------------

### API Endpoint: Get Health Readiness Probe State

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-11/http_api/openapi_spec/health_openapi_spec

Defines the GET `/api/v1/health/readiness` endpoint, which returns the current readiness probe state. The response schema details the `status` (OUT_OF_SERVICE, DOWN) and `components` states, including `dtmState` and `readinessState`, referencing shared probe status models. Examples for `DOWN` and `OUT_OF_SERVICE` responses are provided.

```APIDOC
get:
  operationId: get-api-v1-health-readiness
  description: Return current readiness prob state.
  parameters: []
  responses:
    "200":
      description: OK
      content:
        application/json:
          schema:
            type: object
            properties:
              status:
                type: string
                enum:
                  - OUT_OF_SERVICE
                  - DOWN
              components:
                type: object
                required:
                  - dtmState
                  - readinessState
                properties:
                  dtmState:
                    anyOf:
                      - $ref: '#/components/schemas/probe-status-up'
                      - $ref: '#/components/schemas/probe-status-down'
                  readinessState:
                    anyOf:
                      - $ref: '#/components/schemas/probe-status-up'
                      - $ref: '#/components/schemas/probe-status-out-of-service'
            required:
              - status
              - components
          examples:
            DOWN:
              value:
                status: DOWN
                components:
                  dtmState:
                    status: DOWN
                    details:
                      exception: Query processing verticle is not running
                  readinessState:
                    status: UP
            OUT_OF_SERVICE:
              value:
                status: OUT_OF_SERVICE
                components:
                  dtmState:
                    status: UP
                  readinessState:
                    status: OUT_OF_SERVICE
```

--------------------------------

### CREATE DATABASE Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-7/getting_started/getting_started

Creates a new database instance within the Prostore environment. This command initializes a new logical container for tables, views, and other database objects. It is the first step in setting up a new data repository.

```SQL
CREATE DATABASE
```

--------------------------------

### CREATE DATABASE SQL+ Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-7/overview/main_concepts/change_queue/change_queue

Documents the Prostore SQL+ command for defining and initializing a new database instance.

```SQL
CREATE DATABASE
```

--------------------------------

### Get Local Timestamp in SQL

Source: https://prostore.datamart.ru/docs_prostore/_archive/v7-0/reference/sql_support/sql_support

Shows how to use the LOCALTIMESTAMP function to retrieve the current local timestamp. Examples cover getting the timestamp with and without specified precision, casting to TIMESTAMP, and using LOCALTIMESTAMP within a Common Table Expression (CTE) for ADB and ADP data sources.

```SQL
SELECT LOCALTIMESTAMP [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIMESTAMP AS TIMESTAMP) [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT LOCALTIMESTAMP(3) [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIMESTAMP(3) AS TIMESTAMP) [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT LOCALTIMESTAMP [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT CAST(LOCALTIMESTAMP AS TIMESTAMP) [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT LOCALTIMESTAMP(3) [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT CAST(LOCALTIMESTAMP(3) AS TIMESTAMP) [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

--------------------------------

### Show Prostore Configuration

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-4/working_with_system/logical_schema_update/create_download_table/create_download_table

Displays the current configuration parameters and settings of the Prostore Data Mart system, providing insight into its operational setup.

```SQL
CONFIG_SHOW
```

--------------------------------

### Get Local Time in SQL

Source: https://prostore.datamart.ru/docs_prostore/_archive/v7-0/reference/sql_support/sql_support

Illustrates the use of the LOCALTIME function to retrieve the current local time. Examples include getting the time with and without specified precision, casting to TIME, and using LOCALTIME within a Common Table Expression (CTE) for ADB and ADP data sources.

```SQL
SELECT LOCALTIME [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIME AS TIME) [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT LOCALTIME(3) [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIME(3) AS TIME) [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT LOCALTIME [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT CAST(LOCALTIME AS TIME) [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT LOCALTIME(3) [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT CAST(LOCALTIME(3) AS TIME) [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

--------------------------------

### SQL: CREATE VIEW command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-3/reference/download_format/download_format

Documentation for the SQL-like CREATE VIEW command in Prostore, used for defining new views.

```SQL
CREATE VIEW
```

--------------------------------

### API Response Schema: Asynchronous Query Status

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-9/http_api/openapi_spec/openapi_spec

Describes the schema and examples for checking the status of an asynchronous query. Includes details like query status, status code, datamart, table, topic, query string, and timestamps for start and error. Provides examples for running and error states.

```APIDOC
headers:
  x-request-id:
    $ref: '#/components/headers/x-request-id-required'
async-query-status:
  description: ResultSet
  content:
    application/json:
      schema:
        type: object
        properties:
          status:
            type: string
          statusCode:
            type: integer
          datamart:
            type: string
          table:
            type: string
          topic:
            type: string
            nullable: true
          query:
            type: string
          startTime:
            type: string
          errorTime:
            type: string
            nullable: true
          errorCause:
            type: string
            nullable: true
        required:
          - status
          - statusCode
          - datamart
          - table
          - topic
          - query
          - startTime
          - errorTime
          - errorCause
      examples:
        query-status-run:
          value:
            status: running
            statusCode: 0
            datamart: testdb
            table: tbl
            topic: testdb_topic
            query: INSERT INTO testdb.tbl SELECT * FROM testdb.upload_tbl
            startTime: '2023-09-04 16:06:28'
            errorTime: null
            errorCause: null
        query-status-error:
          value:
            status: error
            statusCode: 2
            datamart: testdb
            table: tbl
            topic: null
            query: INSERT INTO testdb.tbl SELECT * FROM testdb.tbl2
            startTime: '2023-09-04 16:13:45'
            errorTime: '2023-09-04 16:13:46'
            errorCause: 'Table[all_types] blocked: KeeperErrorCode = NodeExists'
```

--------------------------------

### SQL: CREATE TABLE command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-3/reference/download_format/download_format

Documentation for the SQL-like CREATE TABLE command in Prostore, used for defining new tables.

```SQL
CREATE TABLE
```

--------------------------------

### API Response Example: Empty ResultSet and Async Operation Start

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-11/http_api/openapi_spec/openapi_spec

Illustrates the structure of an empty ResultSet response from the Prostore data mart API, including metadata for columns and overall query statistics. It also shows the structure for an asynchronous operation start confirmation, providing a request ID.

```APIDOC
elapsedDbMs: 20
ResultSet (empty):
  value:
    result: []
    metadata:
      - name: id
        type: BIGINT
        size: null
        nullable: false
      - name: name
        type: VARCHAR
        size: -1
        nullable: true
    rows: 0
    queryId: null
    statistics:
      elapsedTotalMs: 34
      elapsedDbMs: 20
async:
  value:
    requestId: 2f8b7a67-a17e-4f71-a0f0-22249c005d5c
    message: Async operation started
```

--------------------------------

### CONFIG_SHOW Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-12-2/connection/authentication/authentication

Displays the current configuration settings of the Prostore system.

```APIDOC
CONFIG_SHOW
```

--------------------------------

### Get Local Time in SQL

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-10/reference/sql_support/sql_support

Illustrates how to retrieve the current local time using the LOCALTIME function. Examples show basic usage, casting to TIME, and specifying precision. Also includes examples of using LOCALTIME within Common Table Expressions (CTEs). Supports ADB and ADP data sources.

```SQL
SELECT LOCALTIME [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIME AS TIME) [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT LOCALTIME(3) [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
SELECT CAST(LOCALTIME(3) AS TIME) [FROM table1] DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT LOCALTIME [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT CAST(LOCALTIME AS TIME) [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT LOCALTIME(3) [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

```SQL
WITH cte1 AS (SELECT CAST(LOCALTIME(3) AS TIME) [FROM table1]) SELECT * FROM cte1 DATASOURCE_TYPE = {'ADB' | 'ADP'};
```

--------------------------------

### API Response Schema and Examples for Asynchronous Query Status

Source: https://prostore.datamart.ru/docs_prostore/_archive/v7-1/http_api/openapi_spec/openapi_spec

Provides the OpenAPI schema for asynchronous query status responses, including properties like status, status code, datamart, table, query string, and timestamps for start and error. Includes examples for both running and error states.

```APIDOC
schema:
  type: object
  properties:
    status:
      type: string
    statusCode:
      type: integer
    datamart:
      type: string
    table:
      type: string
    topic:
      type: string
      nullable: true
    query:
      type: string
    startTime:
      type: string
    errorTime:
      type: string
      nullable: true
    errorCause:
      type: string
      nullable: true
  required:
    - status
    - statusCode
    - datamart
    - table
    - topic
    - query
    - startTime
    - errorTime
    - errorCause
examples:
  query-status-run:
    value:
      status: running
      statusCode: 0
      datamart: testdb
      table: tbl
      topic: testdb_topic
      query: INSERT INTO testdb.tbl SELECT * FROM testdb.upload_tbl
      startTime: '2023-09-04 16:06:28'
      errorTime: null
      errorCause: null
  query-status-error:
    value:
      status: error
      statusCode: 2
      datamart: testdb
      table: tbl
      topic: null
      query: INSERT INTO testdb.tbl SELECT * FROM testdb.tbl2
      startTime: '2023-09-04 16:13:45'
      errorTime: '2023-09-04 16:13:46'
      errorCause: 'Table[all_types] blocked: KeeperErrorCode = NodeExists'
```

--------------------------------

### CREATE VIEW SQL+ Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-5/working_with_system/other_features/default_db_set-up/default_db_set-up

Reference for the `CREATE VIEW` SQL+ command in Prostore.

```SQL
CREATE VIEW
```

--------------------------------

### SQL Command: CREATE TABLE

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-3/working_with_system/other_features/default_db_set-up/default_db_set-up

Documentation for the SQL CREATE TABLE command in Prostore, used to define new tables.

```SQL
CREATE TABLE
```

--------------------------------

### CURL Request: Get Current Delta (With Authorization)

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-10/http_api/deltas/current

Example CURL command to retrieve the current delta for a datamart with a Bearer authorization token and an `x-request-id` header.

```curl
curl -X 'GET' \
  'http://localhost:9090/api/v1/datamarts/marketing/deltas/current' \
  -H 'x-request-id: 654e270c-f888-4d14-9695-7e2eb485114e' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c'
```

--------------------------------

### Check Prostore System Versions

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-12-2/working_with_data/managing_write_ops/managing_write_ops

Retrieves version information for the Prostore system components and installed modules. This command helps in verifying the current setup and compatibility.

```SQL
CHECK_VERSIONS;
```

--------------------------------

### CONFIG_SHOW Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v5-7/working_with_system/logical_schema_update/create_readable_table/create_readable_table

Displays the current configuration settings of the Prostore system.

```APIDOC
CONFIG_SHOW
```

--------------------------------

### Check Prostore System Versions

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-12-2/working_with_data/download_to_kafka/downloading_data/downloading_data

Retrieves the current version information for the Prostore system components and installed modules. This helps in verifying the environment setup and compatibility.

```APIDOC
CHECK_VERSIONS
```

--------------------------------

### CONFIG_SHOW Command

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-4/overview/main_concepts/partitioning/partitioning

Documents the CONFIG_SHOW command, used to display current configuration settings for the Prostore system.

```APIDOC
CONFIG_SHOW
```

--------------------------------

### Get Latest Delta-ok for Datamart

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-9/http_api/openapi_spec/openapi_spec

Retrieves information about the latest 'delta-ok' for a specific datamart. If the delta does not exist, null is returned. Includes examples for both existing and empty delta-ok.

```APIDOC
'/api/v1/datamarts/{datamart}/deltas/latest/ok':
  get:
    summary: Get Delta-ok
    tags:
      - Deltas
    parameters:
      - $ref: '#/components/parameters/x-request-id'
    responses:
      '200':
        description: Information about delta-ok.
        content:
          application/json:
            schema:
              type: object
              properties:
                ok:
                  anyOf:
                    - $ref: '#/components/schemas/null'
                    - $ref: '#/components/schemas/delta'
            examples:
              delta-ok:
                value:
                  ok:
                    deltaNum: 7
                    deltaDate: '2022-08-09 11:38:04'
                    deltaServerDate: '2022-08-09 11:38:04'
                    cnFrom: 7
              delta-ok empty:
                value:
                  ok: null
        headers:
          x-request-id:
            $ref: '#/components/headers/x-request-id-required'
      '500':
        $ref: '#/components/responses/500'
    operationId: get-deltas-latest-ok
    description: 'A query that returns a delta-ok information. If the delta does not exist, null will be returned for it.'
  parameters:
    - $ref: '#/components/parameters/datamart'
```

--------------------------------

### SQL Command: USE

Source: https://prostore.datamart.ru/docs_prostore/_archive/v6-3/working_with_system/other_features/default_db_set-up/default_db_set-up

Documentation for the SQL USE command in Prostore, used to select a database to work with.

```SQL
USE
```
Tokens:
Raw