missing data in partition hash by id
up vote
0
down vote
favorite
I met a issue in mysql table partition usage.
table create
CREATE TABLE `talk_record_gz` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`eid` int(10) unsigned NOT NULL DEFAULT '0',
`cc_number` varchar(128) NOT NULL DEFAULT '',
`gz_res_token` varchar(512) NOT NULL DEFAULT '',
`gz_file_name` varchar(512) NOT NULL DEFAULT '',
`gz_status` tinyint(2) NOT NULL DEFAULT '1' COMMENT '1=wait,2=uploading,3=success',
PRIMARY KEY (`id`),
KEY `idx_eid` (`eid`),
KEY `idx_ccnumber` (`cc_number`),
KEY `idx_token` (`gz_res_token`(255))
) ENGINE=InnoDB AUTO_INCREMENT=504238 DEFAULT CHARSET=utf8
/*!50100 PARTITION BY HASH (id)
PARTITIONS 10 */
problem:
execute sql below will get no data(YES, we should filter id as the table is split into partitions by hash[id], but for full search, the data should be find anyhow)
select * from talk_record_gz where cc_number='api00400013602154166222649626fD3conf_1541662225484' and eid=79362;
but if we remove filter eid=79632 as below
select * from talk_record_gz where cc_number='api00400013602154166222649626fD3conf_1541662225484';
we will get data as below
the eid(int) shown in picture above is exactly same as we add in first sql.
I assumed that issue is caused by "charater set", but not sure due to eid is type of int.
PAT:only special line will be missed by first sql,most of lines in this table can be searched by filter eid+cc_number.
any suggestion is appreciate.
mysql partition
add a comment |
up vote
0
down vote
favorite
I met a issue in mysql table partition usage.
table create
CREATE TABLE `talk_record_gz` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`eid` int(10) unsigned NOT NULL DEFAULT '0',
`cc_number` varchar(128) NOT NULL DEFAULT '',
`gz_res_token` varchar(512) NOT NULL DEFAULT '',
`gz_file_name` varchar(512) NOT NULL DEFAULT '',
`gz_status` tinyint(2) NOT NULL DEFAULT '1' COMMENT '1=wait,2=uploading,3=success',
PRIMARY KEY (`id`),
KEY `idx_eid` (`eid`),
KEY `idx_ccnumber` (`cc_number`),
KEY `idx_token` (`gz_res_token`(255))
) ENGINE=InnoDB AUTO_INCREMENT=504238 DEFAULT CHARSET=utf8
/*!50100 PARTITION BY HASH (id)
PARTITIONS 10 */
problem:
execute sql below will get no data(YES, we should filter id as the table is split into partitions by hash[id], but for full search, the data should be find anyhow)
select * from talk_record_gz where cc_number='api00400013602154166222649626fD3conf_1541662225484' and eid=79362;
but if we remove filter eid=79632 as below
select * from talk_record_gz where cc_number='api00400013602154166222649626fD3conf_1541662225484';
we will get data as below
the eid(int) shown in picture above is exactly same as we add in first sql.
I assumed that issue is caused by "charater set", but not sure due to eid is type of int.
PAT:only special line will be missed by first sql,most of lines in this table can be searched by filter eid+cc_number.
any suggestion is appreciate.
mysql partition
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I met a issue in mysql table partition usage.
table create
CREATE TABLE `talk_record_gz` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`eid` int(10) unsigned NOT NULL DEFAULT '0',
`cc_number` varchar(128) NOT NULL DEFAULT '',
`gz_res_token` varchar(512) NOT NULL DEFAULT '',
`gz_file_name` varchar(512) NOT NULL DEFAULT '',
`gz_status` tinyint(2) NOT NULL DEFAULT '1' COMMENT '1=wait,2=uploading,3=success',
PRIMARY KEY (`id`),
KEY `idx_eid` (`eid`),
KEY `idx_ccnumber` (`cc_number`),
KEY `idx_token` (`gz_res_token`(255))
) ENGINE=InnoDB AUTO_INCREMENT=504238 DEFAULT CHARSET=utf8
/*!50100 PARTITION BY HASH (id)
PARTITIONS 10 */
problem:
execute sql below will get no data(YES, we should filter id as the table is split into partitions by hash[id], but for full search, the data should be find anyhow)
select * from talk_record_gz where cc_number='api00400013602154166222649626fD3conf_1541662225484' and eid=79362;
but if we remove filter eid=79632 as below
select * from talk_record_gz where cc_number='api00400013602154166222649626fD3conf_1541662225484';
we will get data as below
the eid(int) shown in picture above is exactly same as we add in first sql.
I assumed that issue is caused by "charater set", but not sure due to eid is type of int.
PAT:only special line will be missed by first sql,most of lines in this table can be searched by filter eid+cc_number.
any suggestion is appreciate.
mysql partition
I met a issue in mysql table partition usage.
table create
CREATE TABLE `talk_record_gz` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`eid` int(10) unsigned NOT NULL DEFAULT '0',
`cc_number` varchar(128) NOT NULL DEFAULT '',
`gz_res_token` varchar(512) NOT NULL DEFAULT '',
`gz_file_name` varchar(512) NOT NULL DEFAULT '',
`gz_status` tinyint(2) NOT NULL DEFAULT '1' COMMENT '1=wait,2=uploading,3=success',
PRIMARY KEY (`id`),
KEY `idx_eid` (`eid`),
KEY `idx_ccnumber` (`cc_number`),
KEY `idx_token` (`gz_res_token`(255))
) ENGINE=InnoDB AUTO_INCREMENT=504238 DEFAULT CHARSET=utf8
/*!50100 PARTITION BY HASH (id)
PARTITIONS 10 */
problem:
execute sql below will get no data(YES, we should filter id as the table is split into partitions by hash[id], but for full search, the data should be find anyhow)
select * from talk_record_gz where cc_number='api00400013602154166222649626fD3conf_1541662225484' and eid=79362;
but if we remove filter eid=79632 as below
select * from talk_record_gz where cc_number='api00400013602154166222649626fD3conf_1541662225484';
we will get data as below
the eid(int) shown in picture above is exactly same as we add in first sql.
I assumed that issue is caused by "charater set", but not sure due to eid is type of int.
PAT:only special line will be missed by first sql,most of lines in this table can be searched by filter eid+cc_number.
any suggestion is appreciate.
mysql partition
mysql partition
asked Nov 9 at 4:29
qqzhou
164
164
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53219893%2fmissing-data-in-partition-hash-by-id%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown