Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [smila-dev] SMILA as Search engine

Hi folks,

you've my apologies because of late response.

2. SMILA crashes if you use more than one word in double quotes, e.g. "Every day"
-> correct. I get an error in the log: 
" java.lang.NoClassDefFoundError: org/apache/lucene/index/memory/MemoryIndex"
--> There was an import missing in Solr/Lucene orbit bundles. I modified the manifest and build a new extension jar which I just checked in.

3. "threshold"-parameter has no effect
-> correct. From a first look, there maybe sth. missing in the 
-> SolrQueryConverter
--> Solr doesn't support a parameter like threshold. I'm gonna create an issue in bugzilla and talk with Andreas about a possible solution.

4. R.Content.Operator with value AND doesn't work
-> correct. From a first look the SolrQuery seems to get the correct operator, but it doesn't seem to have any effect.
--> Right now the SolrQueryConverter doesn't handle any parameters within SMILA's "ranking" map. But there is a possibility in Solr which let you set the default operator in a query. I'm gonna create an issue in bugzilla and try to implement this feature as soon as possible. For now you can either change the default operator in schema.xml of your Solr configuration or you send an operator directly with the query like so: <Map key="query"><Val key="Content">smila AND solr</Val></Map>.

I hope this helps for now.

Kind regards

Peter


-----Original Message-----
From: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Andreas Weber
Sent: Dienstag, 9. Oktober 2012 11:06
To: Smila project developer mailing list
Subject: Re: [smila-dev] SMILA as Search engine

Hi Rene,

thanx for your feedback!

@Peter: As you are more familiar with the SOLR search, could you have a look at the issues 2,3 and 4 that I listed below?

I tried to reproduce the problems with SMILA 1.1 and trunk with our 5-minutes index.
Let me try to summarize the issues:

1. SMILA crashes if you go to one of the last result pages
-> can't reproduce that

2. SMILA crashes if you use more than one word in double quotes, e.g. "Every day"
-> correct. I get an error in the log: 
" java.lang.NoClassDefFoundError: org/apache/lucene/index/memory/MemoryIndex" 
...

3. "threshold"-parameter has no effect
-> correct. From a first look, there maybe sth. missing in the 
-> SolrQueryConverter

4. R.Content.Operator with value AND doesn't work
-> correct. From a first look the SolrQuery seems to get the correct operator, but it doesn't seem to have any effect.

Think we should create bugzilla calls for each of these after Peter's feedback.

Best regards,
 Andreas

> -----Ursprüngliche Nachricht-----
> Von: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev- 
> bounces@xxxxxxxxxxx] Im Auftrag von Corinth, Rene
> Gesendet: Montag, 8. Oktober 2012 21:31
> An: smila-dev@xxxxxxxxxxx
> Betreff: [smila-dev] SMILA as Search engine
> 
> 
> Hey Developers,
> 
> there are another bugs in the search Query:
> 
> If I'm searching for more than one word in the field query and put 
> them in double quotes or a minus sign, SMILA crashes unfortunately.
> For example:
>    "Every day"
>    internet-based
> 
> http://www.theseus-programm.de/en/75_smila.php
> 
> Also if I put only one double quote in the query.
> 
> 
> And if I'm searching for a whole sentence, using the attribute 
> R.Content.Operator with the value AND, it still uses OR as a connector 
> (maybe this is default?). I still get too much results where the last 
> result pages contain only one word of the sentence.
> 
> 
> Also using the Threshold-Field has no effect.
> 
> I hope this is not too much headache for you....
> 
> Cheers
> 
> René
> 
> _______________________________________________
> smila-dev mailing list
> smila-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/smila-dev
_______________________________________________
smila-dev mailing list
smila-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-dev


Back to the top