I'll fix, it's a probabilistic test and (I thought) well below what's
possible but this particular seed exceeds it.
By the way --
> [junit4:junit4] JVM J0: 1.48 .. 168.78 = 167.31s
> [junit4:junit4] JVM J1: 1.47 .. 168.25 = 166.78s
> [junit4:junit4] JVM J2: 1.48 .. 168.52 =
[
https://issues.apache.org/jira/browse/SOLR-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raintung Li updated SOLR-3749:
--
Fix Version/s: (was: 4.0-BETA)
(was: 4.0-ALPHA)
Affects Version/s:
[
https://issues.apache.org/jira/browse/SOLR-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raintung Li updated SOLR-3749:
--
Fix Version/s: 4.0-BETA
4.0
Affects Version/s: 4.0
> Default syncLeve
Mark Miller created SOLR-3752:
-
Summary: Currently it seems that when a leader goes down, he stays
marked as the leader in the ClusterState - it's not strictly necessary, but I
think the leader should be cleared until the new one is elected.
Mark Miller created SOLR-3751:
-
Summary: Add defensive checks against errant updates to distrib
update processor.
Key: SOLR-3751
URL: https://issues.apache.org/jira/browse/SOLR-3751
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3750:
--
Fix Version/s: 5.0
> On session expiration, we should explicitly wait some time before running the
Mark Miller created SOLR-3750:
-
Summary: On session expiration, we should explicitly wait some
time before running the leader sync process so that we are sure every node
participates.
Key: SOLR-3750
URL: https://issu
[
https://issues.apache.org/jira/browse/SOLR-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3750:
--
Component/s: SolrCloud
> On session expiration, we should explicitly wait some time before running t
Thanks, Mike, that was quick!
Maven and IntelliJ now both successfully compile.
Steve
-Original Message-
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Wednesday, August 22, 2012 7:18 PM
To: dev@lucene.apache.org
Subject: Re: Maven and IntelliJ (but not Ant) compilati
Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java6/15106/
No tests ran.
Build Log:
[...truncated 9110 lines...]
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected
reader termination
hudson.remoting.RequestAbortedException:
hudson.remoting.RequestAbor
[
https://issues.apache.org/jira/browse/SOLR-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raintung Li updated SOLR-3749:
--
Summary: Default syncLevel cannot be configured by solrconfig.xml for
updateLog(transaction log) (was:
Michael McCandless created LUCENE-4322:
--
Summary: Can we make oal.util.packed.BulkOperation* smaller?
Key: LUCENE-4322
URL: https://issues.apache.org/jira/browse/LUCENE-4322
Project: Lucene - Core
OK I committed the refactoring ... does this make Maven/Intellij happy...?
Mike McCandless
http://blog.mikemccandless.com
On Wed, Aug 22, 2012 at 7:08 PM, Michael McCandless
wrote:
> Urgh.
>
> I'll refactor this enormous source file into separate files...
> hopefully that fixes the immediate is
Urgh.
I'll refactor this enormous source file into separate files...
hopefully that fixes the immediate issue so you all can compile again.
I'll open an issue to see if we can reduce this... it really is
immense. EG maybe we don't need to specialize encode ...
Mike McCandless
http://blog.mikem
[
https://issues.apache.org/jira/browse/SOLR-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Fowler updated SOLR-3304:
--
Attachment: SOLR-3304_Solr_fields_for_Lucene_spatial_module (fieldName in
Strategy) - indexableFields.pa
Am 21.08.2012 07:14, schrieb Andi Vajda:
> Please vote to release these artifacts as PyLucene 3.6.1-2.
-1, sorry :)
test_ICUTransformFilter.py is segfaulting on my system. I haven't been
able to get a sensible stack trace yet. I'm going to recompile
everything with debug infos tomorrow.
OS: Ubun
On Wed, Aug 22, 2012 at 4:24 PM, Steven A Rowe wrote:
> On Win7, I'm getting compilation failures on branch_4x and trunk, under Maven
> (2.2.1 and 3.0.4) and IntelliJ (11.1.3). Under Ant (1.8.2), compilation
> succeeds. I've tried Oracle JDK 1.6.0_21 and 1.6.0_34, both 64-bit, and both
> beha
[
https://issues.apache.org/jira/browse/LUCENE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-4317.
---
Resolution: Fixed
Committed trunk revision 1376261, 4.x revision 1376265
>
See
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
See
--
[...truncated 950 lines...]
[junit4:junit4]
[junit4:junit4] Suite:
org.apache.lucene.util.junitcompat.TestExceptionInBeforeClassHooks
[junit4:junit4] Completed on J5 in 0.28s, 3 tests
[junit4:junit4]
[junit4:junit4] Suite: org.apache.lucene.search
Compilation succeeds for me on Linux using my built-from-source OpenJDK 6 b25
(still not sure what the Oracle-equivalent version is; "javac -version" reports
"javac 1.6.0-internal"). This is consistent with the ASF Jenkins Maven build
success today using OpenJDK 1.6.0_32. - Steve
-Original
On Win7, I'm getting compilation failures on branch_4x and trunk, under Maven
(2.2.1 and 3.0.4) and IntelliJ (11.1.3). Under Ant (1.8.2), compilation
succeeds. I've tried Oracle JDK 1.6.0_21 and 1.6.0_34, both 64-bit, and both
behave the same (success under Ant, failure under Maven and Intelli
Sorry, I missed this thread and reported the same thing.
I think i got the links working, I'll see if i can figure out some of
this formatting.
I dont know any of this much myself, only barely squeezing by to get
the lucene Java releases out.
If anyone wants to help, here is link with a video on
[
https://issues.apache.org/jira/browse/LUCENE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4317:
--
Attachment: LUCENE-4317-2.patch
Patch with test added. Setting to null before or after close d
[
https://issues.apache.org/jira/browse/LUCENE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439778#comment-13439778
]
Robert Muir commented on LUCENE-4317:
-
Looks good, but i think we only need to set s
[
https://issues.apache.org/jira/browse/LUCENE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4317:
--
Attachment: LUCENE-4317-2.patch
Patch. It refactors ReusableStringReader a bit and also adds s
[
https://issues.apache.org/jira/browse/LUCENE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reopened LUCENE-4317:
---
I reopen this one to fix a second reuse problem:
- It does not reuse the StringReader like Lucen
Yeah the SOLR-1093 itself is a little vague but the core idea is to run
multiple queries in a request. The patch is an implementation that runs the
sub queries serially.
On Wed, Aug 22, 2012 at 10:27 AM, Mikhail Khludnev <
mkhlud...@griddynamics.com> wrote:
> SOLR-1093, which is a little bit vagu
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4321.
-
Resolution: Fixed
> java.io.FilterReader considered harmful
> --
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4321:
Attachment: LUCENE-4321.patch
Good idea Uwe.
> java.io.FilterReader considered ha
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439692#comment-13439692
]
Uwe Schindler commented on LUCENE-4321:
---
Ah one thing:
FilteredReader in Java passe
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439691#comment-13439691
]
Uwe Schindler commented on LUCENE-4321:
---
+1, I am fine now. CharFilter now looks el
What I've seen done in the past that _might_ work is, rather than
some arbitrary threshold applied across different search results, use
a delta between two successive scores as your cutoff. For instance,
say you had three documents with scores like:
doc 1 - .90
doc 2 - .80
doc 3 - .20
The delta b
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439668#comment-13439668
]
Michael McCandless commented on LUCENE-4321:
+1
Sneaky trap.
[
https://issues.apache.org/jira/browse/SOLR-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439666#comment-13439666
]
Uwe Schindler commented on SOLR-3685:
-
Hi,
another thing to take into account: Java all
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-4.x/11/
No tests ran.
Build Log:
[...truncated 2973 lines...]
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected
termination of the channel
hudson.remoting.RequestAbortedException:
hudson.remoting.Request
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439609#comment-13439609
]
Dawid Weiss commented on LUCENE-4321:
-
So there was a bug hidden in that filterreader
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439597#comment-13439597
]
Robert Muir commented on LUCENE-4321:
-
{quote}
+1. Does MappingCharFilter really supp
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439595#comment-13439595
]
Uwe Schindler commented on LUCENE-4321:
---
+1. Does MappingCharFilter really support
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4321:
Attachment: LUCENE-4321.patch
Updated patch removing delegation for those methods so we have reade
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439586#comment-13439586
]
Robert Muir commented on LUCENE-4321:
-
We don't need to make these final: we should j
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439581#comment-13439581
]
Uwe Schindler commented on LUCENE-4321:
---
I am just thinking about markSupported(),
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439581#comment-13439581
]
Uwe Schindler edited comment on LUCENE-4321 at 8/23/12 1:51 AM:
---
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4321:
Attachment: LUCENE-4321.patch
Updated patch with the in->input rename. I think this is ready to go
[
https://issues.apache.org/jira/browse/LUCENE-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439566#comment-13439566
]
Sabbir Kumar Manandhar commented on LUCENE-2810:
any working example?
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439564#comment-13439564
]
Robert Muir commented on LUCENE-4321:
-
+1. I'll update the patch.
>
SOLR-1093, which is a little bit vague itself, doesn't help for
implementing my approach, because second query is build in according to the
results of the first one.
On Wed, Aug 22, 2012 at 3:37 PM, Karthick Duraisamy Soundararaj <
d.s.karth...@gmail.com> wrote:
> Hey Mikhail,
>
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439560#comment-13439560
]
Uwe Schindler commented on LUCENE-4321:
---
In 3.x the delegate was named "input", thi
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4321:
Attachment: LUCENE-4321.patch
Also added tests.
In the patch, MockTokenizer switches up its read
[
https://issues.apache.org/jira/browse/LUCENE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4321:
Attachment: LUCENE-4321.patch
Updated patch: made 'in' final as Dawid suggested.
Additionally I k
[
https://issues.apache.org/jira/browse/SOLR-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1854.
Resolution: Not A Problem
> wrong calc of numFound in DistributedSearch
> --
[
https://issues.apache.org/jira/browse/SOLR-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439482#comment-13439482
]
Yonik Seeley commented on SOLR-1854:
Distributed search removes *some* duplicates (only
[
https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439463#comment-13439463
]
Franco Callari commented on LUCENE-4314:
Michael, you are welcome. Thanks for the
[
https://issues.apache.org/jira/browse/SOLR-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Breitner updated SOLR-1854:
--
Comment: was deleted
(was: I have the same issue with Solr 3.5.
Two searches over 4 shards. One
[
https://issues.apache.org/jira/browse/SOLR-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439442#comment-13439442
]
Daniel Breitner commented on SOLR-1854:
---
I have the same issue with Solr 3.5.
Two se
Hey Mikhail,
Yes. Thats a very good idea and a certain solution for my
problem:). But two solr calls for each search results might be a concern.
Maybe I should tweak https://issues.apache.org/jira/browse/SOLR-1093 a
little bit so it takes the grouping results and boots them.
Othe
[
https://issues.apache.org/jira/browse/LUCENE-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439398#comment-13439398
]
Grant Ingersoll commented on LUCENE-2810:
-
It's now possible, at least, via the C
[
https://issues.apache.org/jira/browse/SOLR-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439388#comment-13439388
]
alsadi commented on SOLR-3747:
--
Yes, Eric I agree with you that score is not a percent and if
[
https://issues.apache.org/jira/browse/SOLR-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raintung Li updated SOLR-3749:
--
Comment: was deleted
(was: java code)
> Default syncLevel can be configured by solrconfig.xml for
[
https://issues.apache.org/jira/browse/SOLR-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raintung Li updated SOLR-3749:
--
Attachment: configpatch
> Default syncLevel can be configured by solrconfig.xml for
> updateLog(tra
[
https://issues.apache.org/jira/browse/SOLR-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raintung Li updated SOLR-3749:
--
Attachment: patch.txt
java code
> Default syncLevel can be configured by solrconfig.xml
Raintung Li created SOLR-3749:
-
Summary: Default syncLevel can be configured by solrconfig.xml for
updateLog(transaction log)
Key: SOLR-3749
URL: https://issues.apache.org/jira/browse/SOLR-3749
Project: S
> All filters must be final and they are?:
Ooops, yeah, I had to confuse something. Ok, I'll see what I can come up with.
Dawid
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h..
All filters must be final and they are?:
public final class StopFilter extends FilteringTokenFilter
public final class JapanesePartOfSpeechStopFilter extends FilteringTokenFilter
In all cases you can move your special filter into the package of
FilteringTokenFilter
-
Uwe Schindler
H.-H.-M
Yeah, this is exactly what I was thinking about and it even worked
(accept being protected is not a huge problem because these classes
are not final so I can open it up using a local subclass). I just
wasn't sure if this isn't too hacky. Thanks Uwe.
Dawid
On Wed, Aug 22, 2012 at 10:03 AM, Uwe Sch
You could misuse the attributes API:
All filters in a chain have the same attributes. This is achieved by the
chaining (new TokenFilter(other TS) shares the attributes). What you could do
to be non-linear in chaining:
Create the "helpers" that are not part of the chain, by linking them to th
66 matches
Mail list logo
