I am doing that but the API is in experimental stage. Not sure to use it or not. BTW can you also let me know how clustering works on Windows OS cos I saw clustering scripts for Unix OS bundled out with Solr release.
-----Original Message----- From: Noble Paul നോബിള് नोब्ळ् [mailto:[EMAIL PROTECTED] Sent: Friday, October 31, 2008 11:37 AM To: solr-user@lucene.apache.org Subject: Re: Using Solrj First of all you need to index your data in Solr. I suggest DataImportHandler because it can help you join multiple tables and index data On Fri, Oct 31, 2008 at 10:20 AM, Raghunandan Rao <[EMAIL PROTECTED]> wrote: > Thank you so much. > > Here goes my Use case: > > I need to search the database for collection of input parameters which > touches 'n' number of tables. The data is very huge. The search query itself > is so dynamic. I use lot of views for same search. How do I make use of Solr > in this case? > > -----Original Message----- > From: Erick Erickson [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 30, 2008 7:01 PM > To: solr-user@lucene.apache.org > Subject: Re: Using Solrj > > Generally, you need to get your head out of the database world and into > the search world to be successful with Lucene. For instance, one > of the cardinal tenets of database design is to normalize your > data. It goes against every instinct to *denormalize* your data when > creating an Lucene index explicitly so you do NOT have to think > in terms of joins or sub-queries. Whenever I start thinking this > way, I try to back up and think again. > > Both your posts indicate to me that you're thinking in database > terms. There are no views in Lucene, for instance. You refer > to tables. There are no tables in Lucene, there are only documents > with various numbers of fields. You could conceivable make your index > look like a database by creatively naming your document fields. But > that doesn't play to the strengths of Lucene *or* the database. > > In fact, there is NO requirement that documents have the *same* fields. > Which is really difficult to get into when thinking like a DBA. > > Lucene is designed to search text. Fast and well. It is NOT intended to > efficiently manipulate relationships *between* documents. There > are various hybrid solutions that people have used. That is, put the > data you really need to do text searching on in a Lucene index, > along with enough data to be able to get the *rest* of what you need > from your database. But it all depends upon the problem you're trying to > solve. > > But as Noble says, all this is too general to be really useful, you need > to provide quite more detail about the problem you're trying to > solve to get useful recommendations. > > Best > Erick > > On Thu, Oct 30, 2008 at 8:50 AM, Raghunandan Rao < > [EMAIL PROTECTED]> wrote: > >> Thanks Noble. >> >> So you mean to say that I need to create a view according to my query and >> then index on the view and fetch? >> >> -----Original Message----- >> From: Noble Paul നോബിള് नोब्ळ् [mailto:[EMAIL PROTECTED] >> Sent: Thursday, October 30, 2008 6:16 PM >> To: solr-user@lucene.apache.org >> Subject: Re: Using Solrj >> >> hi , >> There are two sides to this . >> 1. indexing (getting data into Solr) SolrJ or DataImportHandler can be >> used for this >> 2.querying . getting data out of solr. Here you do not have the choice >> of joining multiple tables. There only one index for Solr >> >> >> >> On Thu, Oct 30, 2008 at 5:34 PM, Raghunandan Rao >> <[EMAIL PROTECTED]> wrote: >> > Hi, >> > >> > I am trying to use Solrj for my web application. I am indexing a table >> > using the @Field annotation tag. Now I need to index or query multiple >> > tables. Like, get all the employees who are managers in Finance >> > department (interacting with 3 entities). How do I do that? >> > >> > >> > >> > Does anyone have any idea? >> > >> > >> > >> > Thanks >> > >> > >> >> >> >> -- >> --Noble Paul >> > -- --Noble Paul
