Issue #5993 has been updated by Daniel Pittman.

Nigel Kersten wrote:
> We definitely have people with much longer fields than this.

…and our work-around for non-NDB engines that limits that index to 50 
characters is not available, either, since NDB doesn't work with that.  That 
said, we don't use any unique indexing on the field, so if you were willing to 
sacrifice search performance you could just not index that field.

Er, no promises on performance, by the way: I have not checked if this index is 
actually worth anything in practice, or anything like that, although it is the 
primary search point for the table, so I would guess it usually is.

----------------------------------------
Feature #5993: Puppet on mysql NDB cluster
https://projects.puppetlabs.com/issues/5993

Author: Karl Pietri
Status: Needs More Information
Priority: Low
Assignee: Nigel Kersten
Category: stored configuration
Target version: 
Affected Puppet version: 0.25.5
Keywords: 
Branch: 


The only minor issue for running puppet with its backend database on mysql ndb 
cluster is that the resources.title column is a text column and also part of an 
index which ndb forbids.  I believe this would be not a very hard problem to 
fix as after analyzing my database i noticed the max character length was only 
100, but i can see why the field was picked as a text column for longer 
resource (ie long path) names.  Perhaps there is a easy way to fix this one 
issue (perhaps at the expense of duplicating the column to a full one and a 
partial one) and be able to easily and safely use puppet on ndb.  Unfortunately 
i am not familiar with the actual puppet code (or very familiar with ruby at 
all), but i will be looking in to a way to patch this, so I thought I would 
open a feature request for it in case someone might be able to do it quickly or 
have ideas.

    Specific error:
    mysql> alter table resources engine=ndb;
    ERROR 1073 (42000): BLOB column 'title' can't be used in key specification 
with the used table type




-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to