See http://hudson.zones.apache.org/hudson/job/Solr-trunk/351/changes
Changes:
[ehatcher] SOLR-473: RDoc patch contributed Chris Kline
--
[...truncated lines...]
AUclient/ruby/solr-ruby/lib/solr/importer/delimited_file_source.rb
AU
Hi Stu,
Thank you very much for your reply. It cleared very many things.
Thanks,
Roopesh
Stu Hood wrote:
Hello Roopesh,
What you are seeing is called 'Stemming'. Stemming takes tokens and reduces
them to their language specific prefixes. So for instance, when you search for
attach, you get
Hi Chris,
You should be able to reopen SOLR-42. Please attach your test case
and/or patch on it. This does sound like a problem.
-Grant
On Feb 13, 2008, at 8:28 PM, Chris Harris wrote:
https://issues.apache.org/jira/browse/SOLR-42 changed the
HtmlStripReader so that Tokens from a
Those levels comes from java.util.logging.Level:
http://java.sun.com/javase/6/docs/api/java/util/logging/Level.html
I disagree that the default should be off. Logging doesn't impact
performance that much unless it is set to something like FINEST.
I don't think you want to ignore SECERE and/or
[
https://issues.apache.org/jira/browse/SOLR-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568938#action_12568938
]
Grant Ingersoll commented on SOLR-342:
--
Sounds like we will have a Lucene 2.3.1 release
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568992#action_12568992
]
Henri Biestro commented on SOLR-350:
Regarding c/variables/properties, imho we can
Currently, default settings output UPDATE messages (thousands per second
in my case). Is it WARNING/SEVERE setting in SOLR source?
I disagree that the default should be off. Logging doesn't impact
performance that much unless it is set to something like FINEST.
I don't think you want to
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569018#action_12569018
]
Ryan McKinley commented on SOLR-350:
Regarding c/variables/properties, imho we can
[
https://issues.apache.org/jira/browse/SOLR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Harris updated SOLR-42:
-
Attachment: TokenPrinter.java
HtmlStripReaderTestXmlProcessing.patch
The committed
[
https://issues.apache.org/jira/browse/SOLR-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-127:
--
Attachment: HTTPCaching.patch
checkpoint: unification of the most recent HTTPCaching.patch and Thomas's last
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Gnatovskiy updated SOLR-236:
-
Attachment: field_collapsing_dsteigerwald.diff
Latest patch file fixes an issue where facet
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569146#action_12569146
]
Henri Biestro commented on SOLR-350:
We need a way to define a global data root without
[
https://issues.apache.org/jira/browse/SOLR-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-127:
--
Attachment: HTTPCaching.patch
Changes made in this version...
1) refactored etag cache to be core specific.
2)
: Currently, default settings output UPDATE messages (thousands per second
: in my case). Is it WARNING/SEVERE setting in SOLR source?
They are INFO level messages, which is the jvm defualt.
One INFO level message per request doesn't seem that excessive to me,
almost any HTTP server i can think
14 matches
Mail list logo
