MySQL Bugs: #17805: Cluster_replication database should be renamed to just cluster

Bug #17805	Cluster_replication database should be renamed to just cluster
Submitted:	28 Feb 2006 20:46	Modified:	2 Mar 2006 6:05
Reporter:	Jonathan Miller	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1.8	OS:	Linux (Linux)
Assigned to:	Tomas Ulin	CPU Architecture:	Any

Description:
The cluster team had discussed the fact that the system level cluster_replication database was going to be used for more then just replication and that we should rename the database to cluster. This would make it clear to customers and would not cause upgrade issue that might be seen waiting to do the rename in later releases.

To date the database still has not been renamed. Renaming this later in the project would cause a delay in QA for having to rebuild test that use this database for slave syncs and may cause issues from some customer currently using cluster replication.

This bug is being created to make sure this it talked about and a decision to move forward or to aborts it made.

How to repeat:
n/a

Suggested fix:
rename the database.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/3310

pushed to 5.1.8

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Feature change documented in 5.1.8 changelog, 5.1 Manual Cluster chapter. Closed.