1 - Overview

Service Overview

Quick Query is an interactive query service that allows you to easily and quickly analyze large-scale data using standard SQL. It is automatically installed on a standard Kubernetes cluster, and you can easily and quickly access various data sources such as Cloud Hadoop, Object Storage, and RDB for data retrieval and processing.

Features

  • Easy and Fast Data Retrieval: After defining a schema for data stored in Object Storage and executing queries using standard SQL, you can retrieve data easily and quickly. Any user who can work with SQL can easily analyze large data sets, even without being a professional analyst.
  • Fast Parallel Distributed Processing: Using the Trino engine capable of parallel distributed processing, queries are automatically split and processed in parallel across multiple nodes simultaneously, allowing rapid query results even for large-scale data.
  • Various Service Architectures: We provide a public fixed-resource mode, a public resource-scaling mode, and a personal resource-scaling mode. The public fixed-resource mode supports stable response times for large-scale data queries, while the public resource-scaling mode can be used at a lower cost when usage frequency is irregular. Additionally, the personal resource-scaling mode enables each user to perform analysis tasks in an independent environment, allowing the use of Quick Query with a structure that meets user requirements.

Service Architecture Diagram

Diagram
Figure. Quick Query diagram

Provided features

Quick Query provides the following features.

  • Support single access to various data sources (support for 11 types of data sources)
  • Automatic saving of result data in Object Storage
  • Result reuse feature for identical queries
  • Access control feature through Ranger integration
  • Data Usage Control Feature
CategorytypeRemarks
Cloud Hadoophive_on_cloud_hadoop
iceberg_on_cloud_hadoop
Using Hive Metastore in Cloud Hadoop
Object Storagehive_on_object_storage
iceberg_on_object_storag
Deploy and use Hive Metastore in Quick Query
RDBpostgresql
mariadb
sqlserver
oracle
mysql
JDBC Driver Upload needed (license)
TPCDStpcdsBuilt-in Data Source provided by Quick Query
TPCHtpchBuilt-in Data Source provided by Quick Query
Table. Supported Data Source
typeselectinsertuptatedeletecreatedropalteranalyzecall
hive_on_cloud_hadoopOOOOOOOOO
iceberg_on_cloud_hadoopOOOOOOOOO
hive_on_object_storageOOOOOOOOO
iceberg_on_object_storageOOOOOOOOO
postgresqlOOOOOO
mariadbOOOOOO
sqlserverOOOOOO
greenplumOOOOOO
oracleOOOOOO
mysqlOOOOOO
tpcdsO
tpchO
Table. Supported SQL

Component

Query Engine Type: Shared

The query engine is structured so that a single instance, once started, can be shared by multiple users.

  • Fixed Resource Mode (Auto Scaling Disabled): When Auto Scaling is not used, the query engine for the fixed resources is launched according to the resources selected by the user. Because the query engine always runs on the same resources, it can guarantee consistent query performance.

    Diagram
    Figure. Fixed resource mode (Auto Scaling not used)
  • Resource Expansion Mode (Auto Scaling enabled): When Auto Scaling is used, the query engine’s Worker nodes automatically scale in/out based on throughput. If the throughput is low, the number of Worker nodes can be reduced to as few as one, and when the throughput increases, the Worker nodes expand. Additionally, resources can be adjusted according to the cluster size.

    Diagram
    Figure. Resource expansion mode (using Auto Scaling)

Query Engine Type: Private

  • Resource Expansion Mode (Auto Scaling Enabled): The personal query engine type runs a separate query engine for each user. Each query engine supports Auto Scale in/out, and if unused for an extended period, the engine automatically stops. When reconnecting for reuse, the query engine automatically restarts. When the throughput is low, the number of Worker nodes can decrease to as few as one, and when the throughput increases, the number of Worker nodes grows. Additionally, resources can be adjusted according to the cluster size.

    Diagram
    Figure. Resource Expansion Mode (using Auto Scaling)

Server type

The server types supported by Quick Query are as follows.

CategoryexampleDetailed description
Server typeStandardProvided server types
  • Standard: Standard configuration (vCPU, Memory) commonly used
  • High Capacity: Large-capacity server specifications with 24 cores or more
Server sizes1v2m4Provided server specifications
  • vCPU 2, Memory 4G
Table. Quick Query Supported Server Types

The minimum specifications required to use Quick Query are as follows.

