I definitely agree with Chris here. Although Lucene and Solr are highly
related, the version numbering should communicate whether Solr has changed in a
significant or minor way to the end-user. A minor change in Lucene could cause
major changes in Solr. And vice-versa, a major change in Lucene c
[
https://issues.apache.org/jira/browse/SOLR-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832711#action_12832711
]
Kevin Osborn commented on SOLR-1365:
I am finally getting back around to this. And
[
https://issues.apache.org/jira/browse/SOLR-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744682#action_12744682
]
Kevin Osborn commented on SOLR-1365:
Thanks for the comments. I'll make the ch
[
https://issues.apache.org/jira/browse/SOLR-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744376#action_12744376
]
Kevin Osborn commented on SOLR-1365:
Thanks for the feedback. I looked at IndexSc
[
https://issues.apache.org/jira/browse/SOLR-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Osborn updated SOLR-1365:
---
Attachment: SOLR-1365.patch
> Add configurable Sweetspot Similarity fact
Reporter: Kevin Osborn
Priority: Minor
Fix For: 1.4
This is some code that I wrote a while back.
Normally, if you use SweetSpotSimilarity, you are going to make it do something
useful by extending SweetSpotSimilarity. So, instead, I made a factory class
and an configurable
I had a case where I was extending the DisMax parser. So, my class
MyNewDxMaxQParserPlugin extends QParserPlugin. But, I just copied and pasted
from DixMaxQParserPlugin.java. Sure, doesn't reuse all the code, but in my case
I just needed the existing code as an example and then I had to change
[
https://issues.apache.org/jira/browse/SOLR-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Osborn updated SOLR-432:
--
Attachment: QueryResultsKey.diff
> Add accessor functions to QueryResults
: Kevin Osborn
Priority: Minor
We need to add accessor functions to QueryResultsKey. In our custom
regenerator, we need to get the query, filter and sort data items. The only
accessible object we have is the QueryResultsKey object. I then added accessor
functions for SFields and
[
https://issues.apache.org/jira/browse/SOLR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Osborn updated SOLR-431:
--
Attachment: XMLWriter.diff
> Add the ability to disable XML escaping in XMLWri
Reporter: Kevin Osborn
Priority: Minor
Attachments: XMLWriter.diff
This is definitely not the prettiest way to do things, but it is by far the
simplest. In April, 2006, Erik Hatcher added a fix to Solr that properly
escaped all XML attributes in the response
[
https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549609
]
Kevin Osborn commented on SOLR-243:
---
We used this patch with great success. We have a custom multiindex reader. This
[
https://issues.apache.org/jira/browse/SOLR-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Osborn resolved SOLR-429.
---
Resolution: Fixed
> Add remove function to LRUCa
Add remove function to LRUCache
---
Key: SOLR-429
URL: https://issues.apache.org/jira/browse/SOLR-429
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Kevin Osborn
[
https://issues.apache.org/jira/browse/SOLR-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Osborn updated SOLR-429:
--
Attachment: LRUCache.diff
> Add remove function to LRUCa
15 matches
Mail list logo