A simple data-config.xml hitting a SQL db is all we need. Here is a
wordpress DB layout:
mysql> show tables;
+-----------------------+
| Tables_in_india |
+-----------------------+
| wp_comments |
| wp_links |
| wp_options |
| wp_postmeta |
| wp_posts |
| wp_term_relationships |
| wp_term_taxonomy |
| wp_terms |
| wp_usermeta |
| wp_users |
+-----------------------+
10 rows in set (0.00 sec)
mysql> describe wp_posts;
+-----------------------+---------------------+------+-----
+---------------------+----------------+
| Field | Type | Null | Key |
Default | Extra |
+-----------------------+---------------------+------+-----
+---------------------+----------------+
| ID | bigint(20) unsigned | NO | PRI |
NULL | auto_increment |
| post_author | bigint(20) | NO | |
0 | |
| post_date | datetime | NO | |
0000-00-00 00:00:00 | |
| post_date_gmt | datetime | NO | |
0000-00-00 00:00:00 | |
| post_content | longtext | NO | |
NULL | |
| post_title | text | NO | |
NULL | |
| post_category | int(4) | NO | |
0 | |
| post_excerpt | text | NO | |
NULL | |
| post_status | varchar(20) | NO | |
publish | |
| comment_status | varchar(20) | NO | |
open | |
| ping_status | varchar(20) | NO | |
open | |
| post_password | varchar(20) | NO |
| | |
| post_name | varchar(200) | NO | MUL
| | |
| to_ping | text | NO | |
NULL | |
| pinged | text | NO | |
NULL | |
| post_modified | datetime | NO | |
0000-00-00 00:00:00 | |
| post_modified_gmt | datetime | NO | |
0000-00-00 00:00:00 | |
| post_content_filtered | text | NO | |
NULL | |
| post_parent | bigint(20) | NO | |
0 | |
| guid | varchar(255) | NO |
| | |
| menu_order | int(11) | NO | |
0 | |
| post_type | varchar(20) | NO | MUL |
post | |
| post_mime_type | varchar(100) | NO |
| | |
| comment_count | bigint(20) | NO | |
0 | |
+-----------------------+---------------------+------+-----
+---------------------+----------------+
24 rows in set (0.01 sec)
On Nov 10, 2008, at 11:27 AM, Noble Paul നോബിള്
नोब्ळ् wrote:
I'm not sure what kind of interfaces WordPress expose. Does it have a
DB/REST end point?
If so, it would be very easy to write a sample data-config.xml for
wordpress.
--Noble
On Mon, Nov 10, 2008 at 8:13 PM, Grant Ingersoll
<[EMAIL PROTECTED]> wrote:
I don't know of anyone that has done this, but I would welcome it
as well.
I suspect the main issue is that most WP users live in a shared
hosting
world, where Java doesn't play very nicely.
That being said, it would be fairly easy to use the
DataImportHandler's feed
import for indexing (I think) and then it's just a matter of
pointing the
search box at the Solr instance, I suppose.
On Nov 6, 2008, at 11:19 PM, Stephen Weiss wrote:
Hi,
We recently implemented Solr for one major search component of our
site,
and now that this is complete we're turning to other areas of our
site to
see where Solr can help us improve results relevancy and
performance.
One major area where I think Solr could do a lot of good is to
replace
Wordpress's search function. Wordpress powers a solid 1/3 of our
site, and
moving this over could provide dramatic performance benefits. I
see there
is a Lucene plugin for WP but I have not seen any plugin yet using
Solr.
While I'm not terribly afraid of writing one (we've already
completely
replaced the built-in routine with our own plugin to optimize MySQL
searching), it would of course be even better if there was some
sort of
plugin already out there (why reinvent the wheel)? Somehow it
just seems
strange that no one would have tried this yet.
I figure if anyone knows, someone on this list knows. Thanks for
any
info!
--
Steve
--------------------------
Grant Ingersoll
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
--
--Noble Paul
