[
https://issues.apache.org/jira/browse/LUCENE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848565#action_12848565
]
Shai Erera commented on LUCENE-2339:
I personally haven't seen problem using NIO on Wi
[
https://issues.apache.org/jira/browse/LUCENE-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848560#action_12848560
]
Shai Erera commented on LUCENE-2342:
Took me a while to spot the typo :). Can you repr
DisjunctionSumScorer explain
Key: LUCENE-2342
URL: https://issues.apache.org/jira/browse/LUCENE-2342
Project: Lucene - Java
Issue Type: Bug
Components: Search
Reporter: Gary Yngve
[
https://issues.apache.org/jira/browse/LUCENE-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848484#action_12848484
]
Renaud Delbru commented on LUCENE-2340:
---
{quote}
The block is "shared" across postin
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848475#action_12848475
]
Michael Busch edited comment on LUCENE-2329 at 3/23/10 12:51 AM:
---
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848475#action_12848475
]
Michael Busch commented on LUCENE-2329:
---
I did some performance experiments:
I inde
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848427#action_12848427
]
Earwin Burrfoot commented on LUCENE-2328:
-
I do not touch *IndexInput, these shoul
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2339:
Attachment: LUCENE-2339.patch
1 -> I googled all around and nobody mentions any problems s
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848385#action_12848385
]
Uwe Schindler commented on LUCENE-2328:
---
Ahm,
one question, why does this patch rei
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2328:
Attachment: LUCENE-2328.patch
added comment to jdocs
> IndexWriter.synced field accumula
[
https://issues.apache.org/jira/browse/LUCENE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848380#action_12848380
]
Michael McCandless commented on LUCENE-2335:
bq. The sort-first-then-resolve-S
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848376#action_12848376
]
Shai Erera commented on LUCENE-2339:
Patch looks good! Few comments:
# is it safe to
Thank you so much, gonna try both options. Im trying to find some Similarity
examples too.
Andrzej Bialecki wrote:
>
> On 2010-03-22 18:06, zsl wrote:
>>
>> I was thinking about that, but i dont know if it is the best option. Ty.
>
> There is a certain trick to do this with the current API (let
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2339:
Attachment: LUCENE-2339.patch
Patch with overridable copyTo(), based off trunk+LUCENE-2328
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848341#action_12848341
]
Shai Erera commented on LUCENE-2328:
Earwin, can you add a deprecation message to sync
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848331#action_12848331
]
Earwin Burrfoot commented on LUCENE-2339:
-
bq. Google says that with certain restr
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848324#action_12848324
]
Michael McCandless commented on LUCENE-2328:
Patch looks great Earwin -- I'll
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2328:
Attachment: LUCENE-2328.patch
Clean patch against trunk
> IndexWriter.synced field accum
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2328:
Attachment: LUCENE-2328.patch
New patch.
FSyncStrategy removed, default inlined. All our D
[
https://issues.apache.org/jira/browse/LUCENE-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848305#action_12848305
]
Michael McCandless commented on LUCENE-2340:
bq. This can be problematic and c
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2331.
Resolution: Fixed
Committed on newtrunk.
> Add NoOpMergePolicy
>
On 03/22/2010 at 2:30 PM, Yonik Seeley wrote:
> On Mon, Mar 22, 2010 at 2:20 PM, Ryan McKinley
> wrote:
> > I'm confused... what is the need for a new name? The only place where
> > there is a conflict is in the top level svn tree...
>
> Agree, no need to re-brand.
Hmm, I've apparently misunder
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848284#action_12848284
]
Michael McCandless commented on LUCENE-2339:
OK this sounds like a good plan!
Right. That was exactly my understanding .. I guess instead of "ONE thing" I
should have written "single project" ... but I think you get my point.
BTW, this thread happens on java-dev only ...
Shai
On Mon, Mar 22, 2010 at 8:35 PM, Yonik Seeley wrote:
> On Mon, Mar 22, 2010 at 2:25 PM, Shai Er
[
https://issues.apache.org/jira/browse/LUCENE-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Renaud Delbru updated LUCENE-2340:
--
Attachment: LUCENE-1458-FixedIntBlockIndexOutput.patch
Fixed SimpleIntBlockIndex* and added un
On 2010-03-22 18:06, zsl wrote:
I was thinking about that, but i dont know if it is the best option. Ty.
There is a certain trick to do this with the current API (let's hope the
new API is more .. flexible .. ? ;) )
Implement a dummy Searcher that delegates most of its work to the real
Sea
On Mon, Mar 22, 2010 at 2:25 PM, Shai Erera wrote:
> To the best of my knowledge, it
> hasn't been decided that Lucene and Solr merge and become ONE thing
Depends on what the meaning of "thing" is ;-)
We have merged into one development project. But Lucene and Solr as
separate downloads will re
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848273#action_12848273
]
Robert Muir commented on LUCENE-2298:
-
Dawid, thanks... so it is "pick your poison" af
explore morfologik integration
--
Key: LUCENE-2341
URL: https://issues.apache.org/jira/browse/LUCENE-2341
Project: Lucene - Java
Issue Type: New Feature
Components: contrib/analyzers
Reporter
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848270#action_12848270
]
Dawid Weiss commented on LUCENE-2298:
-
The answer from the developer is: pick any lice
On Mon, Mar 22, 2010 at 2:20 PM, Ryan McKinley wrote:
> I'm confused... what is the need for a new name? The only place where
> there is a conflict is in the top level svn tree...
Agree, no need to re-brand.
> What about something general like:
> https://svn.apache.org/repos/asf/lucene/dev
> or
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848265#action_12848265
]
Robert Muir commented on LUCENE-2298:
-
bq. Is there any legal sense in this? Is this a
I am confused about the need for a new name. To the best of my knowledge, it
hasn't been decided that Lucene and Solr merge and become ONE thing ... but
rather that Lucene can still be released on its own (and thus considered a
project on its own) and that when Solr releases, so does Lucene. But So
I'm confused... what is the need for a new name? The only place where
there is a conflict is in the top level svn tree...
What about something general like:
https://svn.apache.org/repos/asf/lucene/dev
or
https://svn.apache.org/repos/asf/lucene/project
ryan
On Mon, Mar 22, 2010 at 2:02 PM, Stev
[
https://issues.apache.org/jira/browse/LUCENE-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Renaud Delbru updated LUCENE-2340:
--
Attachment: LUCENE-1458-FixedIntBlockIndexOutput.patch
A potential patch to the problem that I
FixedIntBlockIndexOutput encodes unnecessary integers at the end of a list
--
Key: LUCENE-2340
URL: https://issues.apache.org/jira/browse/LUCENE-2340
Project: Lucene - Java
Now that Solr and Lucene live in the same space, there has been an on-going
debate about what to call the merged entity.
The names being mulled at this point include (variously sized) snippets of both
Lucene's and Solr's names, and include LuSolr, Solcene, etc. (my current
personal favorites al
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848226#action_12848226
]
Michael Busch commented on LUCENE-2312:
---
I think sync'ing after every doc is probabl
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848212#action_12848212
]
Michael McCandless commented on LUCENE-2328:
Patch looks great -- what a sweet
I was thinking about that, but i dont know if it is the best option. Ty.
Michael McCandless-2 wrote:
>
> You can create your own Similarity implementation?
>
> Mike
>
> On Mon, Mar 22, 2010 at 12:32 PM, zsl wrote:
>>
>> Hi all!
>>
>> Im developing an aplication that uses Lucene and I´m tryin
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848210#action_12848210
]
Michael Busch edited comment on LUCENE-2312 at 3/22/10 5:01 PM:
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848210#action_12848210
]
Michael Busch commented on LUCENE-2312:
---
bq. So.. what does this mean for allowing a
On Mar 22, 2010, at 12:43 PM, Ryan McKinley wrote:
> Logistically, how would this work?
>
> would d...@lucene.apache.org be an alias for java-dev and solr-dev? or
> a whole new list?
I thought of d...@l.a.o, but we still have other dev lists under the PMC, so
didn't want to imply it was the on
On Thu, Mar 18, 2010 at 05:16:23AM -0500, Michael McCandless wrote:
> Also, will Lucy store the original stats?
These?
* Total number of tokens in the field.
* Number of unique terms in the field.
* Doc boost.
* Field boost.
That would depend on which Similiarity the user specs for
Logistically, how would this work?
would d...@lucene.apache.org be an alias for java-dev and solr-dev? or
a whole new list?
Would people need to subscribe to it, or would you already be on the
list if you were on java/solr dev? If we are on both lists, do we get
two copies of every message?
On
You can create your own Similarity implementation?
Mike
On Mon, Mar 22, 2010 at 12:32 PM, zsl wrote:
>
> Hi all!
>
> Im developing an aplication that uses Lucene and I´m trying to set the IDF
> manually before I do query.
> In other words ¿Is there a way to do a search query with an IDF value
>
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848201#action_12848201
]
Michael McCandless commented on LUCENE-2312:
So.. what does this mean for allo
Hi all!
Im developing an aplication that uses Lucene and I´m trying to set the IDF
manually before I do query.
In other words ¿Is there a way to do a search query with an IDF value
provided by me?
If it is, let me know.
Thank you in advance.
--
View this message in context:
http://old.nabbl
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848198#action_12848198
]
Michael Busch commented on LUCENE-2312:
---
Hi Brian - good to see you on this list!
I
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848197#action_12848197
]
Earwin Burrfoot commented on LUCENE-2339:
-
bq. NIO's transferTo, right?
I didn't r
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848196#action_12848196
]
Michael McCandless commented on LUCENE-2331:
OK, then I'll leave it.
Patch lo
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848192#action_12848192
]
Shai Erera commented on LUCENE-2331:
I think it's correct. The idea is to say that eve
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848189#action_12848189
]
Michael McCandless commented on LUCENE-2331:
In the jdocs for NoMergeScheduler
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848188#action_12848188
]
Jason Rutherglen commented on LUCENE-2312:
--
Brian, thanks for the explanation!
>
[
https://issues.apache.org/jira/browse/LUCENE-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848186#action_12848186
]
Michael McCandless commented on LUCENE-2334:
bq. With the current implementati
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848183#action_12848183
]
Brian Goetz commented on LUCENE-2312:
-
@JasonR: There is a good reason there is no Ato
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-2329:
--
Attachment: lucene-2329.patch
Removed reset(). All tests still pass.
> Use parallel arrays i
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848180#action_12848180
]
Michael McCandless commented on LUCENE-2339:
bq. I wonder if we could convert
wait, wait... no...
solr-and-some-java-apis-...@lucene.apache.org
-Yonik
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
+1
Michael
On Mar 22, 2010, at 8:55 AM, Michael McCandless > wrote:
+1
Mike
On Mon, Mar 22, 2010 at 11:53 AM, Ryan McKinley
wrote:
why not just "d...@lucene.apache.org"?
On Mon, Mar 22, 2010 at 11:44 AM, Grant Ingersoll > wrote:
Shall we merge the dev mailing lists? This should red
+1
Mike
On Mon, Mar 22, 2010 at 11:53 AM, Ryan McKinley wrote:
> why not just "d...@lucene.apache.org"?
>
>
>
> On Mon, 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
why not just "d...@lucene.apache.org"?
On Mon, 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 pl
+1, let's do this now.
Mike
On Mon, 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 plan to merge
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2331:
---
Attachment: LUCENE-2331.patch
Patch includes NoMergePolicy.NO_COMPOUND_FILES and COMPOUND_FILES sing
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 plan to merge dev efforts.
I'd propose it be called lucene-solr-...@l.a.o. I can put in an issue for
infr
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848161#action_12848161
]
Michael Busch commented on LUCENE-2329:
---
bq. I think *ParallelPostingsArray.reset do
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848159#action_12848159
]
Michael McCandless commented on LUCENE-2328:
BTW on the sync of still-open fil
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848158#action_12848158
]
Michael McCandless commented on LUCENE-2331:
bq. You ask because of the useCom
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848139#action_12848139
]
Dawid Weiss commented on LUCENE-2298:
-
I agree about classpath issues, they're a pain
[
https://issues.apache.org/jira/browse/LUCENE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ritesh Nigam updated LUCENE-2280:
-
Attachment: LuceneUtils.zip
Sample application which replicates the actual application.
> Index
[
https://issues.apache.org/jira/browse/LUCENE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848135#action_12848135
]
Ritesh Nigam commented on LUCENE-2280:
--
Thanks michael, the fix you provided seems to
[
https://issues.apache.org/jira/browse/LUCENE-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848122#action_12848122
]
Mike Hanafey commented on LUCENE-2334:
--
The problem is IndexReader implements the Clo
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848120#action_12848120
]
Robert Muir commented on LUCENE-2298:
-
bq. The problem with Morfologik is that its dic
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848114#action_12848114
]
Earwin Burrfoot commented on LUCENE-2339:
-
I wonder if we could convert these meth
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848113#action_12848113
]
Shai Erera commented on LUCENE-2331:
bq. do you think we should allow instantiation of
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2331:
---
Attachment: LUCENE-2331.patch
Sorry - new eclipse and project settings :). Should be ok now.
> Add
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848109#action_12848109
]
Michael McCandless commented on LUCENE-2339:
Patch looks good Earwin -- simple
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-2328:
--
Assignee: Michael McCandless
> IndexWriter.synced field accumulates data lead
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-2339:
--
Assignee: Michael McCandless
> Allow Directory.copy() to accept a collection o
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848103#action_12848103
]
Robert Muir commented on LUCENE-2298:
-
bq. Staszek suggested that perhaps it would be
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848102#action_12848102
]
Earwin Burrfoot commented on LUCENE-2328:
-
Ah, patch is based off LUCENE-2339. If
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2328:
Attachment: LUCENE-2328.patch
Okay, dirty patch go!
I threw in FSyncStrategy, so we choos
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 to put the main development and how to switch, so non-devel
I think that would be ideal because right now it is somewhat confusing
on where to pull your latest-and-greatest from and what should you
base your patches on.
On Mon, Mar 22, 2010 at 14:21, Chris Male wrote:
> I think that would be ideal because we can then start getting some nightly
> builds us
I think that would be ideal because we can then start getting some nightly
builds using (new)trunk as well.
On Mon, Mar 22, 2010 at 12:13 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> Right, I think it's ready to be 'the trunk'... I'm now doing all my
> work on it. When a take an
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848085#action_12848085
]
Michael McCandless commented on LUCENE-2329:
Looks great Michael!
I think *Pa
Right, I think it's ready to be 'the trunk'... I'm now doing all my
work on it. When a take an issue, I apply the patch there, and run
all tests there, etc. I don't use "old trunk" alone anymore.
I agree, at some point soon we should rename it in svn so things are
less confusing :) Ie, trunk ->
Hi,
If we are developing on newtrunk and merging to the old trunk, what issues
are preventing it from becoming 'the trunk'? or was that what you were
suggesting?
Cheers
Chris
On Mon, Mar 22, 2010 at 11:37 AM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> I think we should.
>
> It (ne
I think we should.
It (newtrunk) was created to test Hoss's side-by-sdie proposal, and
that approach looks to be working very well.
Up until now we've been committing to the old trunk and then
systematically merging over to newtrunk. I think we should now flip
that, ie, commit to newtrunk and on
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-2331:
--
Assignee: Michael McCandless
> Add NoOpMergePolicy
> ---
>
>
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848080#action_12848080
]
Michael McCandless commented on LUCENE-2331:
Patch looks good Shai!
But, can
Are we now only working on newtrunk?
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Michael McCandless (JIRA) [mailto:j...@apache.org]
> Sent: Monday, March 22, 2010 11:22 AM
> To: java-dev@lucene.apache
[
https://issues.apache.org/jira/browse/LUCENE-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2297.
Resolution: Fixed
Fixed on newtrunk.
> IndexWriter should let you optionally enab
[
https://issues.apache.org/jira/browse/LUCENE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848076#action_12848076
]
Yuval Feinstein commented on LUCENE-2091:
-
Hi Katja.
I am adding this to my task l
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-2329:
--
Attachment: lucene-2329.patch
Made the memory tracking changes as described in my previous com
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848058#action_12848058
]
Michael Busch commented on LUCENE-2329:
---
One change I should make to the patch is ho
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848054#action_12848054
]
Dawid Weiss commented on LUCENE-2298:
-
Staszek suggested that perhaps it would be conv
[
https://issues.apache.org/jira/browse/LUCENE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-2329:
--
Attachment: lucene-2329.patch
Changes the indexer to use parallel arrays instead of PostingLis
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2339:
Attachment: LUCENE-2339.patch
A simple patch
> Allow Directory.copy() to accept a collect
1 - 100 of 101 matches
Mail list logo
