Skip to main content

MySQL LOAD DATA from csv file into partitioned table

MySQL LOAD DATA from .csv file into partitioned table:

MySQL load data into the MySQL partitioned table, from .csv file which has 63 column and table has 43 columns, column 43 of the table is loaddate and it's value will be current date. Here we are not loading some data from .csv file means skip data from .csv file and load selected data into the table.

Table created with column loaddate, loaddate is part of primary key, table is partitioned on loaddate:


CREATE TABLE CCB_SV_SVSEEK_1 (
Col_1,
Col_2,
Col_3,
Col_4, .... Col_42

 loaddate DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
 PRIMARY KEY(Col_1,Col_2,Col_3,Col_4,Col_5,LOADDATE),
 )
 PARTITION BY RANGE COLUMNS (LOADDATE)(
 PARTITION 2019_JAN VALUES LESS THAN ('2019-02-01') ,
 PARTITION 2019_FEB VALUES LESS THAN ('2019-03-01') , ... PARTITION 2019_DEC ....
 PARTITION 2019_ONWARDS VALUES LESS THAN MAXVALUE
);

Code to load data from .csv file to table:
LOAD DATA INFILE '/mysql/admin/scripts/<Table_Name>.csv' INTO TABLE <Schema_Name.Table_Name> FIELDS TERMINATED BY ',' LINES TERMINATED BY '\n'
(
Col_1,
Col_2,
Col_3,
Col_4, .... Col_42

@var44,
@var45, ... @var63

)
SET loaddate = CURRENT_TIMESTAMP;

Data is loaded in partition 2019_APR:
mysql> SELECT * FROM <Table_Name> PARTITION (2019_APR);
12 rows in set (0.00 sec)

Other partitions are empty:
mysql> SELECT * FROM <Table_Name> PARTITION (2019_JAN,2019_FEB, 2019_MAR, 2019_MAR,2019_MAY, 2019_JUN, 2019_JUL, 2019_AUG, 2019_SEP, 2019_OCT,2019_NOV, 2019_DEC);
Empty set (0.01 sec)


Note:  If you don't use  FIELDS TERMINATED BY ',' you could get error - ERROR 1406 (22001): Data too long for column

Comments

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...

MySQL slave Error_code: 1032 | MySQL slave drift | HA_ERR_KEY_NOT_FOUND

MySQL slave Error_code: 1032 | MySQL slave drift: With several MySQL, instance with master slave replication, I have one analytics MySQL, environment which is larger in terabytes, compared to other MySQL instances in the environment. Other MySQL instances with terabytes of data are running fine master, slave replication. But this analytics environment get started generating slave Error_code :1032. mysql> show slave status; Near relay log: Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_log_pos 5255306 Near master section: Could not execute Update_rows event on table <db_name>.<table_name>; Can't find record in '<table_name>', Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_l...

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...