lp:mysql-fabric

Branch merges

Propose for merging

2 branches proposed for merging into this one.

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

240. By Alfranio Correia <email address hidden> on 2014-07-10

Releasing version 1.4.4

239. By Alfranio Correia <email address hidden> on 2014-07-10

Fixed dependency on the connector python.

238. By Israel Gomez on 2014-07-09

BUG#18904014 : mysqlfabric manage setup can't find configuration file

The freeze version of mysqlfabric (mysqlfabric.exe) is trying to locate the
configuration file outside of the installation folder. This fix corrects the
default location of fabric configuration file inside the installation folder
specified on mysqlfabric script. The change requires the MSI build mechanism
to create a msi package that will install fabric.cfg to a newer location (old
location with "scripts" folder removed, i.e., from
C:\Program...\MySQL\MySQL Utilities 1.4.3\scripts\etc\mysql\fabric.cfg
to C:\Program...\MySQL\MySQL Utilities 1.4.3\etc\mysql\fabric.cfg).

In addition, the patch for utilities will include a shortcut in the start menu,
Start Menu -> Programs -> MySQL -> MySQL Utilities ->
'MySQL Fabric configuration file' targeting:
"C:\MySQL\MySQL Utilities-fabric\etc\mysql\fabric.cfg".

237. By Narayanan Venkateswaran <email address hidden> on 2014-07-08

Bug#18669231: SHARDING PRUNE ISSUE WITH 20MN RECORDS

Prune was taking a very long time when the number of records that
needed to be pruned was a very large value (for e.g.
20MN records). This was caused by the DELETEs taking a very
long time when the data is very huge.

This can be avoided by performing the DELETEs in small bunches,
(i.e.) by setting a LIMIT on the number of records deleted at
any time.

236. By Alfranio Correia <email address hidden> on 2014-07-07

BUG#72818: BUG#18874603: THE --DAEMONIZE OPTION IN "MYSQLFABRIC MANAGE START" IS BROKEN

If you try to use the --daemonize option in "mysqlfabric manage start", the
following error is produced:

$mysqlfabric manage start --daemonize
mysqlfabric: error: no such option: --daemonize

This happening because the options are defined upon the optional parameters
found in the command's execute or dispatch methods. If the execute method
exists, its optional parameters are used. Otherwise, the optional parameters
in the dispatch method are used.

The daemonize is broken because an execute method was introduced in the
Command class which is inherited by the other commands and thus any dispatch
method is ignored.

This changed was introduced by the following patch:

revno: 227 [merge]
committer: Alfranio Correia <email address hidden>
branch nick: mysql-hub
timestamp: Mon 2014-04-14 19:25:34 +0100

To fix the issue, we have reverted part of the previous patch. This
solution is not ideal though and we will improve this in the future.
Any ideal solution should:

   . Look at either the dispatch or execute method but it should not look
     at both methods as the current solution does. This is error prone as
     you have seen.

   . Allow users to define commands without any magic (.e.g. See Martin
     Arrieta suggestion in the bug report). Currently this is not working.

235. By Mats Kindahl on 2014-05-23

Releasing 1.4.3rc2

234. By Narayanan Venkateswaran <email address hidden> on 2014-05-23

Bug#18824565:SHARD MOVE AND SPLIT FAILS IF PASSWORD IS PROVIDED FOR CLIENT IN FABRIC.CFG

Using a fabric setup with a valid password in the fabric.cfg client section
was causing shard move and shard split to fail. This was because of erroneous
invocation of the mysql client command line.

This has been fixed by removing the misplaced mysql client parameter that
was being passed while calling the mysql client.

233. By Mats Kindahl on 2014-05-13

Releasing version 1.4.2

232. By Mats Kindahl on 2014-05-13

Merging with 1.4 branch

231. By Mats Kindahl on 2014-05-13

Fixing CHANGELOG diff