[
https://issues.apache.org/jira/browse/SOLR-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-387:
Fix Version/s: (was: 1.2)
It probably isn't a good idea to introduce functionality that we know
[
https://issues.apache.org/jira/browse/SOLR-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas resolved SOLR-395.
-
Resolution: Fixed
Committed! Thanks Mike and Scott.
Spell-check should return frequencies of word
/SOLR-395
Project: Solr
Issue Type: Improvement
Components: spellchecker
Affects Versions: 1.3
Reporter: Mike Krimerman
Assignee: Mike Klaas
Priority: Minor
Fix For: 1.3
Attachments: extended_results.diff
[
https://issues.apache.org/jira/browse/SOLR-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539661
]
Mike Klaas commented on SOLR-395:
-
a python example
{code:java}
{
'responseHeader': {
'status':0,
'QTime':16
[
https://issues.apache.org/jira/browse/SOLR-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas closed SOLR-401.
---
Resolution: Invalid
Assignee: Mike Klaas
subsumed by SOLR-395
Hi frequency words in spellcheck
[
https://issues.apache.org/jira/browse/SOLR-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas closed SOLR-375.
---
Resolution: Invalid
Assignee: Mike Klaas
Scott, I worked with Mike to produce a patch that integrates
[
https://issues.apache.org/jira/browse/SOLR-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas reassigned SOLR-395:
---
Assignee: Mike Klaas
Spell-check should return frequencies of word and suggestions
I don't use Windows myself, but I just read that there is a
CreateHardLink() function in the windows api, so it might be possible
to implement the same collection distirbution scheme on windows.
-MIke
[
https://issues.apache.org/jira/browse/SOLR-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538064
]
Mike Klaas commented on SOLR-395:
-
If the extra data is only present when some parameter is present, backward
[
https://issues.apache.org/jira/browse/SOLR-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-375:
Component/s: (was: clients - java)
spellchecker
I think that the general approach
[
https://issues.apache.org/jira/browse/SOLR-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537778
]
Mike Klaas commented on SOLR-395:
-
Might it be better to rename the fields queryFreq/suggestionFreqs? (or
something
[
https://issues.apache.org/jira/browse/SOLR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-42:
---
Component/s: (was: update)
highlighter
Highlighting problems
[
https://issues.apache.org/jira/browse/SOLR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-195:
Component/s: (was: search)
highlighter
Wildcard/prefix queries not highlighted
[
https://issues.apache.org/jira/browse/SOLR-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-175:
Component/s: highlighter
Implement hl.formatter=interleave
[
https://issues.apache.org/jira/browse/SOLR-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-395:
Component/s: (was: search)
spellchecker
Spell-check should return frequencies of word
[
https://issues.apache.org/jira/browse/SOLR-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-382:
Component/s: (was: search)
spellchecker
Assignee: Mike Klaas
[
https://issues.apache.org/jira/browse/SOLR-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536302
]
Mike Klaas commented on SOLR-386:
-
I suppose the real question is What behaviour are you trying to achieve by
ripping
[
https://issues.apache.org/jira/browse/SOLR-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535768
]
Mike Klaas commented on SOLR-380:
-
In my opinion the best solution is to create one solr document per page
[
https://issues.apache.org/jira/browse/SOLR-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535789
]
Mike Klaas commented on SOLR-382:
-
I've committed a modified patch that only passes in the IndexReader
[
https://issues.apache.org/jira/browse/SOLR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas resolved SOLR-376.
-
Resolution: Fixed
committed for 1.3
Allow backup summary field for highlighting
[
https://issues.apache.org/jira/browse/SOLR-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-375:
Fix Version/s: (was: 1.2)
1.3
SpellCheckerRequestHandler improvements to handle
The SolrConfig patch changed the interface for creating a token
filter factory:
@Deprecated
public void init(MapString,String args) {
log.warning(calling the deprecated form of init; should be
calling init(SolrConfig solrConfig, MapString,String args));
this.args=args;
}
The
On 10-Oct-07, at 2:45 PM, Yousef Ourabi wrote:
Has anyone taken a closer look at this?
It looks like
org.apache.solr.client.solrj.embedded.SolrExampleJettyTest
is unable to connect to the SolrServer instance. Timing out? Perhaps
increase timeout?
On 10-Oct-07, at 3:41 PM, Ryan McKinley wrote:
Would it be appropriate to exclude this test, since a test that
fails
every night is like the boy who cried wolf? At least until it's
worked
out -- I'm not really familiar with the setup on the nightly
build box.
+1! Never-working tests
[
https://issues.apache.org/jira/browse/SOLR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-376:
Attachment: alternate_field_highlight.patch
Allow backup summary
Allow backup summary
Key: SOLR-376
URL: https://issues.apache.org/jira/browse/SOLR-376
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Mike Klaas
Assignee: Mike Klaas
[
https://issues.apache.org/jira/browse/SOLR-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531588
]
Mike Klaas commented on SOLR-342:
-
We could probably just wait for lucene 2.3 to be released before releasing 1.3.
I
On 21-Sep-07, at 11:08 AM, Yonik Seeley wrote:
I wanted to take a step back for a second and think about if HTTP was
really the right choice for the transport for distributed search.
I think the high-level approach in SOLR-303 is the right way to go
about it, but I'm unsure if HTTP is the
On 21-Sep-07, at 2:34 PM, Yonik Seeley wrote:
On 9/21/07, Mike Klaas [EMAIL PROTECTED] wrote:
On 21-Sep-07, at 11:08 AM, Yonik Seeley wrote:
I wanted to take a step back for a second and think about if HTTP
was
really the right choice for the transport for distributed search.
I think
[
https://issues.apache.org/jira/browse/SOLR-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528846
]
Mike Klaas commented on SOLR-354:
-
Actually, this is already commited (accidently?) in r576683.
I'm not sure what you
On 19-Sep-07, at 11:33 AM, Ed Summers wrote:
On 9/18/07, Mike Klaas [EMAIL PROTECTED] wrote:
I'm afraid it exists only in my imagination g
IMHO it would be easier to work on said tests if the new client was in
svn. The current python client checked into svn after all is totally
broken, so
On 19-Sep-07, at 5:59 PM, Ed Summers wrote:
On 9/19/07, Mike Klaas [EMAIL PROTECTED] wrote:
I'm not trying to be obtuse or anything, but could you elaborate on
what problems are caused by not having the file checked in? After
all, it is a single file that can be just plopped into the client
On 16-Sep-07, at 5:43 PM, Ed Summers wrote:
If necessary I'd like to help out getting SOLR-216 [1] applied. The
python client that's currently in the trunk is horribly broken with
the server implementation. What remains to be done?
It is on my list of things to review, though I'm working on a
On 10-Sep-07, at 12:32 PM, Brian Whitman wrote:
On Sep 10, 2007, at 1:56 PM, Mike Klaas wrote:
I'm a little worried about Solr getting a bad rap for being buggy
or not well-documented due to people trying to use it embeddedly.
It seems that we need to do one of two things:
1. Someone
Core request handlers do not use this, favouring the new, almost-
identical code in the highlighting package. Deprecate or delete? It
is rather simple to upgrade code using this to the new regime.
-Mike
On 6-Sep-07, at 12:55 PM, Yonik Seeley wrote:
On 9/5/07, Mike Klaas [EMAIL PROTECTED] wrote:
Issues:
- Solr still uses it's own FunctionQuery instead of what was added
back to Lucene. May want to migrate first, or may want to hold
off if
changes are needed that would be easier to make here
On 6-Sep-07, at 2:04 PM, Jonathan Woods wrote:
The queries are generally BooleanQuery combinations of TermQueries,
sometimes with output from the vanilla Lucene QueryParser thrown in
as one
of the boolean clauses: get me all pages about the Senior School
about
drama [that's the fq bit],
[
https://issues.apache.org/jira/browse/SOLR-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525578
]
Mike Klaas commented on SOLR-348:
-
Note that highlighting already has short circuiting for hl!=true, and does
almost
[
https://issues.apache.org/jira/browse/SOLR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-209:
Fix Version/s: (was: 1.1.0)
Multifields and multivalued facets
[
https://issues.apache.org/jira/browse/SOLR-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-200:
Fix Version/s: (was: 1.1.0)
Scripts don't work when run as root in ~root and su'ing to a user
[
https://issues.apache.org/jira/browse/SOLR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525162
]
Mike Klaas commented on SOLR-345:
-
Can this issue be resolved?
Add support for debugging
[
https://issues.apache.org/jira/browse/SOLR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-288:
Fix Version/s: (was: 1.2)
Allow custom IndexSearcher class
[
https://issues.apache.org/jira/browse/SOLR-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas resolved SOLR-299.
-
Resolution: Fixed
committed r573019
Audit use of backticks in solr.py
On 5-Sep-07, at 1:10 PM, Yonik Seeley wrote:
Issues:
- Solr still uses it's own FunctionQuery instead of what was added
back to Lucene. May want to migrate first, or may want to hold off if
changes are needed that would be easier to make here.
I believe that the main thing missing is the
On 31-Aug-07, at 11:04 AM, Jeff Rodenburg wrote:
I need to publish quite a few different things for sample usage of the
Solrsharp library. Solrsharp doesn't have a dedicated website, just a
container page on the wiki that points to source code and a JIRA
issue for a
zip download.
The wiki
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523925
]
Mike Klaas commented on SOLR-303:
-
Great stuff!
I think asynchronous/parallel requests are a central feature
[
https://issues.apache.org/jira/browse/LUCENE-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521590
]
Mike Klaas commented on LUCENE-982:
---
One heuristic that has been quite useful for us is to skip optimizing
[
https://issues.apache.org/jira/browse/LUCENE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521191
]
Mike Klaas commented on LUCENE-871:
---
The switch statement is not equivalent to a list of sequential ifelses
Assignee: Mike Klaas
Priority: Trivial
Attachments: solr.py, solr.py
I've taken the original solr.py code and extended it to include
higher-level functions.
* Requires python 2.3+
* Supports SSL (https://) schema
* Conforms (mostly) to PEP 8 -- the Python Style Guide
[junit] Running org.apache.solr.update.AutoCommitTest
[junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed:
20.424 sec
[junit] Test org.apache.solr.update.AutoCommitTest FAILED
This is how long it takes to run on my (medium-loaded) system:
junit:
[junit] Running
On 26-Jul-07, at 6:54 PM, Sundling, Paul wrote:
When I started computing it was always Master and Slave. In the last
several years I've seen people use Primary and Secondary instead.
When
I saw the old style I looked it up and this is what I found:
On 26-Jul-07, at 5:36 PM, Grant Ingersoll wrote:
I propose we take the following path for migrating Lucene Java to
JDK 1.5:
1. Put in any new deprecations we want, cleanups, etc.
2. Release 2.4 so all of Mike M's goodness is available to 1.4
users within the next 2-4 weeks using our new
[
https://issues.apache.org/jira/browse/SOLR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515784
]
Mike Klaas commented on SOLR-320:
-
Thanks for the bug report! I should be able to fix this momentarily
[
https://issues.apache.org/jira/browse/SOLR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas resolved SOLR-320.
-
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Mike Klaas
Fixed in r559887
[
https://issues.apache.org/jira/browse/SOLR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515788
]
Mike Klaas commented on SOLR-320:
-
This fixes the problem for me:
Index: src/java/org/apache/solr/update
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515424
]
Mike Klaas commented on SOLR-139:
-
Darn, you're right: writer.addDocument() is outside of the synchronized block.
We
On 23-Jul-07, at 3:43 PM, Yonik Seeley wrote:
On 7/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: klaas
Date: Mon Jul 23 15:15:18 2007
New Revision: 558879
URL: http://svn.apache.org/viewvc?view=revrev=558879
Log:
Sync to lucene 2.2.0. Tests pass.
OK, I guess we don't have any
On 19-Jul-07, at 2:49 PM, Yonik Seeley wrote:
Does anyone have a good idea how to go about searching for
concatenated tokens?
Say that the index has painkiller and the user types in
pain killer (without the quotes).
If one were using the standard request handler, the easiest would be
to
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514099
]
Mike Klaas commented on SOLR-139:
-
It is my fault that the DUH2 locking is so hairy to begin with, so I should
[
https://issues.apache.org/jira/browse/SOLR-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas resolved SOLR-102.
-
Resolution: Fixed
committed in r557872
Ideas for better highlighting
Deleting pending handling can cause OOM
---
Key: SOLR-310
URL: https://issues.apache.org/jira/browse/SOLR-310
Project: Solr
Issue Type: Bug
Reporter: Mike Klaas
Assignee: Mike
On 18-Jul-07, at 2:58 PM, Yonik Seeley wrote:
On 7/18/07, Mike Klaas [EMAIL PROTECTED] wrote:
Could happen when doDeleting the pending docs too. James: try
sending commit every 500k docs or so.
Hmmm, right... some of the memory usage will be related to the treemap
keeping track of deleted
On 15-Jul-07, at 1:59 PM, Sergey Dryganets (JIRA) wrote:
than I create query field_name:value1 value2 value3
i recive only documents with field_name== value1
Now i trying to filter results of the query by id list
may be there are some another way to filter results by id's list?
Note
On 13-Jul-07, at 12:48 AM, Thomas Peuss (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-298?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Peuss reopened SOLR-298:
---
Sorry. I have not really stated that this issue
On 13-Jul-07, at 1:53 PM, Yonik Seeley (JIRA) wrote:
... ParallelReader, where some fields are in one sub-index ...
the processor would ask the updateHandler for the existing
document - the updateHandler deals with
getting it to/from the right place.
The big reason you would use
Reporter: Mike Klaas
Assignee: Mike Klaas
Fix For: 1.3
backticks are often the wrong thing to do (they return a debugging
representation of a variable).
This may be superceded by the new python client, but should be fixed in the
mean time.
--
This message
: 1.3
Reporter: Mike Klaas
Assignee: Mike Klaas
Priority: Minor
Fix For: 1.3
WDF is handy but over-tokenizes when faced with short word parts:
A9
R2D2
mp3
This creates one- or two- character tokens which are extremely slow to query as
the doc freq
[
https://issues.apache.org/jira/browse/SOLR-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511306
]
Mike Klaas commented on SOLR-293:
-
Would it be useful to be able to configure this separately for words and
numbers
[
https://issues.apache.org/jira/browse/SOLR-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-102:
Attachment: regexfrag.patch
Fleshes out the RegexFragmenter integration with solr (which was already
I haven't looked into this in depth, but there seems to be a bug with
the new update handler.
Combining monitor.xml and monitor2.xml into a single add command and
running ./post.sh twice used to produce:
INFO: DirectUpdateHandler2 deleting and removing dups for 2 ids
INFO:
Oops, wrong direction. XppUpdateHandler is fine, the new
XmlUpdateHandler is exhibiting the bug
On 4-Jul-07, at 4:53 PM, Mike Klaas wrote:
I haven't looked into this in depth, but there seems to be a bug
with the new update handler.
Combining monitor.xml and monitor2.xml into a single
[
https://issues.apache.org/jira/browse/LUCENE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509998
]
Mike Klaas commented on LUCENE-850:
---
Hi Doron,
The main use case is the same as for documents (and to a lesser
[
https://issues.apache.org/jira/browse/LUCENE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510001
]
Mike Klaas commented on LUCENE-850:
---
Tim: That is typically done by adding an optional implicit phrase query
On 2-Jul-07, at 11:34 PM, Ryan McKinley wrote:
URL: http://svn.apache.org/viewvc?view=revrev=552683
Log:
SOLR-102 - regex fragmenter using SOLR-225 plugin framework
Mike - I did not add this to CHANGES.txt.
Do you want to?
I'll add it, along with some javadocs/wiki docs.
Thanks,
-Mike
[
https://issues.apache.org/jira/browse/SOLR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SOLR-273 started by Mike Klaas.
Make max document analyzed bytes (for highlighter) configurable
[
https://issues.apache.org/jira/browse/SOLR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas resolved SOLR-273.
-
Resolution: Fixed
commited option+test in r553023
Make max document analyzed bytes (for highlighter
On 2-Jul-07, at 11:32 AM, Yonik Seeley wrote:
In the spirit of shared ownership, what do people think of getting rid
of @author tags (for committers or other dev people that consent?).
Other apache projects have done so, for a host of reasons.
- some people don't use author tags, hence credit
[
https://issues.apache.org/jira/browse/SOLR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509709
]
Mike Klaas commented on SOLR-225:
-
Looking great Ryan (again, only commenting on the Highlighting configurability
[
https://issues.apache.org/jira/browse/SOLR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509709
]
Mike Klaas edited comment on SOLR-225 at 7/2/07 4:14 PM:
-
Looking great Ryan (again, only
[
https://issues.apache.org/jira/browse/SOLR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509728
]
Mike Klaas commented on SOLR-225:
-
I'm torn on what is more/less elegant.
Should we have a new class
Components: search
Affects Versions: 1.2
Reporter: Mike Klaas
Assignee: Mike Klaas
Priority: Minor
Fix For: 1.3
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/SOLR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SOLR-274 started by Mike Klaas.
autoCommit maxDocs does not apply if maxTime is defined
[
https://issues.apache.org/jira/browse/SOLR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas resolved SOLR-274.
-
Resolution: Fixed
fixed in r550576
autoCommit maxDocs does not apply if maxTime is defined
On 22-Jun-07, at 6:53 AM, Henri Biestro (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-255?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_12507326 ]
Henri Biestro commented on SOLR-255:
Toru,
I've been
On 20-Jun-07, at 9:54 AM, Ryan McKinley wrote:
should we update to latest stable builds?
* lucene-2.2
+1, once the release is finalized.
-mike
[
https://issues.apache.org/jira/browse/SOLR-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505393
]
Mike Klaas commented on SOLR-176:
-
Might it then make sense to wait until the search component thing is done?
Auto
[
https://issues.apache.org/jira/browse/SOLR-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-176:
Attachment: dtiming.patch
added javadocs for RTimer.java, and removed a superfluous line from SRH.java
Add
On 11-Jun-07, at 5:48 PM, Chris Hostetter wrote:
: Yes, the current JIRA patch uses the FieldCache.
I just ment in contrast with Mike's comment about iterating over
all the
stored fields to support the post-faceting situation (but frankly
i'm
not sure that i undersatnd what the
On 11-Jun-07, at 8:10 AM, Will Johnson wrote:
And one other point, one of the reasons why it's hard to find an
example
of post-faceting is that many of the major engines can't do it.
It seems that the only way to do it would be to collapse the entire
result set first, which entails
[
https://issues.apache.org/jira/browse/SOLR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas resolved SOLR-257.
-
Resolution: Fixed
commited in r545597 with inverted logic and yonik's name suggestion.
Add ability
[
https://issues.apache.org/jira/browse/SOLR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502906
]
Mike Klaas commented on SOLR-257:
-
Might be a good idea. Case-based splitting is a relatively aggressive default
On 8-Jun-07, at 2:44 PM, Chris Hostetter wrote:
:* '''generateWordParts=1''' causes parts of words to be
generated:
: * `PowerShot = Power Shot`
: +* `Power-Shot = Power Shot`
: + * '''splitOnCaseChange=1''' causes lowercase = uppercase
transitions to generate a new part
Components: update
Affects Versions: 1.2
Reporter: Mike Klaas
Assignee: Mike Klaas
Priority: Trivial
Fix For: 1.3
Attachments: ignoreCaseChange.patch
patch adds ignoreCaseChange option to WordDelimiterFilter, which I have used
and it may
[
https://issues.apache.org/jira/browse/SOLR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated SOLR-257:
Attachment: ignoreCaseChange.patch
Add ability for WordDelimiterFilter to ignore case changes
[
https://issues.apache.org/jira/browse/SOLR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502546
]
Mike Klaas commented on SOLR-257:
-
The difference from generateWordParts is as follows: gWP splits adjacent
tokens
On 30-May-07, at 12:43 PM, Erik Hatcher wrote:
On May 29, 2007, at 4:38 PM, Mike Klaas wrote:
I agree. I was not aware of field boosts at the time. I'll code
this change.
Unfortunately, it is still somewhat awkward. In my python client
I end up passing (name, value, field boost or None
On 31-May-07, at 4:02 PM, Yonik Seeley wrote:
Sorry folks... one more time. This release candidate fixes SOLR-250
(scripts need to tell curl the content-type), as well as the minor
README typo.
Please vote to release the artifacts at
http://people.apache.org/~yonik/staging_area/solr/1.2rc3/
[
https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas reassigned SOLR-216:
---
Assignee: Mike Klaas
Improvements to solr.py
---
Key: SOLR-216
[
https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SOLR-216 started by Mike Klaas.
Improvements to solr.py
---
Key: SOLR-216
URL: https://issues.apache.org
[
https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499913
]
Mike Klaas commented on SOLR-216:
-
On 29-May-07, at 12:41 PM, Jason Cater wrote:
I've had my solr.py in production
201 - 300 of 453 matches
Mail list logo
