MySQL Bugs: #47922: MySQL 5.1 source should no longer include ndb engine

Bug #47922	MySQL 5.1 source should no longer include ndb engine
Submitted:	8 Oct 2009 17:53	Modified:	4 Mar 2013 13:43
Reporter:	Andrew Hutchings	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
MySQL 5.1 source still contains the ndbcluster engine but it has not been updated in a very long time.  I believe it is not maintained and generally not supported and those that need it should be using 6.2/6.3/7.0.  Therefore it should probably be removed from the standard MySQL 5.1 source.

How to repeat:
./configure --with-plugins=ndbcluster
make
make install

Suggested fix:
Remove /storage/ndb and references to it in configure/make files

5.1 mainline contains cluster engine so that we get test coverage in mysql-test-run. This way we ensure server team not breaking ndb accidentally in sustaining and feature development. 

ndb will be merged back to server mainline eventually. 

But mainline should not be *released* with ndb.

Andrew,

was this what you were refering? (i.e the released src-tar-balls)
if yes, then this should be set to Server:Packaging
  else, this should be closed as not-a-bug

Yes, src-tar-balls.  Switched it to Server:Packaging

We cannot remove the cluster sources from the source tree, because that would make the checks mentioned by Bernhard impossible.
As a consequence, these sources will remain available in Launchpad.

If we exclude the cluster sources from a "make dist", we will make them unavailable to the internal tests using the Pushbuild2 mechanism, again preventing the checks which Bernhard mentions.

Having different "make dist" for internal and external purposes is no option, because this is controlled by the builtin logic of "automake"; we cannot easily duplicate that rule.

So my proposal is to set this to "Won't fix".

The concern about cluster sources becoming old in our general source tree could also be handled by doing a backmerge now and then, not just relying on some vague "eventually".

I have a proposal for a compromise:

Is it possible for ./configure to show a warning somewhere obvious (ie. at the end) that the cluster contained inside should not be used if it is selected as a build option?

I'm not sure how that will conflict with 6.x/7.x releases but it could help reduce the instances of customers and the community trying to use cluster from a 5.1 source build.

I checked "configure.in".
It should be rather trivial to add some text to the final message that is output only if cluster was part of the configure options.

I would ensure this happens in 5.1 only.

Please provide a draft text.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

The basic issue should be moot with 5.6, with Cluster now doing merges on a regular basis.