Comments for Enterprise Search, System Administration, and Cloud Computing http://www.tnrglobal.com/blog/ Thu, 20 May 2010 19:04:48 -0400 http://wordpress.org/?v=2.8.6 hourly 1 Comment on How to get the MongoDB server version using PyMongo by Ross Farinella http://www.tnrglobal.com/blog/2010/05/how-to-get-the-mongodb-server-version-using-pymongo/cpage/1/#comment-271 Ross Farinella Thu, 20 May 2010 19:04:48 +0000 http://www.tnrglobal.com/blog/2010/05/how-to-get-the-mongodb-server-version-using-pymongo/#comment-271 Updated code to include the slicker-looking "server_info()" call -- thanks Mike! Updated code to include the slicker-looking “server_info()” call — thanks Mike!

]]> Comment on How to get the MongoDB server version using PyMongo by Mike Dirolf http://www.tnrglobal.com/blog/2010/05/how-to-get-the-mongodb-server-version-using-pymongo/cpage/1/#comment-270 Mike Dirolf Thu, 20 May 2010 18:22:40 +0000 http://www.tnrglobal.com/blog/2010/05/how-to-get-the-mongodb-server-version-using-pymongo/#comment-270 Good tip! You can also use the server_info() method on a Connection instead of running the command manually. There are some tools (meant just for testing, but might be worth a look) that do this in the `test/version.py` file in the PyMongo source tree. Good tip! You can also use the server_info() method on a Connection instead of running the command manually. There are some tools (meant just for testing, but might be worth a look) that do this in the `test/version.py` file in the PyMongo source tree.

]]> Comment on How to create a duplicate ESP collection without re-crawling! by Natasha http://www.tnrglobal.com/blog/2010/03/how-to-create-a-duplicate-esp-collection-without-re-crawling/cpage/1/#comment-229 Natasha Tue, 04 May 2010 20:34:31 +0000 http://www.tnrglobal.com/blog/2010/03/how-to-create-a-duplicate-esp-collection-without-re-crawling/#comment-229 thanks thanks

]]> Comment on MySQL Error: BLOB/TEXT used in key specification without a key length by Jeff Peck http://www.tnrglobal.com/blog/2009/10/mysql-error-blobtext-used-in-key-specification-without-a-key-length/cpage/1/#comment-99 Jeff Peck Thu, 04 Feb 2010 02:40:27 +0000 http://www.tnrglobal.com/blog/2009/10/mysql-error-blobtext-used-in-key-specification-without-a-key-length/#comment-99 That's a really clever way to access fields in a database by a URL key. Just thinking about it, I am noticing... to optimize this even further, you might want to store that MD5 hash in two BIGINT UNSIGNED fields with a single index over them (if you are not doing it that way already). Storing them in CHAR(32) fields uses 256 bits per row whereas two BIGINTs are only 128 bits total, which is all that you need to store an MD5 hash. The may not be a big deal for space, but should make a noticeable difference in the performance. This would be the query to accomplish the insert in MySQL: [code] INSERT INTO `my_url_table` (`id_1`, `id_2`) VALUES (cast(conv(substring(md5("www.hugeurl.com"),1,16),16,10) as unsigned integer),cast(conv(substring(md5("www.hugeurl.com"),17,32),16,10) as unsigned integer)) [/code] ... where id_1 and id_2 are the primary keys. Note the difference in substring() from 1 to 16 and from 17 to 32 to evenly slice the hash. Another approach might be to use an CHAR(16) field and convert the hex md5 hash into ASCII. Either way, I think the idea to access fields by their URL as a hash is a great idea! Thanks. That’s a really clever way to access fields in a database by a URL key.

Just thinking about it, I am noticing… to optimize this even further, you might want to store that MD5 hash in two BIGINT UNSIGNED fields with a single index over them (if you are not doing it that way already).

Storing them in CHAR(32) fields uses 256 bits per row whereas two BIGINTs are only 128 bits total, which is all that you need to store an MD5 hash. The may not be a big deal for space, but should make a noticeable difference in the performance.

This would be the query to accomplish the insert in MySQL:

[code]
INSERT INTO `my_url_table` (`id_1`, `id_2`) VALUES (cast(conv(substring(md5("www.hugeurl.com"),1,16),16,10) as unsigned integer),cast(conv(substring(md5("www.hugeurl.com"),17,32),16,10) as unsigned integer))
[/code]

… where id_1 and id_2 are the primary keys. Note the difference in substring() from 1 to 16 and from 17 to 32 to evenly slice the hash.

Another approach might be to use an CHAR(16) field and convert the hex md5 hash into ASCII.

Either way, I think the idea to access fields by their URL as a hash is a great idea! Thanks.

]]> Comment on Integrate custom services with the Fast ESP Node Controller by andy http://www.tnrglobal.com/blog/2010/01/integrate-custom-services-with-the-fast-esp-node-controller/cpage/1/#comment-100 andy Wed, 13 Jan 2010 05:00:26 +0000 http://www.tnrglobal.com/blog/2010/01/integrate-custom-services-with-the-fast-esp-node-controller/#comment-100 Thankyou for visiting www.fastesphelp.com Thankyou for visiting http://www.fastesphelp.com

]]>