[
https://issues.apache.org/jira/browse/LUCENE-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848560#action_12848560
]
Shai Erera commented on LUCENE-2342:
Took me a while to spot the typo :). Can you
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848565#action_12848565
]
Shai Erera commented on LUCENE-2339:
I personally haven't seen problem using NIO on
[
https://issues.apache.org/jira/browse/LUCENE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848571#action_12848571
]
Shai Erera commented on LUCENE-1482:
Well ... since Mark hasn't closed it yet (thanks
[
https://issues.apache.org/jira/browse/LUCENE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848589#action_12848589
]
Toke Eskildsen commented on LUCENE-2335:
I can see that I messed up reading your
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848591#action_12848591
]
Uwe Schindler commented on LUCENE-2339:
---
bq. I just wanted to avoid converting
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848591#action_12848591
]
Uwe Schindler edited comment on LUCENE-2339 at 3/23/10 7:17 AM:
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848606#action_12848606
]
Shai Erera commented on LUCENE-2339:
Sorry ... I was confused w/ the for loop of Java
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848626#action_12848626
]
Michael McCandless commented on LUCENE-2329:
Sweet, this looks great Michael!
[
https://issues.apache.org/jira/browse/LUCENE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848628#action_12848628
]
Michael McCandless commented on LUCENE-2335:
bq. I have used some time
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848631#action_12848631
]
Michael McCandless commented on LUCENE-2339:
I love CloseSafely! We do that
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848632#action_12848632
]
Michael McCandless commented on LUCENE-2328:
I think it's OK to make an
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848634#action_12848634
]
Earwin Burrfoot commented on LUCENE-2339:
-
bq. So unless LUCENE-1482 springs back
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848636#action_12848636
]
Shai Erera commented on LUCENE-2339:
I don't want to block the issue. If LUCENE-1482
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848648#action_12848648
]
Dawid Weiss commented on LUCENE-2298:
-
The dictionary's author states that:
[
https://issues.apache.org/jira/browse/LUCENE-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848649#action_12848649
]
Dawid Weiss commented on LUCENE-2341:
-
Robert, should I wait for Stempel patch first
https://issues.apache.org/jira/browse/INFRA-2567
On Mar 22, 2010, at 11:44 AM, Grant Ingersoll wrote:
Shall we merge the dev mailing lists? This should reduce the cross-posting
and can be completely automated (other than you may have to update your
client-side filters) and was part of the
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848670#action_12848670
]
Michael McCandless commented on LUCENE-2339:
bq. Let's mask it? That way the
[
https://issues.apache.org/jira/browse/LUCENE-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848672#action_12848672
]
Robert Muir commented on LUCENE-2341:
-
Dawid, sounds good. I had a few questions,
[
https://issues.apache.org/jira/browse/LUCENE-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848674#action_12848674
]
Robert Muir commented on LUCENE-2341:
-
oh yeah, and also, what about cases with
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848678#action_12848678
]
Earwin Burrfoot commented on LUCENE-2339:
-
Not right.
Imagine exception is thrown
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848685#action_12848685
]
Michael McCandless commented on LUCENE-2339:
Urgh... can we add a boolean arg
On Mar 22, 2010, at 8:27 AM, Uwe Schindler wrote:
Hi all,
the discussion where to do the development after the merge, now gets actual:
Currently a lusolr test-trunk is done as a branch inside solr
(https://svn.apache.org/repos/asf/lucene/solr/branches/newtrunk). The
question is, where
This looks good to me.
+1 on landing flex now.
On 03/22/2010 08:27 AM, Uwe Schindler wrote:
Hi all,
the discussion where to do the development after the merge, now gets actual:
Currently a lusolr test-trunk is done as a branch inside solr
On Mar 22, 2010, at 8:27 AM, Uwe Schindler wrote:
Hi all,
the discussion where to do the development after the merge, now gets actual:
Currently a lusolr test-trunk is done as a branch inside solr
(https://svn.apache.org/repos/asf/lucene/solr/branches/newtrunk). The
question is, where
For Solr, we can just move the current trunk to a 15 branch.
-Yonik
On Tue, Mar 23, 2010 at 9:39 AM, Grant Ingersoll gsing...@apache.org wrote:
On Mar 22, 2010, at 8:27 AM, Uwe Schindler wrote:
Hi all,
the discussion where to do the development after the merge, now gets actual:
Currently
[
https://issues.apache.org/jira/browse/LUCENE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848707#action_12848707
]
Robert Muir commented on LUCENE-1709:
-
Thanks Jason.
So for newtrunk I applied a
[
https://issues.apache.org/jira/browse/LUCENE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848712#action_12848712
]
Mark Miller commented on LUCENE-1709:
-
+1 on removing those flags - personally I find
[
https://issues.apache.org/jira/browse/LUCENE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848718#action_12848718
]
Michael McCandless commented on LUCENE-1709:
+1 for removing the flags and
Quick Status on where we are at:
The new trunk for the merge is now open:
https://svn.apache.org/repos/asf/lucene/dev/trunk/ All committers should have
the same rights that they had before.
Please do all development on those.
The new mailing list has been requested:
Of you have checkouts of the previous trunks that you don't want to
re-checkout, then use svn switch.
Solr trunk was moved to a 1.5 branch, so for old trunk checkouts, cd
into your directory and do
svn switch https://svn.apache.org/repos/asf/lucene/solr/branches/branch-1.5-dev
For newtrunk
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848729#action_12848729
]
Shai Erera commented on LUCENE-2339:
Mike, that's what I wrote above if someone does
On Mar 23, 2010, at 10:09 AM, Grant Ingersoll wrote:
3. Other nightly build stuff. My cron tabs, etc. I will update them to
point at the new trunk.
OK, I updated my cron tab for the site check out of Lucene. Not sure who
handles Solr.
On Tue, Mar 23, 2010 at 10:49 AM, Grant Ingersoll gsing...@apache.org wrote:
On Mar 23, 2010, at 10:09 AM, Grant Ingersoll wrote:
3. Other nightly build stuff. My cron tabs, etc. I will update them to
point at the new trunk.
OK, I updated my cron tab for the site check out of Lucene.
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848744#action_12848744
]
Michael McCandless commented on LUCENE-2339:
bq. So how about we call it
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848748#action_12848748
]
Michael Busch commented on LUCENE-2329:
---
{quote}
so it's surprising the savings was
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848753#action_12848753
]
Shai Erera commented on LUCENE-2339:
bq. But there is still a need to close
I changed the hudson nightly job of Lucene trunk to simply checkout the correct
folders (Lucene-only). This builds lucene separate from solr, so all artifacts
are build with a JDK 1.5. This enables solr to maybe move to 1.6.
I changed the solr build to checkout the new trunk and use a similar
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848767#action_12848767
]
Michael McCandless commented on LUCENE-2329:
bq. But, keep in mind that
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848769#action_12848769
]
Michael McCandless commented on LUCENE-2339:
bq. My assumption is that when
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848777#action_12848777
]
Shai Erera commented on LUCENE-2339:
Ok that's indeed different :). I guess we can
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848778#action_12848778
]
Uwe Schindler commented on LUCENE-2328:
---
I am fine now! Go for it! Policeman is
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848782#action_12848782
]
Michael Busch commented on LUCENE-2329:
---
{quote}
OK, but, RAM used by TermVectors*
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848785#action_12848785
]
Earwin Burrfoot commented on LUCENE-2339:
-
I'll get back to the issue in N hours
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848789#action_12848789
]
Michael McCandless commented on LUCENE-2328:
OK I will commit shortly! Thanks
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2328.
Resolution: Fixed
IndexWriter.synced field accumulates data leading to a Memory
I'm still slightly confused on in order and out of order collectors. I
mean, I get what they do, but, if I'm implementing a new collector (see
https://issues.apache.org/jira/browse/LUCENE-2215) that is going to be part of
core, should I implement two versions: one for in order and one for out
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848795#action_12848795
]
Grant Ingersoll commented on LUCENE-2127:
-
Hey Jason,
My tests are inconclusive
You can implement just the out of order collector, since it subsumes
the in-order case, and all will work fine.
However, if the collector can save CPU when docs are known to arrive
in-order (not all collectors can) it'd be good to make a separate
in-order one as well.
Mike
On Tue, Mar 23, 2010
On Mar 23, 2010, at 1:20 PM, Michael McCandless wrote:
You can implement just the out of order collector, since it subsumes
the in-order case, and all will work fine.
However, if the collector can save CPU when docs are known to arrive
in-order (not all collectors can) it'd be good to make
OK put it up! Sounds good :)
Mike
On Tue, Mar 23, 2010 at 1:54 PM, Grant Ingersoll gsing...@apache.org wrote:
On Mar 23, 2010, at 1:20 PM, Michael McCandless wrote:
You can implement just the out of order collector, since it subsumes
the in-order case, and all will work fine.
However, if
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848827#action_12848827
]
Michael Busch commented on LUCENE-2329:
---
{quote}
They save the object header
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848827#action_12848827
]
Michael Busch edited comment on LUCENE-2329 at 3/23/10 6:06 PM:
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848833#action_12848833
]
Michael McCandless commented on LUCENE-2329:
OK indeed it does sounds
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848842#action_12848842
]
Grant Ingersoll commented on LUCENE-2215:
-
I think in order to properly implement
[
https://issues.apache.org/jira/browse/LUCENE-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848853#action_12848853
]
Hoss Man commented on LUCENE-2323:
--
bq. If no one objects, (especially including Hoss
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848855#action_12848855
]
Michael Busch commented on LUCENE-2329:
---
Cool, will do! Thanks for the review and
Hi all,
I wanted to commit LUCENE-2329. I just checked out the new combined
trunk https://svn.apache.org/repos/asf/lucene/dev/trunk and ran ant
test. After 20 mins the build failed on the unmodified code (see
below). I hadn't applied my patch yet.
What's the status of the combined trunk?
The last hudson run worked two hours ago...
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Michael Busch [mailto:busch...@gmail.com]
Sent: Tuesday, March 23, 2010 8:37 PM
To:
Robert very recently committed some stuff that parallelizes the solr
tests that may need to be worked out in all cases still (if that is
indeed the problem here). A variety of devs have tested it, but there
may be a lingering issue?
No helpful errors printed above BUILD FAILED? The line the
Maybe, the Solr test TestLBHttpSolrServer failed for me randomly
before this parallelization though, and still does.
In general the jetty tests have caused me some grief.
But its also equally likely i broke it for you somehow...
Michael, can you try running with -Dsequential-tests=1 ?
Apologies
Thanks Michael, this isn't a parallel test problem at all, its a
sporatic problem with solr's jetty tests (the same problem I mentioned
in the previous response).
You might/will see this problem running the tests sequentially too.
Test org.apache.solr.client.solrj.embedded.JettyWebappTest FAILED
On 3/23/10 1:07 PM, Robert Muir wrote:
Maybe, the Solr test TestLBHttpSolrServer failed for me randomly
before this parallelization though, and still does.
In general the jetty tests have caused me some grief.
But its also equally likely i broke it for you somehow...
Michael, can you try
I see. And all the other exceptions printed are expected?
Michael
On 3/23/10 1:20 PM, Robert Muir wrote:
Thanks Michael, this isn't a parallel test problem at all, its a
sporatic problem with solr's jetty tests (the same problem I mentioned
in the previous response).
You might/will see this
Yeah its a bit confusing... before, exceptions happening in other
threads were silently hidden.
Uwe fixed this in Lucene I think, and right now the verbosity is
cranked for Solr, too.
Yonik is hacking away at these tests to quiet the ones that are truly
expected exceptions...
At least I think I
Uh, the IRC logs... Do people really think making those *searchable* would be
useful?
I think they'd be *extremely* noisy and hard to interpret without a person
really just sequentially reading them. Lots of people talking at the same
time, multiple topics, lots of very short intertwined
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848896#action_12848896
]
Shai Erera commented on LUCENE-2215:
I've reviewed PagingCollector.java and the first
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-2215:
Attachment: LUCENE-2215.patch
Here's an update of Aaron's work with the following
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848904#action_12848904
]
Grant Ingersoll commented on LUCENE-2215:
-
bq. BTW, I've noticed that you don't
[
https://issues.apache.org/jira/browse/LUCENE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848908#action_12848908
]
Shai Erera commented on LUCENE-2215:
I must admit I don't like throwing UOE. I imagine
If you do an update your issue should be resolved. This is something we
ran into the other day as well, and have been solving it a bit at a time ;)
- Mark
On 03/23/2010 04:29 PM, Robert Muir wrote:
Yeah its a bit confusing... before, exceptions happening in other
threads were silently hidden.
On Tue, Mar 23, 2010 at 5:07 PM, Michael Busch busch...@gmail.com wrote:
OK I reran the tests sequentially with my LUCENE-2329 patch applied. The
same test failed again:
[junit] Test org.apache.solr.client.solrj.embedded.JettyWebappTest FAILED
Everything else looks good. So it should be
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch resolved LUCENE-2329.
---
Resolution: Fixed
Committed revision 926791.
Use parallel arrays instead of PostingList
On 3/23/10 2:12 PM, Yonik Seeley wrote:
On Tue, Mar 23, 2010 at 5:07 PM, Michael Buschbusch...@gmail.com wrote:
OK I reran the tests sequentially with my LUCENE-2329 patch applied. The
same test failed again:
[junit] Test org.apache.solr.client.solrj.embedded.JettyWebappTest FAILED
On Tue, Mar 23, 2010 at 01:30:42PM -0700, Otis Gospodnetic wrote:
Archiving the logs feels like it would be useful, but realistically
speaking, they would be pretty big and who has the time to read them after
the fact?
Someone who participated in the chat reviewing it while preparing a
[
https://issues.apache.org/jira/browse/LUCENE-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848972#action_12848972
]
John Wang commented on LUCENE-2252:
---
Hi Mike:
Sorry for the late reply. We have
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848973#action_12848973
]
Earwin Burrfoot commented on LUCENE-2328:
-
Mike, you missed latest patch, with
76 matches
Mail list logo
