[
https://issues.apache.org/jira/browse/LUCENE-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782823#action_12782823
]
Michael McCandless commented on LUCENE-2037:
Can we, for this issue, focus on
On Wed, Nov 25, 2009 at 8:29 PM, Erick Erickson wrote:
> IMHO there are other reasons to upgrade to junit4 besides
> parallelization, there are some nice new capabilities. I
> suppose the analogous question is "why upgrade to
> Lucene 2.9?"
OK then I think we should do the upgrade, and separately
Since 3.0 is almost out of the door and development on Unicode support
for supplementary characters has already started heavily (I like the
word heavy - like uwe) I see a lot of stuff going on in the flex
branch which seems to be a huge change that might take quite a while
to finish / be releaseabl
I still think there's value to faster tests, even if they don't become
so fast as to enable "fully interactive testing".
Plus, this is an ongoing goal with time, not a one-time event. As we
create tests we should generally try to maximize coverage and minimize
CPU cost, as long as the effort is s
Hello Lucene users,
On behalf of the Lucene dev community (a growing community far larger than
just the committers) I would like to announce the release of Lucene Java
3.0.0:
The new version is mostly a cleanup release without any new features. All
deprecations targeted to be removed in version
JRA-3609 gets at yet another improvement I'd like to see in Jira,
which is the ability to customize subject-line for each comment added
to an issue.
EG I would have really liked to use the comment 'pathological GC
behavior' for this post:
https://issues.apache.org/jira/browse/LUCENE-2075?foc
[
https://issues.apache.org/jira/browse/LUCENE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782873#action_12782873
]
Nicolas Helleringer commented on LUCENE-1934:
-
As Chris work is being released
[
https://issues.apache.org/jira/browse/LUCENE-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782872#action_12782872
]
Nicolas Helleringer commented on LUCENE-1930:
-
As Chris work is being released
[
https://issues.apache.org/jira/browse/LUCENE-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782896#action_12782896
]
Chris Male commented on LUCENE-1930:
Hi Nicolas,
I have every intention to commit my
right - as soon as you have to start running the tests often enough,
any decent savings turns into less waiting and more work. Waiting for
tests to run is time that could be better spent elsewhere. And many of
us runthe tests *a lot* considering how long they take. And we will
only keep ad
On Nov 25, 2009, at 9:32 PM, Erick Erickson
wrote:
I suppose this implies that the
hard-core committers agree that as long as failed tests
are caught/corrected within a day things are fine.
Personally, I don't agree with that. Others are checking out,
updating, and using the tests to
[
https://issues.apache.org/jira/browse/LUCENE-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782908#action_12782908
]
Nicolas Helleringer commented on LUCENE-1930:
-
Ok ! I did not get that =)
O
[
https://issues.apache.org/jira/browse/LUCENE-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated LUCENE-1844:
---
Attachment: LUCENE-1844-Junit3.patch
Speeds up TestBooleanMinShouldMatch and TestCustomScore
[
https://issues.apache.org/jira/browse/LUCENE-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782915#action_12782915
]
Erick Erickson commented on LUCENE-1844:
OK, fire when ready Gridley. Pretty soon
[
https://issues.apache.org/jira/browse/LUCENE-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782916#action_12782916
]
Erick Erickson commented on LUCENE-2037:
Hold off on this patch until I get a chan
Despite my long rambling, I agree that speeding things up is worthwhile.
Just
not a huge deal for some of us poor peons who are on dinky little 2-core
machines and feel inadequate even *talking* to people who have *real*
machines ...
Time to go get ready to eat Turkey
Erick
On Thu, Nov 26, 2
[
https://issues.apache.org/jira/browse/LUCENE-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1844:
---
Attachment: LUCENE-1844.patch
OK I started from Erick's last patch, and trimmed back
[
https://issues.apache.org/jira/browse/LUCENE-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1844:
--
Assignee: Michael McCandless
> Speed up junit tests
>
>
>
[
https://issues.apache.org/jira/browse/LUCENE-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva updated LUCENE-1910:
---
Attachment: (was: LUCENE-1910.patch)
> Extension to MoreLikeThis to use tag information
[
https://issues.apache.org/jira/browse/LUCENE-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783010#action_12783010
]
Thomas D'Silva commented on LUCENE-1910:
Mark,
I refactored the code so that the
[
https://issues.apache.org/jira/browse/LUCENE-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva updated LUCENE-1910:
---
Attachment: LUCENE-1910.patch
> Extension to MoreLikeThis to use tag information
> -
Hey guys, I am a JIRA dev, so I thought I should throw in my 2c:
The root cause is most likely http://jira.atlassian.com/browse/JRA-15548
This bug was fixed in JIRA v4.0 and usually only effects customers with
lots of Issues (100,000's)
When a user saves changes to an Issue, we first store the
See my other email for what I think the problem is and what to do about it.
( http://jira.atlassian.com/browse/JRA-15548 )
> JIRA allows for administrative export of the database to XML. If
these don't export then something is really bad.
The DB holds the correct information, but Lucene is st
23 matches
Mail list logo