CategoryDetailsCluster size (user input value)Fixed node poolAuto-scaling node pool
CommonFixed resource mode (Auto Scaling not used)Replica: 1
CPU: 4 Core
Memory: 8GB
8 Core, 16GB * 4N/A
CommonResource expansion mode (Auto Scaling enabled)Small(1 Core, 4GB)8 Core, 16GB * 38 Core, 16GB * 1
PersonalResource expansion mode (Auto Scaling enabled)Small(1 Core, 4GB)8 Core, 16GB * 38 Core, 32GB * 2
Table. Quick Query Minimum Specifications

Provision status by region

Quick Query is available in the following environments.

regionProvision status
Korea West (kr-west1)Provide
Korea East (kr-east1)Provide
South Korea 1 (kr-south1)Not provided
South Korea South 2 (kr-south2)Not provided
South Korea 3 (kr-south3)Not provided
Table. Quick Query Provision Status by Region

Preliminary Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

Service CategoryserviceDetailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
NetworkingSecurity GroupVirtual firewall that controls server traffic
StorageFile StorageA storage system that enables multiple client servers to share files over a network connection.
Table. Quick Query Preliminary Services

1.1 - ServiceWatch metric

You can view Kubernetes Engine metrics in ServiceWatch for the Kubernetes Engine created from Quick Query. As with Kubernetes Engine, the metrics provided by default monitoring are data collected at one‑minute intervals.

Reference
Refer to the ServiceWatch guide for how to view metrics in ServiceWatch.

Basic Metrics

The following are basic metrics for the Kubernetes Engine namespace.

The metrics whose names are shown in bold below are the key metrics selected from the default metrics provided by Kubernetes Engine. Key metrics are used to build service dashboards that are automatically created for each service in ServiceWatch.

Each metric provides guidance in the user guide on which statistical values are meaningful when querying that metric, and among the meaningful statistics, the values shown in bold are the primary statistics. In the service dashboard, you can view key metrics using primary statistical values.

Indicator NameDetailed descriptionunitmeaningful statistics
cluster_upCluster upCount
  • Total
  • Average
  • Maximum
  • Minimum
cluster_node_countNumber of cluster nodesCount
  • Total
  • Average
  • Maximum
  • Minimum
cluster_failed_node_countNumber of failed nodes in the clusterCount
  • Total
  • Average
  • Maximum
  • Minimum
cluster_namespace_phase_countNumber of cluster namespace phasesCount
  • Total
  • Average
  • Maximum
  • Minimum
cluster_pod_phase_countNumber of cluster pod phasesCount
  • Total
  • Average
  • Maximum
  • Minimum
node_cpu_allocatableNode CPU allocatable amount-
  • Total
  • Average
  • Maximum
  • Minimum
node_cpu_capacityNode CPU capacity-
  • Total
  • Average
  • Maximum
  • Minimum
node_cpu_usageNode CPU usage-
  • Total
  • Average
  • Maximum
  • Minimum
node_cpu_utilizationNode CPU usage-
  • Total
  • Average
  • Maximum
  • Minimum
node_memory_allocatableNode memory allocatable amountBytes
  • Total
  • Average
  • Maximum
  • Minimum
node_memory_capacityNode memory capacityBytes
  • Total
  • Average
  • Maximum
  • Minimum
node_memory_usageNode memory usageBytes
  • Total
  • Average
  • Maximum
  • Minimum
node_memory_utilizationNode memory usage rate-
  • Total
  • Average
  • Maximum
  • Minimum
node_network_rx_bytesNode network received bytesBytes/Second
  • Total
  • Average
  • Maximum
  • Minimum
node_network_tx_bytesNode network transmitted bytesBytes/Second
  • Total
  • Average
  • Maximum
  • Minimum
node_network_total_bytesTotal bytes of the node networkBytes/Second
  • Total
  • Average
  • Maximum
  • Minimum
node_number_of_running_podsNumber of pods running on the nodeCount
  • Total
  • Average
  • Maximum
  • Minimum
namespace_number_of_running_podsNumber of running pods in the namespaceCount
  • Total
  • Average
  • Maximum
  • Minimum
namespace_deployment_pod_countNamespace deployment pod countCount
  • Total
  • Average
  • Maximum
  • Minimum
namespace_statefulset_pod_countNamespace StatefulSet pod countCount
  • Total
  • Average
  • Maximum
  • Minimum
namespace_daemonset_pod_countNumber of DaemonSet Pods per NamespaceCount
  • Total
  • Average
  • Maximum
  • Minimum
