[
https://issues.apache.org/jira/browse/SOLR-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967118#action_12967118
]
tom liu commented on SOLR-1395:
---
in proxy:
katta.node.properties:
#node.server.class=net.sf.ka
[
https://issues.apache.org/jira/browse/LUCENE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967115#action_12967115
]
Uwe Schindler commented on LUCENE-2235:
---
Hi Nick,
thanks for reporting this. Your pr
Search Index Generation fails
-
Key: LUCENE-2800
URL: https://issues.apache.org/jira/browse/LUCENE-2800
Project: Lucene - Java
Issue Type: Bug
Components: Index
Affects Versions: 2.0.0
Envir
[
https://issues.apache.org/jira/browse/LUCENE-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967100#action_12967100
]
Shai Erera commented on LUCENE-2471:
At some point IndexInput/Output.copyBytes did use
[
https://issues.apache.org/jira/browse/SOLR-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967086#action_12967086
]
JohnWu commented on SOLR-1395:
--
TomLiu:
I still jam in the query dipatch to subproxy!
[
https://issues.apache.org/jira/browse/SOLR-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967085#action_12967085
]
Israel Ekpo commented on SOLR-1913:
---
I am glad it worked out for you.
I was going to ask
>
> Yet another way would be to declare the problem non-existent and screw our
> users by insulting them with a honking great mass of changes without any
> indication about what they are or how they are inter-related. (You won't be
> surprised at this point, I think, by my -1 to this.)
Right,
Hi Chris,
On 12/5/2010 at 10:36 PM, Chris Mattman wrote:
> Yep, like you state below JIRA *could* be configured to deal with this.
>
> In all honesty, putting tons of thought and effort into how to precisely
> deal with the changes you specify below might be somewhat overkill.
I think dumping CH
Hi Steven,
Yep, like you state below JIRA *could* be configured to deal with this.
In all honesty, putting tons of thought and effort into how to precisely deal
with the changes you specify below might be somewhat overkill.
Cheers,
Chris
On Dec 5, 2010, at 12:17 PM, Steven A Rowe wrote:
> On
Hi Robert,
True, JIRA isn't a perfect solution for this matter, but works good enough
usually since many times (especially with prodding) those same users who report
the bugs are those that report the JIRA issues.
Cheers,
Chris
On Dec 5, 2010, at 9:18 AM, Robert Muir wrote:
> On Sun, Dec 5, 2
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967076#action_12967076
]
Robert Muir commented on SOLR-1979:
---
{quote}
It makes sense to allow for detecting languag
On Sun, Dec 5, 2010 at 9:12 PM, Simon Willnauer
wrote:
> I personally consider android a valid platform for lucene and we
> should try to reduce the pain for android folks as much as possible.
> Changing supported platforms is a totally different thing to me.
>
good, you can start a separate subp
[
https://issues.apache.org/jira/browse/LUCENE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967064#action_12967064
]
Chris Male commented on LUCENE-2599:
I just noticed that Solr depends upon some method
Mark, Robert can we keep things constructive here please. The issue
what DM is reporting might not be valid on "true" java and nobody asks
for specializing code for the android platform. I figure from uwes
response that this issue can be solved easily so not a real big deal.
If not we should try to
[
https://issues.apache.org/jira/browse/LUCENE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967063#action_12967063
]
Simon Willnauer commented on LUCENE-2599:
-
Chris, I think we should not add an emp
[
https://issues.apache.org/jira/browse/LUCENE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967057#action_12967057
]
Nick Pellow commented on LUCENE-2235:
-
I just upgraded to 3.0.3 and we started getting
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967048#action_12967048
]
Grant Ingersoll commented on SOLR-1979:
---
Note, the patch still needs more tests and ne
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1979:
--
Attachment: SOLR-1979.patch
Here's a patch that passes the tests. Note, I modified the Solr bas
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967046#action_12967046
]
Grant Ingersoll commented on SOLR-1979:
---
bq. @Grant: I actually planned to do the regE
On 12/5/10 6:15 PM, Robert Muir wrote:
On Sun, Dec 5, 2010 at 6:10 PM, Mark Miller wrote:
On 12/5/10 5:05 PM, Robert Muir wrote:
what I am saying, is that this is a java project, and I don't want to
write to some least common denominator/intersection of java and android.
So don't - DM submi
bq. Perhaps that is not possible or too difficult in every case
To clarify - sounds like I could be saying, well, perhaps we can't
improve every case, but some we can. I'm saying *too difficult in every*
case - even if we don't try and *fix a single case* - its still
beneficial for you to rep
On Sun, Dec 5, 2010 at 6:10 PM, Mark Miller wrote:
> On 12/5/10 5:05 PM, Robert Muir wrote:
>>
>> what I am saying, is that this is a java project, and I don't want to
>> write to some least common denominator/intersection of java and android.
>
> So don't - DM submitting cases that don't work and
Hey,
I'm trying to use the lucene FieldCache for some custom field collapsing
implementation: basically i'm collapsing on a non-stored field,
and so am using the fieldcache to retrieve field value instances during run.
I noticed I'm getting some OOM's after deploying it, and after looking into
it
On 12/5/10 5:05 PM, Robert Muir wrote:
what I am saying, is that this is a java project, and I don't want to
write to some least common denominator/intersection of java and android.
So don't - DM submitting cases that don't work and you not giving a shit
are not mutually exclusive.
- Mark
[
https://issues.apache.org/jira/browse/SOLR-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967035#action_12967035
]
Jon Bodner commented on SOLR-1048:
--
The issue is still present in the 1.4.1 code base for S
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967032#action_12967032
]
Jan Høydahl commented on SOLR-1979:
---
@Robert: Yes, there must be a way to tell whether or
what I am saying, is that this is a java project, and I don't want to write
to some least common denominator/intersection of java and android. if an api
doesn't exist in android, I could care less. inzstead, why can't interest
parties have a little project where we port lucene java (perhaps a trivi
On Dec 5, 2010, at 3:34 PM, Yonik Seeley wrote:
> On Sun, Dec 5, 2010 at 3:28 PM, Grant Ingersoll wrote:
>> Anyone have any thoughts on testing UpdateProcessorChain (and Factory). In
>> looking at the Signature (dedup) tests, it seems a little clunky, yet the
>> Solr base test class adoc (and
[
https://issues.apache.org/jira/browse/SOLR-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967022#action_12967022
]
Yonik Seeley commented on SOLR-2266:
OK, here's my guess: it's probably due to multiple
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967019#action_12967019
]
Robert Muir commented on SOLR-1979:
---
bq. Yeah, that makes sense, however, I believe Tika r
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967016#action_12967016
]
Yonik Seeley commented on SOLR-1979:
bq. The new field is made by concatenating the orig
I have an interest - don't really care if it uses true java or not. I
say keep it coming. Where/if it makes sense, why not make lucene work
better with it. Perhaps that is not possible or too difficult in every
case - but I'd still like to see the cases pop up. Better than those
spam wiki updat
Thanks Uwe (and others). We'll adapt.
Is there any interest here in knowing if there are any other problems regarding
Lucene on Android? From what I see, it is the first mobile platform on which
Lucene can run.
-- DM
On Dec 5, 2010, at 5:16 AM, Uwe Schindler wrote:
> Hi DM,
>
> In Lucene 3.0
On Sun, Dec 5, 2010 at 3:28 PM, Grant Ingersoll wrote:
> Anyone have any thoughts on testing UpdateProcessorChain (and Factory). In
> looking at the Signature (dedup) tests, it seems a little clunky, yet the
> Solr base test class adoc (and related methods) don't seem to support
> specifying t
Gotto love a wrong email address autocomplete.
On 12/5/10 3:26 PM, Mark Miller wrote:
This shouldn't normally be something that you need to do with jruby I'd
think - but Avram asked about this on the call back when there where ui
running out of memory issues.
Since we require java 6, this is ac
Anyone have any thoughts on testing UpdateProcessorChain (and Factory). In
looking at the Signature (dedup) tests, it seems a little clunky, yet the Solr
base test class adoc (and related methods) don't seem to support specifying the
Update handler to hit.
Thoughts?
-Grant
---
This shouldn't normally be something that you need to do with jruby I'd
think - but Avram asked about this on the call back when there where ui
running out of memory issues.
Since we require java 6, this is actually really easy.
Java itself comes with jconsole. It should be on your path. You j
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967011#action_12967011
]
Grant Ingersoll commented on SOLR-1979:
---
Another thought, here, is that, over time, th
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967010#action_12967010
]
Grant Ingersoll commented on SOLR-1979:
---
bq. I would like to see RFC 3066 instead
Yea
On 12/5/2010 at 12:19 PM, Robert Muir wrote:
> On Sun, Dec 5, 2010 at 12:08 PM, Mattmann, Chris A (388J)
> wrote:
> > Hi Mark,
> >
> > RE: the credit system. JIRA provides a contribution report here, like
> > this one that I generated for Lucene 3.1:
> >
>
> My concern with this is that it leaves
You are quite right. I put a bug into JIRA, basically the layout.vm was
referring to a older version of jquery then what was in the Solr.war file! I
do think though that having everything all in the /velocity directory would
make it easier for someone who is new to Solr to grok how to customiz
[
https://issues.apache.org/jira/browse/LUCENE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-1541.
---
Resolution: Won't Fix
I don't think a fix is needed anymore.
> Trie range - make trie range
java.lang.ArrayIndexOutOfBoundsException in field cache when using a tdate
field in a boost function with rord()
Key: SOLR-2266
URL: https://issues.ap
On Sun, Dec 5, 2010 at 12:08 PM, Mattmann, Chris A (388J)
wrote:
> Hi Mark,
>
> RE: the credit system. JIRA provides a contribution report here, like this
> one that I generated for Lucene 3.1:
>
My concern with this is that it leaves out important email contributors.
For example if a user repo
Hi Mark,
RE: the credit system. JIRA provides a contribution report here, like this one
that I generated for Lucene 3.1:
http://s.apache.org/BpL
Just click on Reports > Contribution Report in the upper right of JIRA on the
main project summary page.
We've been using this in Tika since the beg
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966978#action_12966978
]
Robert Muir commented on SOLR-1979:
---
We really need to not be using ISO 639-1 here.
For
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1979:
--
Attachment: SOLR-1979.patch
I took Jan's and Tommaso's patches and reworked them a bit. It seem
[
https://issues.apache.org/jira/browse/SOLR-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966718#action_12966718
]
Yonik Seeley edited comment on SOLR-2158 at 12/5/10 10:38 AM:
--
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966972#action_12966972
]
Robert Muir commented on SOLR-1979:
---
bq. cause that distance measure is kind of an interna
[
https://issues.apache.org/jira/browse/SOLR-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966971#action_12966971
]
Yonik Seeley commented on SOLR-2158:
OK, so we upgraded jetty... but the "failed to resp
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966970#action_12966970
]
Jan Høydahl commented on SOLR-1979:
---
The idField input parameter is just used for decent l
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966964#action_12966964
]
Jan Høydahl commented on SOLR-1979:
---
Simply allowing to set the threshold for isReasonably
[
https://issues.apache.org/jira/browse/LUCENE-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966963#action_12966963
]
Robert Muir commented on LUCENE-2793:
-
There is another problem we should solve here,
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966955#action_12966955
]
Grant Ingersoll commented on SOLR-1979:
---
See http://wiki.apache.org/solr/LanguageDetec
[
https://issues.apache.org/jira/browse/SOLR-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-2244.
---
Resolution: Won't Fix
Actually, I'm going to switch back to SOLR-1979, as it is a superset of
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned SOLR-1979:
-
Assignee: Grant Ingersoll
> Create LanguageIdentifierUpdateProcessor
> ---
On Sun, Dec 5, 2010 at 1:46 AM, Apache Hudson Server
wrote:
> Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2211/
>
> 1 tests failed.
> REGRESSION: org.apache.solr.update.AutoCommitTest.testMaxTime
>
There's still a timing issue in this test I think. I modified it a
wh
On Sun, Dec 5, 2010 at 9:00 AM, Yonik Seeley wrote:
> Well, darn upgrading jetty didn't seem to help this.
>
I was getting really hopeful for a while!
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additiona
Well, darn upgrading jetty didn't seem to help this.
-Yonik
http://www.lucidimagination.com
On Sun, Dec 5, 2010 at 7:05 AM, Apache Hudson Server
wrote:
> Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2221/
>
> 1 tests failed.
> REGRESSION: org.apache.solr.TestDi
[
https://issues.apache.org/jira/browse/LUCENE-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966943#action_12966943
]
Robert Muir commented on LUCENE-2763:
-
+1, looks good to me.
> Swap URL+Email recogn
[
https://issues.apache.org/jira/browse/LUCENE-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966933#action_12966933
]
Robert Muir commented on LUCENE-2798:
-
Steven, before working too hard on the jdk coll
On Sat, Dec 4, 2010 at 6:16 PM, DM Smith wrote:
> Should Android be a supported client OS?
Not by lucene java, since Android isn't java.
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mai
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2221/
1 tests failed.
REGRESSION: org.apache.solr.TestDistributedSearch.testDistribSearch
Error Message:
Some threads threw uncaught exceptions!
Stack Trace:
junit.framework.AssertionFailedError: Some threads threw uncaugh
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2218/
1 tests failed.
REGRESSION: org.apache.solr.TestDistributedSearch.testDistribSearch
Error Message:
Some threads threw uncaught exceptions!
Stack Trace:
junit.framework.AssertionFailedError: Some threads threw uncaugh
Hi DM,
In Lucene 3.0.3, NativeFSLockFactory no longer aquires a test log and does
not need the process ID anymore, so java.lang.management package is no
longer used.
In general, Lucene Java is compatible to the Java 5 SE specification.
Android uses Harmony and therefore we cannot guarantee compat
On 5 December 2010 00:16, DM Smith wrote:
> Should Android be a supported client OS?
> If so, wouldn't it be better not to have OS specific if-then-else and use
> reflection or something else?
>
Well Lucene is only relying on standard JVM API. The fact that Androïd is
using a non-standard JVM is
The current code that works on Android with 2.9.1, but fails with 3.0.2:
Directory dir = FSDirectory.open(file);
...
do something with directory
...
The error we're seeing is:
12-04 21:34:41.629: WARN/System.err(23160): java.lang.NoClassDefFoundError:
java.lang.management.ManagementFactory
12-04
67 matches
Mail list logo
