[
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=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=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=12848973#action_12848973
]
Earwin Burrfoot commented on LUCENE-2328:
-
Mike, you missed latest patch
Issue Type: Improvement
Reporter: Earwin Burrfoot
Par example, I want to copy files pertaining to a certain commit, and not
everything there is in a Directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online
[
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
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 gento...@gmail.com wrote:
I think that would be ideal because we can then start getting some
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848102#action_12848102
]
Earwin Burrfoot commented on LUCENE-2328:
-
Ah, patch is based off LUCENE-2339
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848114#action_12848114
]
Earwin Burrfoot commented on LUCENE-2339:
-
I wonder if we could convert
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848197#action_12848197
]
Earwin Burrfoot commented on LUCENE-2339:
-
bq. NIO's transferTo, right?
I didn't
[
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
[
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
[
https://issues.apache.org/jira/browse/LUCENE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848331#action_12848331
]
Earwin Burrfoot commented on LUCENE-2339:
-
bq. Google says that with certain
[
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
[
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
[
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
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848427#action_12848427
]
Earwin Burrfoot commented on LUCENE-2328:
-
I do not touch *IndexInput
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847512#action_12847512
]
Earwin Burrfoot commented on LUCENE-2328:
-
I'll either jdoc this, or move
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847515#action_12847515
]
Earwin Burrfoot commented on LUCENE-2328:
-
Thus, I think we should officially
[
https://issues.apache.org/jira/browse/LUCENE-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847516#action_12847516
]
Earwin Burrfoot commented on LUCENE-2334:
-
I wholeheartedly agree this API
Unless maven has some features i'm not aware of, your nicely depends
works buy pulling Lucene jars from a repository
The 'missing feature' is called multi-module projects.
On Thu, Mar 18, 2010 at 03:33, Chris Hostetter hossman_luc...@fucit.org wrote:
: build and nicely gets all dependencies to
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846835#action_12846835
]
Earwin Burrfoot commented on LUCENE-2328:
-
A shot in the sky (didn't delve deep
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846880#action_12846880
]
Earwin Burrfoot commented on LUCENE-2328:
-
EG running merges (or any still-open
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846899#action_12846899
]
Earwin Burrfoot commented on LUCENE-2328:
-
I'm proposing something even more dead
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846902#action_12846902
]
Earwin Burrfoot commented on LUCENE-2328:
-
Btw, initial problem stems from
[
https://issues.apache.org/jira/browse/LUCENE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846903#action_12846903
]
Earwin Burrfoot commented on LUCENE-2330:
-
Please, only open up something if you
[
https://issues.apache.org/jira/browse/LUCENE-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846926#action_12846926
]
Earwin Burrfoot commented on LUCENE-2331:
-
NoMergesPolicy - that's exactly what
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846938#action_12846938
]
Earwin Burrfoot commented on LUCENE-2328:
-
How would IndexInput report back
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846956#action_12846956
]
Earwin Burrfoot commented on LUCENE-2328:
-
Keeping track of not-yet-sync'd files
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846991#action_12846991
]
Earwin Burrfoot commented on LUCENE-2328:
-
Okay, summing up.
1. Directory gets
[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847010#action_12847010
]
Earwin Burrfoot commented on LUCENE-2328:
-
Every Directory implementation decides
Some of these people got traumatized by maven, now they only can think
in terms of mash everything together and sprinkle with
hand-downloaded dependency jars.
No offence : )
I, personally, prefer side-by-side layouts. You can add new stuff, and
wire dependencies to the old one, without
[
https://issues.apache.org/jira/browse/LUCENE-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845530#action_12845530
]
Earwin Burrfoot commented on LUCENE-2320:
-
We could split MergePolicy in two
[
https://issues.apache.org/jira/browse/LUCENE-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845167#action_12845167
]
Earwin Burrfoot commented on LUCENE-2320:
-
Or, maybe, we should think
[
https://issues.apache.org/jira/browse/LUCENE-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844931#action_12844931
]
Earwin Burrfoot commented on LUCENE-2310:
-
These settings will go to FieldType
[
https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844690#action_12844690
]
Earwin Burrfoot commented on LUCENE-2308:
-
I'm strongly against names like
[
https://issues.apache.org/jira/browse/LUCENE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844130#action_12844130
]
Earwin Burrfoot commented on LUCENE-2000:
-
I believe we should do this at our next
[
https://issues.apache.org/jira/browse/LUCENE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844250#action_12844250
]
Earwin Burrfoot commented on LUCENE-2311:
-
Not only newly created, but newly
: MacOS X, Java 6
Reporter: Earwin Burrfoot
Happened on trunk:
[junit] Testsuite: org.apache.lucene.index.TestIndexWriter
[junit] Tests run: 106, Failures: 1, Errors: 0, Time elapsed: 18.567 sec
[junit]
[junit] - Standard Output ---
[junit
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841193#action_12841193
]
Earwin Burrfoot commented on LUCENE-2293:
-
bq. I wonder if that won't complicate
[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841574#action_12841574
]
Earwin Burrfoot commented on LUCENE-2294:
-
I voted for killing these delegating
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12840949#action_12840949
]
Earwin Burrfoot commented on LUCENE-2293:
-
bq. The IndexWriter (or a new class
but even non-final methods are inlined by hotspot, if the compiler is sure
that the class was not extended
There's absolutely no way a JIT compiler can be sure that the class
was not extended (except declaring it final) - because you can create
a new classloader and load new class any time you
I'm thinking, should Lucene introduce new interface to read stored
document fields?
Current 'Document document(int n)' mechanism is barely usable due to
overhead involved. While I believe underlying index structure works
pretty fast (if it fits in memory, as is the case for most
you actually want all the fields.
Erick
On Thu, Feb 25, 2010 at 7:52 AM, Earwin Burrfoot ear...@gmail.com wrote:
I'm thinking, should Lucene introduce new interface to read stored
document fields?
Current 'Document document(int n)' mechanism is barely usable due to
overhead involved
(didn't see any interest from anyone though)
-- Tim
Erick Erickson wrote:
OK, never mind G
Erick
On Thu, Feb 25, 2010 at 1:48 PM, Earwin Burrfoot ear...@gmail.com wrote:
My issue is with extra objects created in the process. Field selection
can be handled with, well, FieldSelector.
2010
256 here (MBP)
On Tue, Jan 12, 2010 at 17:49, Grant Ingersoll gsing...@apache.org wrote:
On Jan 11, 2010, at 4:25 PM, Marvin Humphrey wrote:
On Mon, Jan 11, 2010 at 03:20:17PM -0500, Grant Ingersoll wrote:
Should we really still be defaulting to true for setUseCompoundFile? Do
people still
[
https://issues.apache.org/jira/browse/LUCENE-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792637#action_12792637
]
Earwin Burrfoot commented on LUCENE-2171:
-
(without looking deep) I have a feeling
[
https://issues.apache.org/jira/browse/LUCENE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790663#action_12790663
]
Earwin Burrfoot commented on LUCENE-2161:
-
Remove volatile from numDocs? All
[
https://issues.apache.org/jira/browse/LUCENE-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790314#action_12790314
]
Earwin Burrfoot commented on LUCENE-2156:
-
Did I miss you exploiting 'atomicity
[
https://issues.apache.org/jira/browse/LUCENE-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790354#action_12790354
]
Earwin Burrfoot commented on LUCENE-2156:
-
bq. ensureOpen is only on a best effort
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790586#action_12790586
]
Earwin Burrfoot commented on LUCENE-2089:
-
bq. I would like to know how the paper
[
https://issues.apache.org/jira/browse/LUCENE-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789377#action_12789377
]
Earwin Burrfoot commented on LUCENE-2133:
-
bq. I would like to hear the opionions
[
https://issues.apache.org/jira/browse/LUCENE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789473#action_12789473
]
Earwin Burrfoot commented on LUCENE-2026:
-
If I understand everything right
[
https://issues.apache.org/jira/browse/LUCENE-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789474#action_12789474
]
Earwin Burrfoot commented on LUCENE-2142:
-
+1
FieldCache.getStringIndex should
[
https://issues.apache.org/jira/browse/LUCENE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789604#action_12789604
]
Earwin Burrfoot commented on LUCENE-2026:
-
bq. Until you need to spillover to disk
[
https://issues.apache.org/jira/browse/LUCENE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789604#action_12789604
]
Earwin Burrfoot edited comment on LUCENE-2026 at 12/11/09 11:19 PM
[
https://issues.apache.org/jira/browse/LUCENE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788838#action_12788838
]
Earwin Burrfoot commented on LUCENE-2026:
-
We need an ability to see segment write
[
https://issues.apache.org/jira/browse/LUCENE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788840#action_12788840
]
Earwin Burrfoot commented on LUCENE-2026:
-
Oh, forgive me if I just said something
[
https://issues.apache.org/jira/browse/LUCENE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787505#action_12787505
]
Earwin Burrfoot commented on LUCENE-2135:
-
A better approach is to don IR-keyed
[
https://issues.apache.org/jira/browse/LUCENE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787552#action_12787552
]
Earwin Burrfoot commented on LUCENE-2135:
-
bq. I'd love to see a MapObject,Object
[
https://issues.apache.org/jira/browse/LUCENE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787585#action_12787585
]
Earwin Burrfoot commented on LUCENE-2135:
-
bq. Please see LUCENE-2133
[
https://issues.apache.org/jira/browse/LUCENE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787589#action_12787589
]
Earwin Burrfoot commented on LUCENE-1377:
-
Hehehe. There is an upside for Lucene
[
https://issues.apache.org/jira/browse/LUCENE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787696#action_12787696
]
Earwin Burrfoot commented on LUCENE-2135:
-
bq. To provide arbitrary cacheable
Replace SegmentReader.Ref with AtomicInteger
Key: LUCENE-2137
URL: https://issues.apache.org/jira/browse/LUCENE-2137
Project: Lucene - Java
Issue Type: Improvement
Reporter: Earwin
[
https://issues.apache.org/jira/browse/LUCENE-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2137:
Description: I think the patch should be applied to backcompat tag in its
entirety
[
https://issues.apache.org/jira/browse/LUCENE-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2137:
Attachment: LUCENE-2137.patch
Replace SegmentReader.Ref with AtomicInteger
On Sun, Dec 6, 2009 at 02:01, Grant Ingersoll gsing...@apache.org wrote:
On Dec 5, 2009, at 10:47 PM, Earwin Burrfoot wrote:
If someone needs all results, they know it beforehand. Why can't they
write this collector themselves? It's trivial, just like you said.
I'm not following your
If someone needs all results, they know it beforehand. Why can't they
write this collector themselves? It's trivial, just like you said.
On Sun, Dec 6, 2009 at 01:22, Grant Ingersoll gsing...@apache.org wrote:
At ScaleCamp yesterday in the UK, I was listening to a talk on Xapian and the
[
https://issues.apache.org/jira/browse/LUCENE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781122#action_12781122
]
Earwin Burrfoot commented on LUCENE-2088:
-
bq. Attribute.class.isAssignableFrom
[
https://issues.apache.org/jira/browse/LUCENE-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12779510#action_12779510
]
Earwin Burrfoot commented on LUCENE-1799:
-
Earwin, if implemented as a directory
[
https://issues.apache.org/jira/browse/LUCENE-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12779512#action_12779512
]
Earwin Burrfoot commented on LUCENE-2075:
-
Well, that's just hosted
[
https://issues.apache.org/jira/browse/LUCENE-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12779602#action_12779602
]
Earwin Burrfoot commented on LUCENE-1799:
-
bq. as far as the encoding itself, BOCU
[
https://issues.apache.org/jira/browse/LUCENE-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12779682#action_12779682
]
Earwin Burrfoot commented on LUCENE-1799:
-
bq. but then i guess we have to deal
This algo is strictly tied to sort-by-score, if I understand it correctly.
Lucene has queries and sorting decoupled (except for allowOutOfOrder
mess), so implementing it would require some really fat hacks.
On Mon, Nov 16, 2009 at 20:26, J. Delgado joaquin.delg...@gmail.com wrote:
As I
[
https://issues.apache.org/jira/browse/LUCENE-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12778675#action_12778675
]
Earwin Burrfoot commented on LUCENE-2075:
-
There's no such thing in Google
Terracotta guys easy-clustered Lucene a few years ago. I'm yet to
see at least one person saying it worked for him allright.
This new directory ain't gonna be faster than RAMDirectory, as syncs
on a map doesn't matter, they are taken once per opened file - once
per reopen, which is not happening
About the RAMDirectory comparison, as you said yourself the bytes
aren't read constantly but just at index reopen so I wouldn't be too
worried about the bunch of methods as they're executed once per
segment loading;
The bytes /are/ read constantly (readByte() method). I believe that is
the
[
https://issues.apache.org/jira/browse/LUCENE-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12776703#action_12776703
]
Earwin Burrfoot commented on LUCENE-1990:
-
bq. hope I am reinventing bycycle
I
[
https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12773000#action_12773000
]
Earwin Burrfoot commented on LUCENE-1997:
-
bq. though they'd have preferred
[
https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772773#action_12772773
]
Earwin Burrfoot commented on LUCENE-1997:
-
Regarding memory - If I'm
[
https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772779#action_12772779
]
Earwin Burrfoot commented on LUCENE-1997:
-
Right now DocComparator cheats
[
https://issues.apache.org/jira/browse/LUCENE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772246#action_12772246
]
Earwin Burrfoot commented on LUCENE-2019:
-
bq. if you disagree with this patch
[
https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771324#action_12771324
]
Earwin Burrfoot commented on LUCENE-1997:
-
bq. One thing that bothers me about
[
https://issues.apache.org/jira/browse/LUCENE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770812#action_12770812
]
Earwin Burrfoot commented on LUCENE-2012:
-
That's why you need @override in first
It's okay in a sense.
See, svn's merge-tracking support was grafted onto it in a particulary
hideous way and is really hairy on the insides.
So while there's no sane explanation for that behaviour, it is expected.
See -
There are some advanced things that are plain impossible with stock new API.
Like having more than one HitQueue in your Collector, and stashing
overflowing values from one of them into another. Once you cross the
segment border - BOOM!
Otherwise it may look intimidating, but is pretty simple in
That's quite possible to reimplement, I believe. You can have your
docid-ordinal map bound to toplevel reader, as it was before and then
your FIeldComparator rebases incoming compare() docids based on what
last setNextReader() was called with.
On Wed, Oct 21, 2009 at 02:07, TomS
[
https://issues.apache.org/jira/browse/LUCENE-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12767165#action_12767165
]
Earwin Burrfoot commented on LUCENE-1945:
-
Package-private classes might as well
Always used 1.
That's also the default for many autoformatters, which probably
explains why people use it.
On Sat, Oct 17, 2009 at 14:55, Uwe Schindler u...@thetaphi.de wrote:
Just because I came along a lot of new Generics declarations:
How should we handle generics parameters in the source
[
https://issues.apache.org/jira/browse/LUCENE-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762993#action_12762993
]
Earwin Burrfoot commented on LUCENE-1856:
-
Still some javadocs referencing Hits
[
https://issues.apache.org/jira/browse/LUCENE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12763083#action_12763083
]
Earwin Burrfoot commented on LUCENE-1257:
-
Not sure if that's the right issue
[
https://issues.apache.org/jira/browse/LUCENE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12763087#action_12763087
]
Earwin Burrfoot commented on LUCENE-1257:
-
Also, we can remove tons of boxing
I intend to fire up IDEA, run java5-specific code inspections and fix
whatever it finds, something automatically (with manual review
afterwards), something by hand.
1. Replace for/while loops that go through arrays/lists by index, or
through collections by iterators with for-each loops.
This just
Might still be lucene-ish issue.
We already have getSequentialSubReaders() on IR, in my patched version
I augmented this with public readerIndex(), and getSubReaderStarts().
Pretty much impossible to do some postprocessing on gathered hits
without at least one of these.
On Tue, Oct 6, 2009 at
On Mon, Oct 5, 2009 at 12:01, Uwe Schindler u...@thetaphi.de wrote:
Hi Marvin,
Property names are always String, values any type (therefore
MapString,?).
With Java 5, integer props and so on are no bad syntax problem because
of
autoboxing (no need to pass new Integer() or
I think AS is overkill for conveying configuration of IW/IR?
Agree.
It's too cumbersome, I think, for something that ought to be simple.
I'd prefer a dedicated config class with strongly typed setters
exposed. Of all the pure syntax options so far I'd still prefer the
traditional config
As I stated in my last email, there's zero difference between
settings+static factory and builder except for syntax. Cannot
understand what Mark, Mike are arguing about.
Right now I offer to do two things, in any possible way - eradicate as
much broken/spahetti-like runtime state change from IW
Builder pattern allows you to switch concrete implementations as you
please, taking parameters into account or not.
We could also achieve this w/ static factory method. EG
IndexReader.open(IndexReader.Config) could switch between concrete
impls (it already does today).
Yes, the choice of
It is also probably a good idea to move various settings methods from
IW to that builder and have IW immutable in regards to configuration.
I'm speaking of the likes of setWriteLockTimeout, setRAMBufferSizeMB,
setMergePolicy, setMergeScheduler, setSimilarity.
IndexWriter.Builder iwb =
301 - 400 of 652 matches
Mail list logo