namespace_job_active_countActive namespace job countCount
  • Total
  • Average
  • Maximum
  • Minimum
namespace_cronjob_active_countNumber of active namespace cronjobsCount
  • Total
  • Average
  • Maximum
  • Minimum
pod_cpu_usagePod CPU usage-
  • Total
  • Average
  • Maximum
  • Minimum
pod_memory_usagePod memory usageBytes
  • Total
  • Average
  • Maximum
  • Minimum
pod_network_rx_bytesPod network received bytesBytes/Second
  • Total
  • Average
  • Maximum
  • Minimum
pod_network_tx_bytesPod network transmitted bytesBytes/Second
  • Total
  • Average
  • Maximum
  • Minimum
pod_network_total_bytesTotal pod network bytesCount
  • Total
  • Average
  • Maximum
  • Minimum
container_cpu_usageContainer CPU usage-
  • Total
  • Average
  • Maximum
  • Minimum
container_cpu_limitContainer CPU limit-
  • Total
  • Average
  • Maximum
  • Minimum
container_cpu_utilizationContainer CPU usage-
  • Total
  • Average
  • Maximum
  • Minimum
container_memory_usageContainer memory usageBytes
  • Total
  • Average
  • Maximum
  • Minimum
container_memory_limitContainer memory limitBytes
  • Total
  • Average
  • Maximum
  • Minimum
container_memory_utilizationContainer memory usage rate-
  • Total
  • Average
  • Maximum
  • Minimum
node_gpu_countNode GPU countCount
  • Total
  • Average
  • Maximum
  • Minimum
gpu_tempGPU temperature-
  • Total
  • Average
  • Maximum
  • Minimum
gpu_power_usageGPU power consumption-
  • Total
  • Average
  • Maximum
  • Minimum
gpu_utilGPU utilizationPercent
  • Total
  • Average
  • Maximum
  • Minimum
gpu_sm_clockGPU SM clock-
  • Total
  • Average
  • Maximum
  • Minimum
gpu_fb_usedGPU FB usageMegabytes
  • Total
  • Average
  • Maximum
  • Minimum
gpu_tensor_activeGPU tensor utilization-
  • Total
  • Average
  • Maximum
  • Minimum
pod_gpu_utilPod GPU utilizationPercent
  • Total
  • Average
  • Maximum
  • Minimum
pod_gpu_tensor_activePod GPU Tensor Utilization Rate-
  • Total
  • Average
  • Maximum
  • Minimum
Table. Kubernetes Engine Basic Metrics

2 - How-to guides

Users can create the service by entering the required Quick Query information and selecting detailed options through the Samsung Cloud Platform Console.

Create Quick Query

You can create and use the Quick Query service in the Samsung Cloud Platform Console.

