[
https://issues.apache.org/jira/browse/SOLR-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul resolved SOLR-1229.
--
Resolution: Fixed
committed r788587
> deletedPkQuery feature does not work when pk and uniqueKey field
[
https://issues.apache.org/jira/browse/SOLR-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-1229:
Assignee: Noble Paul
> deletedPkQuery feature does not work when pk and uniqueKey field do not have
[
https://issues.apache.org/jira/browse/SOLR-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul resolved SOLR-1245.
--
Resolution: Fixed
> DIH eats up SQL exception
> -
>
> Key: SOLR-
[
https://issues.apache.org/jira/browse/SOLR-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724389#action_12724389
]
Noble Paul commented on SOLR-1198:
--
committed r788582 moved datadir reading to solrconfig
[
https://issues.apache.org/jira/browse/SOLR-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724388#action_12724388
]
Noble Paul commented on SOLR-1198:
--
Should it be a required feature for 1.4? My real object
[
https://issues.apache.org/jira/browse/SOLR-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul resolved SOLR-1234.
--
Resolution: Fixed
committed r788580
> Multiple DIH does not work because all of them write to dataimpo
[
https://issues.apache.org/jira/browse/SOLR-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul resolved SOLR-1246.
--
Resolution: Fixed
commited r788571
thanks Rafal
> StatsComponent returing Double.MIN_VALUE when determi
[
https://issues.apache.org/jira/browse/SOLR-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1248:
---
Attachment: SOLR-1248.patch
With the patch to SolrIndexReader.toString() you can see the reference cou
TestSpellCheckResponse depends on example server
Key: SOLR-1249
URL: https://issues.apache.org/jira/browse/SOLR-1249
Project: Solr
Issue Type: Bug
Reporter: Yonik Seeley
Julian Davchev wrote:
Mark Miller wrote:
Rather than using org.apache.solr.request.SolrParams, try using
org.apache.solr.common.params.SolrParms.
Thanks that really helped. One final issue to solve.I don't see
SolrParams.set() which I guess is normal but how can I
modify the q
On Thu, Jun 25, 2009 at 4:57 PM, Otis
Gospodnetic wrote:
>> Right - if we're relatively sure that a Lucene release is imminent
>> (and will happen before a Solr release), it's not such a bad idea to
>> upgrade.
>
> Aha, so this makes sense. Stick with the stable version until we see Lucene
> is p
IndexReader reference counting bug
--
Key: SOLR-1248
URL: https://issues.apache.org/jira/browse/SOLR-1248
Project: Solr
Issue Type: Bug
Affects Versions: 1.4
Reporter: Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724286#action_12724286
]
Michael McCandless commented on SOLR-940:
-
OK try again? Maybe 3rd time's the charm.
Hello,
- Original Message
> From: Yonik Seeley
> To: solr-dev@lucene.apache.org
> Sent: Thursday, June 25, 2009 1:41:39 PM
> Subject: Re: lucene releases vs trunk
>
> On Thu, Jun 25, 2009 at 1:29 PM, Chris
> Hostetterwrote:
> > : This proposal was just for the next (1.5?) release cycl
Mark Miller wrote:
> Rather than using org.apache.solr.request.SolrParams, try using
> org.apache.solr.common.params.SolrParms.
>
Thanks that really helped. One final issue to solve.I don't see
SolrParams.set() which I guess is normal but how can I
modify the q param before I pass it furthe
[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724255#action_12724255
]
Michael McCandless commented on SOLR-940:
-
Sigh. I'll go reopen LUCENE-1630!
> Trie
[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724248#action_12724248
]
Shalin Shekhar Mangar commented on SOLR-940:
{quote}OK I just committed a fix for
[
https://issues.apache.org/jira/browse/SOLR-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafał Kuć updated SOLR-1246:
Attachment: StatsComponent.java.patch
I`ve added the patch for this.
> StatsComponent returing Double.MIN_
On Thu, Jun 25, 2009 at 11:14 PM, Chris Hostetter
wrote:
>
> : Subject: Build failed in Hudson: Solr-trunk #842
> :
> : See http://hudson.zones.apache.org/hudson/job/Solr-trunk/842/
>
> Build #843 seems to have failed because of a compile error in a DIH
> test (Noble are you looking into that?) bu
[
https://issues.apache.org/jira/browse/SOLR-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1025.
Resolution: Won't Fix
Having the default type (defType) only affect the next immediate query parser
: Subject: Build failed in Hudson: Solr-trunk #842
:
: See http://hudson.zones.apache.org/hudson/job/Solr-trunk/842/
Build #843 seems to have failed because of a compile error in a DIH
test (Noble are you looking into that?) but *prior* to that builds 838-842
all seem to have had two tests fai
On Thu, Jun 25, 2009 at 1:29 PM, Chris
Hostetter wrote:
> : This proposal was just for the next (1.5?) release cycle though.
> ...
> : I agree though - there is rapid movement in Lucene these days, and things
> can
> : be pulled back or altered fairly easily during trunk dev. Sometimes even
[
https://issues.apache.org/jira/browse/SOLR-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724157#action_12724157
]
Noble Paul commented on SOLR-1227:
--
Ok. I took a look at the SOLR-1243. I guess it should b
: This proposal was just for the next (1.5?) release cycle though.
...
: I agree though - there is rapid movement in Lucene these days, and things can
: be pulled back or altered fairly easily during trunk dev. Sometimes even index
: format changing issues - which can be a real pain (havin
I am ready to extend my helping hand Eric and Matthias for fixing the docs
and the js-code base (if need be).
I have recently started using SolrJS and I feel that this contrib is unable
to keep pace with enhancements in Solr.
I would have been an author, if not a programmer. Lemme know what all to
Rather than using org.apache.solr.request.SolrParams, try using
org.apache.solr.common.params.SolrParms.
--
- Mark
http://www.lucidimagination.com
Julian Davchev wrote:
Hi devs,
I am not sure if mailing list is for solr developers only or include
extending solr as well.
I ended up buildi
Hi devs,
I am not sure if mailing list is for solr developers only or include
extending solr as well.
I ended up building own plugin(class) which extends
handler.component.SearchHandlercause I wan to use all it's
functionlity only to adjust the q param before it gets preocessed.
How exactl
This proposal was just for the next (1.5?) release cycle though.
Lucene 2.9 is going to beat Solr 1.4 in any case I think, so it would
seem to make sense to go with it, and so this won't be an issue for this
release. For 1.5, we can just run as normal, and I guess, and plan to
release a bit af
I kind of agree... But will this (not) affect how quickly new features in
Luceneland will get their Solr support? In other words, if we have to wait for
a proper Lucene release, doesn't that mean that:
1) Solr releases will depend on Lucene releases (unless there are some
Solr-only changes th
--- Begin Message ---
Eric Pugh schrieb:
Hi all,
hi there
I started to create a bug for this, but thought I would just post to
the mailing list. I've been using SolrJS for a while from
http://solrjs.solrstuff.org/, however from my conversations with
Matthias, the plan is to move to the S
[
https://issues.apache.org/jira/browse/SOLR-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724125#action_12724125
]
Mark Miller commented on SOLR-1243:
---
I'm going to commit if there is no objection. I don't
[
https://issues.apache.org/jira/browse/SOLR-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1242.
---
Resolution: Fixed
Committed. Thanks Jay!
> The admin System handler returns bad JVM info
> --
Hi all,
I started to create a bug for this, but thought I would just post to
the mailing list. I've been using SolrJS for a while from http://solrjs.solrstuff.org/
, however from my conversations with Matthias, the plan is to move to
the Solr JavaScript contrib module being the master, and
This is an excellent idea.
When I find a problem and want to research the Lucene bugs that might
describe it, that is really hard with a trunk build. It's easy with a
release build.
wunder
On 6/25/09 4:18 AM, "Yonik Seeley" wrote:
> For the next release cycle (presumably 1.5?) I think we shoul
[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724080#action_12724080
]
Michael McCandless commented on SOLR-940:
-
OK I just committed a fix for LUCENE-1630
StatsComponent uses top-level FieldCache
Key: SOLR-1247
URL: https://issues.apache.org/jira/browse/SOLR-1247
Project: Solr
Issue Type: Bug
Affects Versions: 1.4
Reporter: Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724050#action_12724050
]
Mark Miller commented on SOLR-1227:
---
SOLR-1243 turns off http caching for all the admin ha
For the next release cycle (presumably 1.5?) I think we should really
try to stick to released versions of Lucene, and not use dev/trunk
versions.
Early in Solr's lifetime, Lucene trunk was more stable (APIs changed
little, even on non-released versions), and Lucene releases were few
and far betwee
[
https://issues.apache.org/jira/browse/SOLR-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723991#action_12723991
]
Shalin Shekhar Mangar commented on SOLR-1241:
-
bq. This ticket covers only CharF
[
https://issues.apache.org/jira/browse/SOLR-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723984#action_12723984
]
Noble Paul commented on SOLR-1246:
--
hi Rafal, go ahead and submit a patch
> StatsComponent
[
https://issues.apache.org/jira/browse/SOLR-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-1246:
Assignee: Noble Paul
> StatsComponent returing Double.MIN_VALUE when determining maximum value for
[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723975#action_12723975
]
Michael McCandless commented on SOLR-940:
-
Shalin I think that exception you got is a
StatsComponent returing Double.MIN_VALUE when determining maximum value for
negativ numbers
---
Key: SOLR-1246
URL: https://issues.apache.org/jira/browse/SOLR-1246
[
https://issues.apache.org/jira/browse/SOLR-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1227:
-
Attachment: SOLR-1227.patch
caching can be disabled for luke?show=schema and showfilerequesthandler
> sch
See http://hudson.zones.apache.org/hudson/job/Solr-trunk/843/changes
Changes:
[noble] SOLR-1244 JdbcDataSource uses wrong overload of getConnection on JNDI
DataSource
[noble] SOLR-1245 DIH eats up SQL exception
[shalin] SOLR-1214 followup -- Fix root cause of test failures by setting
solrHome
[
https://issues.apache.org/jira/browse/SOLR-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-1227:
Assignee: Noble Paul
> schema.jsp will be cached in browser
>
>
init-forrest-entities:
[mkdir] Created dir: /tmp/apache-solr-nightly/build
[mkdir] Created dir: /tmp/apache-solr-nightly/build/web
compile-solrj:
[mkdir] Created dir: /tmp/apache-solr-nightly/build/solrj
[javac] Compiling 83 source files to /tmp/apache-solr-nightly/build/solrj
[
https://issues.apache.org/jira/browse/SOLR-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-994:
Fix Version/s: (was: 1.4)
1.5
it is currently possible to add this Transformer explici
[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723938#action_12723938
]
Uwe Schindler commented on SOLR-940:
{quote}
Regarding Collector#acceptsDocsOutOfOrder, I
49 matches
Mail list logo