Alexander:
You might also look through the mail archive for "database". There have been
several dicsussions on that topic with input from people far more
knowledgable than me that you might find relevant .
Erick
Alexander,
to solve your problem, you have to carefully understand how lucene
handles fields.
Lucene can handle the value of the document fields in different ways;
the different aspects to care of are:
- indexing: whether the value is indexed or not. It may look strange
to store data on a Lucene
For your date interval search requirement, Lucene can do range search.
You need to use ConstantScoreRangeQuery for better performance.
You'd better select all your additional attributes into the lucene
document. This will lead to some data duplications, especially look up
values. But it's a trade
Alexander Mashtakov wrote:
But, the database is going to be big enough, and the list of IDs
returned by
Lucene too. This
may cause high memory usage and slow sql query speed (for instance 1000 IDs
in "IN (id1, id2 ...)"
sql filter)
For this part, I recommend using a working table to hold the
Thank you *Giulio,*
I read some information about this approach. Is it possible to store in
Lucene field
several FKs ? For example, a document has serveral mappings to category
table (N:M).
The other question is about dates - is it possible to query Lucene for date
interval (from -MM-DD to YY
If I'm understanding you correctly, you're using Lucene to store IDs and
index the columns that would normally be full-text indices in MySQL, then
use the IDs to retrieve the information from the database. This is more of a
MySQL issue than a Lucene issue, but it suggests a flaw in your approach:
Hi Alexander,
if the set of foreign keys you are using to filter the lucene results
with some SQL query, I suggest you to include the foreign keys values
as additional lucene fields, and let lucene return you the exact set
of document IDs.
I had excellent results with this technique.
Hope this
Hi folks,
I'm looking for a solution/best practices concerning Lucene and SQL database
integration.
The database (MySQL) is already developed and contains data. I've tried
MySQL full-text
search, but it's quite slow and doesn't have the possibility to intergate
custom analyzers.
Phrase search is
George -
There are a number of SQL Server specific ways you can do this. Email me
off-list as the solution is not relevant to Lucene.
-- j
On 12/2/05, George Abraham <[EMAIL PROTECTED]> wrote:
>
> All,
> I have created a Lucene index from data in a SQL Server db. When I conduct
> a
> Lucene sea
Instead of just putting the keys in the index, can you put all the data you
might be getting out to display to the user, or whatever the final thing is?
That's what we do.Search on the id as you are, and then the hit has
documents that are loaded with all your final information instead of just
All,
I have created a Lucene index from data in a SQL Server db. When I conduct a
Lucene search, I get back in the hits the primary key (WorkID) and the
scores associated with the hits. Then using the list of WorkIDs, I query the
database for the other associated information of the assets associate
location.
The db (in my case postgres) consists of a table whose columns map to the
above.
So my question is two folds.
1) Lucene and database:
So inherently while building a database it makes sense to index a few things
(similar to Field.keyword). In this case I could make 'class' a
12 matches
Mail list logo
