Start Data Query
To use the Data Query service, the following preparations are required.
Prepare query result storage
To use the Data Query service, an Object Storage bucket is needed to store query results.
When a query is executed, result data is saved to a subdirectory of the user-defined Object Storage bucket.
First, create an Object Storage bucket and then set the result path in Query editor > Settings.
1. Create Object Storage bucket
- You must be using the Object Storage service and have a bucket created for query results.
- You can also use an existing bucket.
- Buckets can be managed via KakaoCloud Console > Beyond Storage Service > Object Storage.
- For more details, refer to the User guide.
caution
- Object Storage service charges apply separately. (View Object Storage pricing)
- Check the Lifecycle policy of the bucket used for Data Query. Query results may be deleted after a certain period depending on the policy.
For details, refer to Manage lifecycle policy.
2. Set Object Storage bucket permissions
- To store results, the Data Query service agent must have write access to the specified bucket.
- The service agent is automatically created when the Data Query service starts.
- For details, refer to Service agent account.
Target | Permission |
---|---|
User | Editor or higher |
Data Query service agent | Editor or higher |
Prepare data source
The Data Query service can load data from various sources.
Currently, Data Catalog and MySQL are supported.
1. Create Data Catalog source
- Data Query can query and load Hive data via the Data Catalog service.
- Catalogs can be created in KakaoCloud Console > Analytics > Data Catalog.
- Catalogs are automatically available without additional connection steps.
- For more information, refer to the Documentation.
2. Create MySQL data source
- Data Query can query and load data from MySQL databases.
- MySQL databases can be created in KakaoCloud Console > Data Store > MySQL.
- To connect to a MySQL database, you must perform data source creation.
- For more information on the MySQL service, refer to the Documentation.