pekka@stripped wrote:
>>Which is totally unclear as to exactly how it will work. eg is it whole
>>tables only on disk, partitions of tables etc.
>
>
> Given _attributes_ on disk. No indexed attributes in 5.1.
> In particular PK must be in memory.
>
Is this the status of 5.1 at this time (i.e disk based storage is
functional)?
The reason being, I checked out 5.1(.3) to examine the new clustering
and partitioning features, However loading a table bigger than my
allocated datamemory is not working for me (see below). If this should
work, or is worth investigating further, then let me know and I'll log a
bug with the details
Cheers
Mark
--
mysql > LOAD DATA LOCAL INFILE '/data0/dump/fact0.dat'
> INTO TABLE fact0 FIELDS TERMINATED BY ',';
ERROR 1297 (HY000): Got temporary error 4010 'Node failure caused abort
of transaction' from NDBCLUSTER
$ ndb_3_error.log
Current byte-offset of file-pointer is: 568
Time: Monday 14 November 2005 - 11:27:01
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error,
programming
error or missing error message, please report a bug)
Error: 2341
Error data: DbtupIndex.cpp
Error object: DBTUP (Line: 67) 0x0000000a
Program: /usr/local/mysql/5.1/libexec/ndbd
Pid: 16765
Trace: /data0/myndb/5.1/ndb_3_trace.log.1
Version: Version 5.1.3 (alpha)
***EOM***
