MySQL Cluster 6.3.24

Izasao MySQL Cluster 6.3.24 .. sta reci, MySQL Cluster je production quality vec dugo vremena, 6.3.24 dolazi sa par ispravljenih bagova:
• Bug #29574 – API Test for 29501 with undo file = (5*1024) cause Ndbd FS inconsistency (lgman)
• Bug #34268 – Keyboard tabbing sequence incorrect when editing a table
• Bug #37934 – Partition pruning doesn’t work for all queries in DBT2
• Bug #38793 – NDBAPI : EQ never sent for Index scan bounds
• Bug #39540 – ndb_restore crash while restoring log from different endian
• Bug #42238 – NDBAPI : NdbRecord insert permits key column value ambiguity
• Bug #42857 – Got error 4541 ‘IndexBound has no bound information’ from NDBCLUSTER
• Bug #43069 – GCP stop in rather simple setup
• Bug #43224 – ndbmtd refuses to restart due to node id allocation failure
• Bug #43226 – Unique index build can fail with internal error after internal retry
• Bug #43256 – Bug#39026 got re-surrected
• Bug #43409 – ndb_restore* tests fail on big endian architectures(PowerPC, Sparc)
• Bug #43567 – TimeBetweenLocalCheckpoints is not time-between but rather time inbetween
• Bug #43590 – NDBAPI : Default NdbRecords can overlap null bits and data
• Bug #43752 – ndb: spurious event operation ref count mismatch during nodre restart
• Bug #43754 – Spurious 723 during createEventOperation in presence of node failure
• Bug #43802 – NDBAPI : NdbApi created bit field null bits incorrectly handled
• Bug #43877 – misplaced typedef warning in NdbDictionaryImpl.hpp
• Bug #43888 – ndbrequire fail in DBDIH during other node failures
• Bug #43891 – NULL bit offset not taken into account
• Bug #44015 – Abort of insert+delete can lead to committed read scan reading inconsistent data
• Bug #44099 – Scan can timeout incorrectly if low selectivit