- Quick Start
- Table Design
- Data Loading
- Data Export
- Using StarRocks
- SQL Reference
- User Account Management
- Cluster Management
- ADMIN CANCEL REPAIR
- ADMIN CHECK TABLET
- ADMIN REPAIR
- ADMIN SET CONFIG
- ADMIN SET REPLICA STATUS
- ADMIN SHOW CONFIG
- ADMIN SHOW REPLICA DISTRIBUTION
- ADMIN SHOW REPLICA STATUS
- ALTER SYSTEM
- CANCEL DECOMMISSION
- CREATE FILE
- DROP FILE
- INSTALL PLUGIN
- SHOW BACKENDS
- SHOW BROKER
- SHOW FRONTENDS
- SHOW FULL COLUMNS
- SHOW INDEX
- SHOW PLUGINS
- SHOW TABLE STATUS
- SHOW FILE
- UNINSTALL PLUGIN
- ALTER DATABASE
- ALTER TABLE
- ALTER VIEW
- ALTER RESOURCE
- CANCEL BACKUP
- CANCEL RESTORE
- CREATE DATABASE
- CREATE INDEX
- CREATE MATERIALIZED VIEW
- CREATE REPOSITORY
- CREATE RESOURCE
- CREATE TABLE AS SELECT
- CREATE TABLE LIKE
- CREATE TABLE
- CREATE VIEW
- CREATE FUNCTION
- DROP DATABASE
- DROP INDEX
- DROP MATERIALIZED VIEW
- DROP REPOSITORY
- DROP RESOURCE
- DROP TABLE
- DROP VIEW
- DROP FUNCTION
- SHOW RESOURCES
- SHOW FUNCTION
- TRUNCATE TABLE
- ALTER ROUTINE LOAD
- BROKER LOAD
- CANCEL LOAD
- GROUP BY
- PAUSE ROUTINE LOAD
- RESUME ROUTINE LOAD
- ROUTINE LOAD
- SHOW ALTER
- SHOW BACKUP
- SHOW DATA
- SHOW DATABASES
- SHOW DELETE
- SHOW DYNAMIC PARTITION TABLES
- SHOW EXPORT
- SHOW LOAD
- SHOW PARTITIONS
- SHOW PROPERTY
- SHOW REPOSITORIES
- SHOW RESTORE
- SHOW ROUTINE LOAD
- SHOW ROUTINE LOAD TASK
- SHOW SNAPSHOT
- SHOW TABLES
- SHOW TABLET
- SHOW TRANSACTION
- SPARK LOAD
- STOP ROUTINE LOAD
- STREAM LOAD
- Data Types
- Auxiliary Commands
- Function Reference
- Date Functions
- Geographic Functions
- String Functions
- JSON Functions
- Aggregate Functions
- Bitmap Functions
- Array Functions
- cast function
- hash function
- Cryptographic Functions
- Math Functions
- Utility Functions
- System variables
- Error code
- System limits
- SQL Reference
- Build in Docker
- Manage a cluster
- Scale in and out
- Backup and restore
- Deploy StarRocks with StarGo
- Data Recovery
- Query planning
- Monitor and alert
- User privilege
- Resource Management
- Release Notes
This topic provides answers to some general questions.
Both are variable-length data types. When you store data of the same length, VARCHAR (32) and STRING occupy the same storage space.
To solve this problem, perform the following steps:
For example, there is a file named original, whose text is garbled. The character set of this file is ISO-8859-1. Run the following code to obtain the character set of the file.
file --mime-encoding origin.txt origin.txt：iso-8859-1
iconvcommand to convert the character set of this file into UTF-8.
iconv -f iso-8859-1 -t utf-8 origin.txt > origin_utf-8.txt
After the conversion, the text of this file still appears garbled. You can then regrade the character set of this file as GBK and convert the character set into UTF-8 again.
iconv -f gbk -t utf-8 origin.txt > origin_utf-8.txt
For VARCHAR(n), StarRocks defines "n" by bytes and MySQL defines "n" by characters. According to UTF-8, one Chinese character is equal to three bytes. When StarRocks and MySQL define "n" as the same number, MySQL saves three times as many characters as StarRocks.
No, only DATE, DATETIME, and INT are supported.
Execute the SHOW DATA statement to see the corresponding storage space. You can also see the data volume, the number of copies, and the number of rows.
Note: There is a time delay in data statistics.
To request a quota increase, run the following code:
ALTER DATABASE example_db SET DATA QUOTA 10T;
StarRocks 2.2 and later support updating specific fields in a table by using the primary key model. StarRocks 1.9 and later support updating all fields in a table by using the primary key model. For more information, see Primary key model in StarRocks 2.2.
Execute the SWAP WITH statement to swap the data between two tables or two partitions. The SWAP WITH statement is more secure than the INSERT OVERWRITE statement. Before you swap the data, check the data first and then see whether the data after the swapping is consistent with the data before the swapping.
Swap two tables: For example, there is a table named table 1. If you want to replace table 1 with another one, perform the following steps:
Create a new table named table 2.
create table2 like table1;
Use Stream Load, Broker Load, or Insert Into to load data from table 1 into table 2.
Replace table 1 with table 2.
ALTER TABLE table1 SWAP WITH table2;
By doing so, the data is loaded accurately into table 1.
Swap two partitions: For example, there is a table named table 1. If you want to replace the partition data in table 1, perform the following steps:
Create a temporary partition.
ALTER TABLE table1 ADD TEMPORARY PARTITION tp1 VALUES LESS THAN("2020-02-01");
Load the partition data from table 1 into the temporary partition.
Replace the partition of table 1 with the temporary partition.
ALTER TABLE table1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
This error occurs due to BDBJE's bug. To solve this problem, update the BDBJE version to 1.17 or later.
msg:Broker list path exception path=hdfs://172.31.3.136:9000/user/hive/warehouse/zltest.db/student_info/*, broker=TNetworkAddress(hostname:172.31.4.233, port:8000)
Contact the StarRocks technical support and check whether the address and port of the namenode are correct and whether you have permission to access the address and port of the namenode.
This error "get hive partition metadata failed" occurs when I query data from a new Apache Hive table
msg:get hive partition meta data failed: java.net.UnknownHostException: emr-header-1.cluster-242
Ensure that the network is connected and upload the host file to each backend (BE) in your StarRocks cluster.
This error "do_open failed. reason = Invalid ORC postscript length" occurs when I access ORC external table in Apache Hive
The metadata of the Apache Hive is cached in the FEs. But there is a two-hours time lag for StarRocks to update the metadata. Before StarRocks finishes the update, If you insert new data or update data in the Apache Hive table, the data in HDFS scanned by the BEs and the data obtained by the FEs are different. Therefore, this error occurs.
MySQL [bdp_dim]> select * from dim_page_func_s limit 1; ERROR 1064 (HY000): HdfsOrcScanner::do_open failed. reason = Invalid ORC postscript length
To solve this problem, perform one of the following operations:
- Upgrade your current version to StarRocks 2.2 or later.
- Manually refresh your Apache Hive table. For more information, see Metadata caching strategy.
The default authentication plugin of MySQL 8.0 is caching_sha2_password. The default authentication plugin of MySQL 5.7 is mysql_native_password. This error occurs because you use the wrong authentication plugin.
To solve this problem, perform one of the following operations:
- Connect to the StarRocks.
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'yourpassword';
- Modify the
vim my.cnf [mysqld] default_authentication_plugin=mysql_native_password
If you execute the DROP TABLE statement to delete a table, StarRocks takes a while to release the allocated disk space. To release the allocated disk space immediately, execute the DROP TABLE FORCE statement to delete a table. When you execute the DROP TABLE FORCE statement, the StarRocks deletes the table directly without checking whether there are unfinished events in it. We recommend that you execute the DROP TABLE FORCE statement with caution. Because once the table is deleted, you cannot restore it.
select current_version(); command or the CLI command
sh bin/show_fe_version.sh to view the current version.
FEs are used to store metadata. You can set the memory size of an FE based on the number of tablets. In StarRocks, you can set the memory size of an FE to 20 GB at most. 10 million tablets occupy about 20 GB of an FE memory.
StarRocks supports querying data by using multiple threads. Query time refers to the time used by multiple threads to query data.
You can test the concurrency limitations based on the actual business scenarios or simulated business scenarios. According to the feedback of some users, maximum of 20,000 QPS or 30,000 QPS can be achieved.
The speed to read disks for the first query relates to the performance of disks. After the first query, the page cache is generated for the subsequent queries, so the query is faster than before.
StarRocks supports single node deployment, so you need to configure at least one BE. BEs need to be run with AVX2, so we recommend that you deploy BEs on machines with 8-core and 16GB or higher configurations.
You can create a new user account and then set the data permission by granting permissions on the table query to the user.
The report is only submitted to the leader FE for access.
show create table xxx command.
Only StarRocks 2.1 or later version supports specifying the default value for a function. For versions earlier than StarRocks 2.1, you can only specify a constant for a function.
- Other FAQs
- Do VARCHAR (32) and STRING occupy the same storage space?
- Do VARCHAR (32) and STRING perform the same for the data query?
- Why do TXT files imported from Oracle still appear garbled after I set the character set to UTF-8？
- Is the length of STRING defined by MySQL the same as that defined by StarRocks?
- Can the data type of partitioned fields of a table be FLOAT, DOUBLE, or DECIMAL?
- How to check the storage space that is occupied by the data in a table?
- How to request a quota increase for the StarRocks database?
- Does StarRocks support updating particular fields in a table by executing the UPSERT statement?
- How to swap the data between two tables or two partitions？
- This error "error to open replicated environment, will exit" occurs when I restart a frontend (FE)
- This error "Broker list path exception" occurs when I query data from a new Apache Hive table
- This error "get hive partition metadata failed" occurs when I query data from a new Apache Hive table
- This error "do_open failed. reason = Invalid ORC postscript length" occurs when I access ORC external table in Apache Hive
- This error "caching_sha2_password cannot be loaded" occurs when I connect external tables of MySQL
- How to release disk space immediately after deleting a table?
- How to view the current version of StarRocks?
- How to set the memory size of an FE?
- How does StarRocks calculate its query time?
- Does StarRocks support setting the path when I export data locally?
- What are the concurrency upper limits of StarRocks?
- Why is the first-time SSB test performance of StarRocks slower than that done the second time?
- How many BEs need to be configured at least for a cluster?
- How to set data permissions when I use Apache Superset to visualize the data in StarRocks？
- Why does the profile fail to display after I set is_report_success to true?
- How to check field annotations in the tables of StarRocks?
- When I create a table, how to specify the default value for the NOW() function?