[
https://issues.apache.org/jira/browse/SOLR-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-493:
--
Assignee: Ryan McKinley
> /admin/file links don't work with legacy configs
>
[
https://issues.apache.org/jira/browse/SOLR-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-312:
--
Assignee: Ryan McKinley
> create solrj javadoc in build.xml
> -
>
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-350:
--
Assignee: Ryan McKinley
> Manage Multiple SolrCores
> -
>
>
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-350.
Resolution: Fixed
Fix Version/s: 1.3
> Manage Multiple SolrCores
> -
>
[
https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-281.
Resolution: Fixed
I'll mark this issue as "fixed" -- I'm not sure why it was still open, the
reason
[
https://issues.apache.org/jira/browse/SOLR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-446.
Resolution: Fixed
> TextResponseWriter should be able to work with SolrDocument and
> SolrDocumentLi
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-139:
---
Fix Version/s: (was: 1.3)
> Support updateable/modifiable documents
> -
[
https://issues.apache.org/jira/browse/SOLR-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-453.
Resolution: Cannot Reproduce
I'll mark this issue as "Cannot Reproduce" -- it looks like solr sends a
[
https://issues.apache.org/jira/browse/SOLR-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-467.
Resolution: Fixed
> Remove 'core' options from solrj
>
>
>
I don't know exactly what Hoss has in mind, but for one thing it would
mean we would need to support this in the future.
In general, changes like this get discussed for a while -- flushing
out any potential implications -- before they get added. The process
can be a bit annoying (and slow)
On May 22, 2008, at 5:59 PM, Otis Gospodnetic wrote:
I agree. Lots of what Jason is doing looks good, but like I pointed
the other day, needs a lot more explanation, at least for dense
people like moi. My guess is, if we want to be aggressive with 1.3,
that none of Jason's stuff will make
Hymm, I guess folks aren't coming out of the woodwork to vote for this
one.
Wicket recently had a poll with ~100 votes cast:
http://www.nabble.com/Re%3A--vote--Release-1.4-with-only-generics-and-stop-support-for-1.3-p16220947.html
So I'm not sure where that leaves us. Unless Grant feels stron
Hello!
I swear I have not forgotten about you all, I have been working like
crazy to put my home back into a habitable form. Drywall is going up
and the end is near.
While I am usually good about following most of what is happening on
solr-dev, I'm currently looking at 350 unread message
[
https://issues.apache.org/jira/browse/SOLR-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-489:
--
Fix Version/s: 1.3
Adding to the list for 1.3 ... we shouldn't release without @deprecation
comments for every @
[
https://issues.apache.org/jira/browse/SOLR-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi closed SOLR-347.
---
Resolution: Cannot Reproduce
> AIOOBE when field name declared twice in schema
> --
[
https://issues.apache.org/jira/browse/SOLR-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599603#action_12599603
]
Koji Sekiguchi commented on SOLR-347:
-
I cannot reproduce the issue. Solr throws a helpfu
[
https://issues.apache.org/jira/browse/SOLR-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-553:
-
Attachment: SOLR-553-SC.patch
Otis,
Here's a patch that fixes the Spell Checker test that gets bro
I think the issue is that the Spell Checker is now returning the
original word as a suggestion even when the word is spelled correctly,
whereas the test assumes there are no entries.
-Grant
On May 24, 2008, at 8:06 AM, Grant Ingersoll wrote:
So, upgrading to Lucene trunk breaks the SpellCh
Also https://issues.apache.org/jira/browse/LUCENE-1183
On May 24, 2008, at 8:06 AM, Grant Ingersoll wrote:
So, upgrading to Lucene trunk breaks the SpellCheckerRequestHandler:
Running org.apache.solr.handler.SpellCheckerRequestHandlerTest
[junit]
[junit] 01responseHeader>10name="cat">1
So, upgrading to Lucene trunk breaks the SpellCheckerRequestHandler:
Running org.apache.solr.handler.SpellCheckerRequestHandlerTest
[junit]
[junit] 01responseHeader>10name="cat">1name="cat">1
[junit]
[junit] )
[junit] Tests run: 5, Failures: 1, Errors: 0, Time elapsed: 3.0
Well, if we're not sure on upgrading, we probably should roll this one
back. I personally haven't tested 2.4-dev with Solr, but it probably
is fine. I don't think copying just the highlighter is the right thing.
-Grant
On May 23, 2008, at 11:15 PM, Otis Gospodnetic wrote:
Ah, sorry about
See http://hudson.zones.apache.org/hudson/job/Solr-trunk/450/changes
Changes:
[otis] - Removed a TODO that does not apply any more due to SOLR-539 commit
[otis] SOLR-553 Use SpanScorer when highlighting phrase terms and
hl.usePhraseHighlighter=true
[otis] SOLR-505 Give RequestHandlers the poss
init-forrest-entities:
[mkdir] Created dir: /tmp/apache-solr-nightly/build
compile-common:
[mkdir] Created dir: /tmp/apache-solr-nightly/build/common
[javac] Compiling 34 source files to /tmp/apache-solr-nightly/build/common
[javac] Note:
/tmp/apache-solr-nightly/src/java/org/apa
23 matches
Mail list logo
