Mohammad, This is the main idea, but things can get quite complicated.
In addition, do you need to do incremental indexing? Do you need to delete duplicates? How would you manage deleted documents in the database? Will taking down the server while indexing affect you? ... You are welcome to take a look at DBSight. Here is a demo that you can create a scalable lucene database search in 3 minutes. http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes -- Chris Lu ------------------------- Instant Scalable Full-Text Search On Any Database/Application site: http://www.dbsight.net demo: http://search.dbsight.com Lucene Database Search in 3 minutes: http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes On 3/31/07, Erick Erickson <[EMAIL PROTECTED]> wrote:
Well, don't do it that way <G>..... I'm assuming that you have some SQL statement like "for each entry in table 1, find all the related info", and what you're failing to retrieve is the result. So, try something like creating a SQL statement that selects the ID for table 1 and write it to a file. At the end of this, you'll have a list of all the IDs from table 1. Then, read those in one at a time and execute your query for use in indexing on one row at a time. In other words, iterate over each row rather than try to execute it in one massive statement. Erick On 3/31/07, Mohammad Norouzi <[EMAIL PROTECTED]> wrote: > > Hi all > I am going to index our database. one approach is to join them and then > index the fields. but the information are very large say more than 3 > millions. so the Sql Server fails to select them. > > I want to know if anyone has such this experience to indexing huge > information of database using lucene. > > can anyone give me some advice? > > -- > Regards, > Mohammad >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
