[jira] Updated: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-84: -- Attachment: solr-nick.gif another possible direction... New Solr logo? -- Key: SOLR-84 URL: https://issues.apache.org/jira/browse/SOLR-84 Project: Solr Issue Type: Improvement Reporter: Bertrand Delacretaz Priority: Minor Attachments: logo-grid.jpg, logo-solr-d.jpg, logo-solr-e.jpg, logo-solr-source-files-take2.zip, solr-84-source-files.zip, solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, solr-nick.gif, solr.jpg, solr.jpg Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) sarraux-dessous.ch) has reworked his logo proposal to be more solar. This can either be the start of a logo contest, or if people like it we could adopt it. The gradients can make it a bit hard to integrate, not sure if this is really a problem. WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-81) Add Query Spellchecker functionality
[ https://issues.apache.org/jira/browse/SOLR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481738 ] Otis Gospodnetic commented on SOLR-81: -- This is in SVN now, but I'm going to leave this open for another week, in case Hoss, Adam, or anyone else finds any issues. Add Query Spellchecker functionality Key: SOLR-81 URL: https://issues.apache.org/jira/browse/SOLR-81 Project: Solr Issue Type: New Feature Components: search Reporter: Otis Gospodnetic Priority: Minor Attachments: SOLR-81-edgengram-ngram.patch, SOLR-81-ngram-schema.patch, SOLR-81-ngram.patch, SOLR-81-ngram.patch, SOLR-81-ngram.patch, SOLR-81-ngram.patch, SOLR-81-spellchecker.patch, SOLR-81-spellchecker.patch, SOLR-81-spellchecker.patch Use the simple approach of n-gramming outside of Solr and indexing n-gram documents. For example: doc field name=wordlettuce/field field name=start3let/field field name=gram3let ett ttu tuc uce/field field name=end3uce/field field name=start4lett/field field name=gram4lett ettu ttuc tuce/field field name=end4tuce/field /doc See: http://www.mail-archive.com/solr-user@lucene.apache.org/msg01254.html Java clients: SOLR-20 (add delete commit optimize), SOLR-30 (search) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r519107 - in /lucene/solr/trunk: CHANGES.txt example/exampledocs/spellchecher.xml example/solr/conf/solrconfig.xml lib/lucene-spellchecker-2.2-dev.jar src/java/org/apache/solr/request/
On Mar 16, 2007, at 3:28 PM, [EMAIL PROTECTED] wrote: Author: otis lucene/solr/trunk/example/exampledocs/spellchecher.xml that should be spellchecker, not spellchecher.
Re: svn commit: r519107 - in /lucene/solr/trunk: CHANGES.txt example/exampledocs/spellchecher.xml example/solr/conf/solrconfig.xml lib/lucene-spellchecker-2.2-dev.jar src/java/org/apache/solr/request/
On Mar 16, 2007, at 3:28 PM, [EMAIL PROTECTED] wrote:
+ str name=spellcheckerIndexDir/home/otis/dev/repos/lucene/
solr/trunk/example/solr/data/index/str
And this needs to be changed to something globally relevant. What
triggers the creation of this index? With this part of the example,
we ought to flesh it out so that it works for anyone trying out Solr,
right?
+public void init(NamedList args) {
+super.init( args );
+spellcheckerIndexDir = invariants.get
(spellcheckerIndexDir);
+try {
+spellChecker = new SpellChecker
(FSDirectory.getDirectory(spellcheckerIndexDir));
+} catch (IOException e) {
+throw new RuntimeException(Cannot open SpellChecker
index, e);
+}
+}
If this index were updated, what would trigger it to get refreshed by
this request handler?
[jira] Commented: (SOLR-81) Add Query Spellchecker functionality
[
https://issues.apache.org/jira/browse/SOLR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481759
]
Otis Gospodnetic commented on SOLR-81:
--
There is a useless (I think) static IndexReader in there:
private static IndexReader reader = null;
If we set this to some real IndexReader, we can get the SpellChecker to act as
follows (from its coffeedocs):
* @param ir the indexReader of the user index (can be null see field param)
* @param field String the field of the user index: if field is not null, the
suggested
* words are restricted to the words present in this field.
* @param morePopular boolean return only the suggest words that are more
frequent than the searched word
* (only if restricted mode = (indexReader!=null and field!=null)
public String[] suggestSimilar(String word, int numSug, IndexReader ir,
String field, boolean morePopular) throws IOException {
So, should we do this on init:
reader = req.getSearcher().getReader();
?
Or maybe add a new param to solrconfig.xml's declaration of the
SpellCheckerRequestHandler that turns this on/off?
Thoughts?
Add Query Spellchecker functionality
Key: SOLR-81
URL: https://issues.apache.org/jira/browse/SOLR-81
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Otis Gospodnetic
Priority: Minor
Attachments: SOLR-81-edgengram-ngram.patch,
SOLR-81-ngram-schema.patch, SOLR-81-ngram.patch, SOLR-81-ngram.patch,
SOLR-81-ngram.patch, SOLR-81-ngram.patch, SOLR-81-spellchecker.patch,
SOLR-81-spellchecker.patch, SOLR-81-spellchecker.patch
Use the simple approach of n-gramming outside of Solr and indexing n-gram
documents. For example:
doc
field name=wordlettuce/field
field name=start3let/field
field name=gram3let ett ttu tuc uce/field
field name=end3uce/field
field name=start4lett/field
field name=gram4lett ettu ttuc tuce/field
field name=end4tuce/field
/doc
See:
http://www.mail-archive.com/solr-user@lucene.apache.org/msg01254.html
Java clients: SOLR-20 (add delete commit optimize), SOLR-30 (search)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: svn commit: r519107 - in /lucene/solr/trunk: CHANGES.txt example/exampledocs/spellchecher.xml example/solr/conf/solrconfig.xml lib/lucene-spellchecker-2.2-dev.jar src/java/org/apache/solr/request/
Hi,
- Original Message
From: Erik Hatcher [EMAIL PROTECTED]
To: solr-dev@lucene.apache.org
Sent: Friday, March 16, 2007 4:36:25 PM
Subject: Re: svn commit: r519107 - in /lucene/solr/trunk: CHANGES.txt
example/exampledocs/spellchecher.xml example/solr/conf/solrconfig.xml
lib/lucene-spellchecker-2.2-dev.jar
src/java/org/apache/solr/request/SpellCheckerRequestHandler.java
On Mar 16, 2007, at 3:28 PM, [EMAIL PROTECTED] wrote:
+ str name=spellcheckerIndexDir/home/otis/dev/repos/lucene/
solr/trunk/example/solr/data/index/str
And this needs to be changed to something globally relevant. What
triggers the creation of this index? With this part of the example,
we ought to flesh it out so that it works for anyone trying out Solr,
right?
OG: Ideally, si. What should I set it to? How can I set it to a dir relative
to solr.home?
+public void init(NamedList args) {
+super.init( args );
+spellcheckerIndexDir = invariants.get
(spellcheckerIndexDir);
+try {
+spellChecker = new SpellChecker
(FSDirectory.getDirectory(spellcheckerIndexDir));
+} catch (IOException e) {
+throw new RuntimeException(Cannot open SpellChecker
index, e);
+}
+}
If this index were updated, what would trigger it to get refreshed by
this request handler?
OG: ...cmd=rebuild should do it.
Otis
