How do you make a query that used criteria on properties and full text search?
If you store your properties in one store (eg. DB) and used index store engine for content search, I expected to have some performance issues when you search on prop and content.
hmmm, not sure I follow you, can you elaborate on this more? it would be very appreciated.
If the properties/metadata are in a DB and content is tokenized into a index engine like Lucene. First, you need to select rows from DB tables and makes a second query into the index store to query on the content itself.
For this kind of scenario (search on prop AND full text search), I expect only one query via Lucene will be faster. Lucene can store properties that will not be tokenized. Anyway, it is not a ideal situation because properties have to be duplicate into 2 differents stores. So, I don't know what will be the best solution !
Agree ! I understand your point of view, the best way to query on properties is certainly the classic select statment but if you need an index/search engine to for full-text search, I don't know.Anyway, Do you have some idea to optimize the current search service ?
I havn't looked into this yet (I'm still lagging behind on some other issues with my project and I havn't attacked this part yet).
The idea is to use an RDBMS as much as possible on all content that can be turned relational without major issues (and normally metadata fits this category). As for full-text search, I agree that there is no way to beat an engine like lucene.
Furthermore, like Erik explains in a previous mail, you can write some filter to apply security rules. So, in one query makes in only one store , you can filters on props, content and security rules.
Can you do that without storing properties into the search engine ? I'm curious :-)
It should be interesting to compare in more detail both solution, makes performance tests, ...
Why not to support both situation : either inder the prop or not ?
You mean with a global configuration or more granularely?
Still thinking on that :-) The idea is to use the domain.xml file to define how to make the query on props and options used for the full text search.
Thanks for this mail, Christophe
-- Stefano.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