To create a Quick Query, follow these steps.

  1. Click the All Services > Data Analytics > Quick Query menu. Go to the Service Home page of Quick Query.

  2. On the Service Home page, click the Quick Query Create button. You will be taken to the Quick Query Create page.

  3. On the Quick Query creation page, enter the information required to create the service and select detailed options.

    • In the Version selection area, select the required information.
      Category
      Required status
      Detailed description
      Quick QueryRequiredSelect Quick Query Service Version
      • Provide a list of available versions
      Table. Quick Query Service Version Selection
    • In the Service Information Input area, enter or select the required information.
      Category
      Required status
      Detailed description
      Quick Query nameRequiredEnter Quick Query name
      • Start with a lowercase English letter and ensure it does not end with a special character (-), using lowercase letters, numbers, and special characters (-) to enter 3 ~ 30 characters
      descriptionSelectionEnter additional information or description about Quick Query within 150 characters.
      Domain SettingsRequiredEnter Quick Query domain
      • must start with a lowercase English letter and must not end with a special character (-, .), using lowercase letters, numbers, and special characters (-, .) to enter 3 to 50 characters
      • {Quick Query name}.{configured domain} becomes the Quick Query access URL.
      Query engine typeRequiredSelect query engine type
      • Shared: A single query engine is shared among multiple users
      • Personal: Each user uses a separate engine
      Cluster sizeRequiredSelect resource capacity for cluster configuration
      • When the engine type is selected as Public
        • If Auto Scaling is set to Enabled, you can choose the cluster capacity from Small, Medium, Large, or Extra Large.
        • If Auto Scaling is not set to Enabled, you can configure the cluster capacity by specifying Replica, CPU, and Memory.
      • When the engine type is selected as Private
        • You can select the cluster capacity from Small, Medium, Large, or Extra Large.
      • Engine capacity (when Auto Scaling is enabled)
        • Small: 1Core, 4GB
        • Medium: 4Core, 16GB
        • Large: 8Core, 64GB
        • Extra Large: 16Core, 128GB
      • Engine capacity (when Auto Scaling is disabled)
        • Replica: can be set from 1 to 9, default: 1
        • CPU: can be set from 4 to 24 (allowed values: 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24), default: 4
        • Memory: can be set from 8 to 256 (allowed values: 8, 16, 32, 64, 128, 192, 256), default: 8
      Maximum number of concurrent queriesRequiredSelect the maximum number of queries to run simultaneously in Quick Query
      • Selectable values: 32, 64, 96, 128
      Data Service Console connectionRequiredEnter Data Service Console domain
      • that starts with a lowercase English letter and does not end with a special character (-, .)using lowercase letters, numbers, and special characters (-, .)to enter 3 to 50 characters
      Host AliasSelectionAdd host information to be linked with Quick Query (up to 20 total, including defaults)
      • After selecting Use, click the + button
      • Hostname: Enter 3–63 characters using lowercase letters, numbers, and special characters (-, .) in host name or domain format
      • IP: Enter in IP format
      • To delete, click the X button
      • The added host information can be used only if the firewall between the cluster and the server is open
      Table. Quick Query Service Information Input
    • In the Cluster Information Input area, enter or select the required information.
      Category
      Required
      Detailed description
      Cluster nameRequiredEnter cluster name
      • must start with a lowercase English letter and must not end with a special character (-), using lowercase letters, numbers, and special characters (-) enter 3 to 30 characters
      Control area settingRequired/Optional
      • Kubernetes version: Display Kubernetes version
        • You can upgrade the Kubernetes version after provisioning.
      • Public endpoint access: To enable access to the Kubernetes API server endpoint from outside, select Use and then enter the Access control IP range (cannot be changed after service request).
      • Control plane logging: Select whether to enable control plane logging
        • If you select Use, you can view the cluster control plane’s Audit/Event logs in Management > Cloud Monitoring > Log Analytics.
        • Log storage up to 1GB for all services in the project is provided for free, and logs exceeding 1GB are deleted sequentially.
      Network SettingsRequiredNetwork Connection Settings
      • VPC: Use the same VPC as the Data Service Console
      • Subnet: Select the subnet to use from the chosen VPC’s subnets
      • Security Group: After clicking Search, select a security group in the Select Security Group popup
      File Storage configurationRequiredSelect file storage volume to use in the cluster
      • Default Volume (NFS): After clicking Search, select file storage in the File Storage Selection popup
      Table. Quick Query Service Cluster Information Input
    • Node Pool Information Input Enter or select the required information in this area.
      Category
      Required status
      Detailed description
      Node pool configurationRequired/OptionalEnter detailed information for the node pool to add
      • * Items marked with an asterisk are required fields
        • If the Query Engine Type is Public and Auto Scaling is set to Disabled, only the Node Pool Configuration (Fixed) option can be configured.
        • Keypair: Select the authentication method used when connecting to the Virtual Server
      Table. Quick Query Service Node Pool Information Input
    • In the Additional Information Input area, enter or select the required information.
      Category
      Whether required
      Detailed description
      tagSelectionAdd Tag
      • Add Tag Click the button to create and add a tag, or add an existing tag.
      • You can add up to 50 tags.
      • The newly added tags will be applied after the service creation is completed.
      Table. Quick Query Service Additional Information Input
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.

    • When creation is complete, check the created resource on the Quick Query List page.

Quick Query Check detailed information

You can view and edit the complete list of resources and detailed information of the Quick Query service. The Quick Query Details page consists of Detailed Information, Tags, Activity Log tabs.

Follow these steps to view the detailed information of the Quick Query service.

  1. Click the All Services > Data Analytics > Quick Query menu. Navigate to the Service Home page of Quick Query.
  2. On the Service Home page, click the Quick Query menu. Navigate to the Quick Query list page.
  3. Quick Query List page: click the resource to view detailed information. You will be taken to the Quick Query Detail page.
    • Quick Query Details At the top of the page, status information and additional feature information are displayed.
      CategoryDetailed description
      Status displayStatus of user-created Quick Query
      • Creating: In progress
      • Running: Creation complete, service available
      • Updating: Updating settings
      • Terminating: Service termination in progress
      • Error: Error occurred during creation or service abnormal state
      Hosts file configuration informationButton to view and copy host file information for accessing Quick Query and Data Service Console
      Service terminationCancel service button
      Table. Quick Query Status Information and Additional Features

