Bug #29699 ndb_blob_partition segv for range partitioning
Submitted: 10 Jul 2007 20:46 Modified: 4 Jan 2008 16:02
Reporter: Tomas Ulin Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.2 OS:Any
Assigned to: Mattias Jonsson CPU Architecture:Any

[10 Jul 2007 20:46] Tomas Ulin
Description:
mysql-test-run: WARNING: Forcing kill of process 25405
ndb_blob_partition             [ fail ]

Errors are (from /home/tomas/mysql-5.2-ndb/mysql-test/var/log/mysqltest-time) :
mysqltest: At line 90: query 'delete from t1 where c < 3' failed: 2013: Lost connection to MySQL server during query
(the last lines may be the most important ones)

How to repeat:
.
[16 Jul 2007 14:20] Ingo Strüwing
Stack backtrace:

#3  <signal handler called>
#4  get_partition_set sql_partition.cc:3526
#5  ha_ndbcluster::read_range_first_to_buf ha_ndbcluster.cc:4170
#6  ha_ndbcluster::read_range_first ha_ndbcluster.cc:4240
#7  handler::multi_range_read_next handler.cc:3420
#8  ha_ndbcluster::multi_range_read_next ha_ndbcluster.cc:9948
#9  QUICK_RANGE_SELECT::get_next opt_range.cc:8474
#10 rr_quick records.cc:292
#11 mysql_delete sql_delete.cc:254
#12 mysql_execute_command sql_parse.cc:2688
#13 mysql_parse "delete from t1 where c < 3" sql_parse.cc:5309

Frame #4 points at

3526   if ((index < MAX_KEY) && 
3527        key_spec->flag == (uint)HA_READ_KEY_EXACT &&
3528        part_info->some_fields_in_PF.is_set(index))

Here 'key_spec' is NULL.

Version 5.2.5

NOTE: I am going to disable ndb_blob_partition in 5.2. Please re-enable after fixing this.