Detailed Information

Quick Query List page allows you to view detailed information of the selected resource and edit the information if needed.

CategoryDetailed description
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • means cluster SRN
Resource nameResource name
  • means the cluster name
Resource IDUnique resource ID in the service
constructorUser who created the service
Creation date and timeService creation date and time
editorUser who edited the service information
Modification dateDate and time the service information was modified
Quick Query nameQuick Query name
descriptionAdditional information or explanation about Quick Query
VersionQuick Query version
Service typeQuick Query Service Type
Query engine typeQuick Query engine type
Engine Spec
  • Whether to use Auto Scaling
  • Resource capacity for cluster configuration
Maximum number of concurrent queriesMaximum number of queries to run simultaneously in Quick Query
Domain SettingsQuick Query domain
Data Service ConsoleData Service Console domain
Host AliasHost information for Quick Query connection
Web URLWeb URLs of Data Service Console and Quick Query
Cluster nameCluster name of the configured servers
Installation node informationDetailed information of the installed node pool
Table. Quick Query Detailed Information Tab Items

tag

Quick Query List page lets you view the tag information of the selected resource, and add, modify, or delete it.

CategoryDetailed description
Tag listTag list
  • You can view the Key, Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the list of previously created Keys and Values
Table. Quick Query Tag Tab Items

Job History

You can view the operation history of the selected resource on the Quick Query List page.

CategoryDetailed description
Task History ListResource Change History
  • You can view the operation date and time, resource type, resource name, operation details, operation result, and operator information
  • Click the relevant resource in the Work History List. The Work History Details popup will open.
  • Provides detailed search functionality via the Detailed Search button.
Table. Quick Query Job History Tab Detailed Information Items

Quick Query Connect

Follow these steps to access Quick Query.

  1. Check the IP of the Windows system(PC) that will connect to Quick Query.
    • Since external access is required, you need to check the system’s public IP.
  2. Check that the IGW connection in the VPC where Quick Query is installed is enabled.
    • An Internet Gateway that can be connected must be configured for external access.
  3. Add the following to the Windows system’s hosts file. You can view it by clicking Hosts file setting information on the Quick Query detail screen.
    • Domain address of Data Service Console
    • Domain address of Data Service Console IAM
    • Domain address of Quick Query
  4. Add the following rule to the VPC IGW firewall you selected when applying for the Quick Query service.
    CategoryProtocolSourceTarget IPPort
    InboundTCPUser IPLoad Balancer service IP80,443
    Table. VPC IGW Firewall Rules
  5. Add the following rule to the Load Balancer Firewall you selected when applying for the Quick Query service.
    CategoryProtocolSourceTarget IPPort
    OutboundTCPUser IPLoad Balancer service IP80,443
    InboundTCPLoad Balancer’s Source NAT IPSubnet range of the Kubernetes Node Pool30000-32767
    TCPLoad Balancer’s Health Check IPSubnet range of the Kubernetes Node Pool30000-32767
    Table. Load Balancer Firewall Rules
  6. Add the following rule to the Security Group you selected when applying for the Quick Query service.
    CategoryProtocolTarget IPPort
    InboundTCPLoad Balancer’s Source NAT IP30000-32767
    TCPLoad Balancer’s Health Check IP30000-32767
    Table. Security Group Rules
  7. On the Windows system (PC) you want to connect to, launch the Chrome browser and then access the Quick Query URL.

Terminate Quick Query

You can cancel the unused service to reduce operating costs. However, canceling the service may immediately stop the running service, so you should thoroughly consider the impact of service interruption before proceeding with the cancellation.

To cancel Quick Query, follow the steps below.

  1. Click the All Services > Data Analytics > Quick Query menu. Go to the Service Home page of Quick Query.
  2. On the Service Home page, click the Quick Query menu. You will be taken to the Quick Query List page.
  3. On the Quick Query List page, select the resource to cancel, and click the Cancel Service button.
  4. After the termination is complete, check on the Quick Query list page whether the resource has been terminated.

3 - API Reference

API Reference

4 - CLI Reference

CLI Reference

5 - Release Note

Quick Query

2025.07.01
NEW Launch of the official version of Quick Query service
  • The Quick Query service, which allows you to easily analyze large-scale data using standard SQL, has been launched.