On Wed, Apr 14, 2010 at 5:22 PM, Michael McCandless
wrote:
> * There is no back compat across major releases (index nor APIs),
> but full back compat within branches.
>
> This would match how many other projects work (KS/Lucy, as Marvin
> describes above; Apache Tomcat; Hibernate; log4J; FreeB
On Thu, Apr 15, 2010 at 9:39 AM, Earwin Burrfoot wrote:
> On Thu, Apr 15, 2010 at 17:17, Yonik Seeley
> wrote:
>> Seamless online upgrades have their place too... say you are upgrading
>> one server at a time in a cluster.
>
> Nothing here that can't be solved w
Seamless online upgrades have their place too... say you are upgrading
one server at a time in a cluster.
-Yonik
Apache Lucene Eurocon 2010
18-21 May 2010 | Prague
On Thu, Apr 15, 2010 at 8:42 AM, Earwin Burrfoot wrote:
> I like the idea of index conversion tool over silent online upgrade
> beca
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857006#action_12857006
]
Yonik Seeley commented on LUCENE-2359:
--
Perhaps I'm misreading the tabl
[
https://issues.apache.org/jira/browse/LUCENE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856984#action_12856984
]
Yonik Seeley commented on LUCENE-2359:
--
Hi Nicolas, I like the idea of reducing
On Wed, Apr 14, 2010 at 12:12 PM, Chris Male wrote:
> On Wed, Apr 14, 2010 at 6:07 PM, Grant Ingersoll
>> On Apr 14, 2010, at 11:06 AM, Chris Male wrote:
>> > For those doing just Cartesian Tier filtering it seems like the new
>> > approach is a win, but for those doing distance calculations on t
On Wed, Apr 14, 2010 at 11:06 AM, Chris Male wrote:
> While having fewer boxes means fewer term queries to make against the index,
> more documents means more costly calculations to filter out those extraneous
> documents.
Filtering out documents (greater selectivity) seems like it should be
the
On Wed, Apr 14, 2010 at 10:39 AM, DM Smith wrote:
> Maybe have the index store the version(s) and use that when constructing a
> reader or writer?
That would cause a reindex to change behavior (among other problems).
-Yonik
Apache Lucene Eurocon 2010
18-21 May 2010 | Prague
[
https://issues.apache.org/jira/browse/LUCENE-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855752#action_12855752
]
Yonik Seeley commented on LUCENE-2386:
--
I think Solr's spellchecker should
[
https://issues.apache.org/jira/browse/LUCENE-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854621#action_12854621
]
Yonik Seeley commented on LUCENE-2380:
--
bq. We could also do shared byte[] bl
On Wed, Mar 31, 2010 at 9:06 AM, wrote:
> JIRA-2353: Config incorrectly handles Windows absolute pathnames
The JIRA-2353 part is my fault - Shai asked me the right format for
JIRA linking, and I got it wrong!
Should be LUCENE-2353 of course. need...more...coffee...
-Yonik
On Tue, Mar 23, 2010 at 5:07 PM, Michael Busch 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 ok to commit
On Tue, Mar 23, 2010 at 10:49 AM, Grant Ingersoll 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. Not sure w
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" chec
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 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 a luso
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
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
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
[
https://issues.apache.org/jira/browse/LUCENE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847647#action_12847647
]
Yonik Seeley commented on LUCENE-2335:
--
This is also useful for MultiReader
E, let's strive for slightly better commit messages ;-)
-Yonik
On Thu, Mar 18, 2010 at 7:48 AM, wrote:
> Author: uschindler
> Date: Thu Mar 18 11:48:11 2010
> New Revision: 924731
>
> URL: http://svn.apache.org/viewvc?rev=924731&view=rev
> Log:
> LUCENE-2326: As rmuir seems to bug me about t
On Tue, Mar 16, 2010 at 6:01 PM, Jake Mannix wrote:
> I'm not concerned with casual downloaders. I'm talking about the companies
> and people who
> may or may not be interested in making multi-million dollar decisions
> regarding using or
> not using Lucene or Solr.
Heh - multi-million dollar de
On Tue, Mar 16, 2010 at 5:42 PM, Jake Mannix wrote:
> On Tue, Mar 16, 2010 at 2:31 PM, Michael McCandless
> wrote:
>>
>> If we move lucene under Solr's existing svn path, ie:
>>
>> /solr/trunk/lucene
>
> Chiming in just a bit here - isn't there any concern that independent of
> whether or not pe
IRC has been discussed to death at Apache:
http://markmail.org/search/?q=IRC+list%3Aorg.apache.incubator.general
Look for the spikes... like this:
http://markmail.org/search/?q=IRC+list%3Aorg.apache.incubator.general#query:IRC%20list%3Aorg.apache.incubator.general%20date%3A200608%20+page:1+state:
On Tue, Mar 16, 2010 at 5:42 AM, Michael McCandless
wrote:
> I think it like the 1st option best (lucene moves as subdir to solr's
> current trunk SVN path), but I don't feel strongly.
>
> This'd mean one could simply checkout lucene alone and do everything
> you can do today.
>
> But if you check
On Tue, Mar 16, 2010 at 2:51 AM, Michael Busch wrote:
> Also, we're in review-and-commit process, not commit-and-review. Changes
> have to be
> proposed, discussed and ideally attached to jira as patches first.
Correction, just for the sake of avoiding future confusion (i.e. I'm
not making any
Due to a tremendous amount of work by our newly merged committer
corps, the get-on-lucene-trunk branch (branches/solr) is ready for
prime-time as the new solr trunk! Lucene and Solr need to move to a
common trunk for a host of reasons, including single patches that can
cover both, shared tags and
On Sun, Mar 14, 2010 at 5:47 PM, Mark Miller wrote:
> On 03/14/2010 06:37 PM, Grant Ingersoll wrote:
>>
>> On Mar 14, 2010, at 2:03 PM, Uwe Schindler wrote:
>>
>>
>>>
>>> This time a +1 without discuss :-)
>>>
>>
>> Yeah, but Uwe, the thread was DISCUSS, not VOTE! :-)
>>
>
> I had a whole spiel a
I've merged JIRA permissions - let me know if I accidentally left anyone out.
Looking forward to the communities working more closely again!
(go Robert, go! ;-)
-Yonik
On Sun, Mar 14, 2010 at 10:44 AM, Grant Ingersoll wrote:
> Per the vote on general@ to merge committers, I've given Lucene and
[
https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844722#action_12844722
]
Yonik Seeley commented on LUCENE-2308:
--
Of course... given that Fieldable i
[
https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844716#action_12844716
]
Yonik Seeley commented on LUCENE-2308:
--
bq. I'm really unsure about this
[
https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844707#action_12844707
]
Yonik Seeley commented on LUCENE-2308:
--
I'm not sure if strict immuta
[
https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844700#action_12844700
]
Yonik Seeley commented on LUCENE-2308:
--
For the non-expert user, it's jus
[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841595#action_12841595
]
Yonik Seeley commented on LUCENE-2294:
--
Yay, we'll be able to remove SolrIn
On Fri, Feb 26, 2010 at 3:31 PM, Jason Rutherglen
wrote:
>> I've never tried to learn a command-line invocation of a test
>> case for a single test method, I've always just used the IDE
>> to run individual methods
>
> Right, I've been doing bunches of Solr dev which for me only works
> from t
[
https://issues.apache.org/jira/browse/LUCENE-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836180#action_12836180
]
Yonik Seeley commented on LUCENE-2271:
--
bq. maybe we should keep it as is then,
[
https://issues.apache.org/jira/browse/LUCENE-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836178#action_12836178
]
Yonik Seeley commented on LUCENE-2271:
--
I'm starting to think that handli
[
https://issues.apache.org/jira/browse/LUCENE-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835762#action_12835762
]
Yonik Seeley commented on LUCENE-2271:
--
bq. A design bug that function queries s
[
https://issues.apache.org/jira/browse/LUCENE-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835750#action_12835750
]
Yonik Seeley commented on LUCENE-2271:
--
bq. its not a bug, as its doc'e
[
https://issues.apache.org/jira/browse/LUCENE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved LUCENE-2270.
--
Resolution: Fixed
committed to trunk and branches 2.9, 3.0
> queries with zero boosts do
[
https://issues.apache.org/jira/browse/LUCENE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835360#action_12835360
]
Yonik Seeley commented on LUCENE-2270:
--
OK, I'll commit this shortly to a
[
https://issues.apache.org/jira/browse/LUCENE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835297#action_12835297
]
Yonik Seeley commented on LUCENE-2270:
--
Another thing to note is that this p
[
https://issues.apache.org/jira/browse/LUCENE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-2270:
-
Attachment: LUCENE-2270.patch
Attached patch that "normalizes" the query norm in Qu
[
https://issues.apache.org/jira/browse/LUCENE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835203#action_12835203
]
Yonik Seeley commented on LUCENE-2270:
--
The problem is twofold: a query with
queries with zero boosts don't work
---
Key: LUCENE-2270
URL: https://issues.apache.org/jira/browse/LUCENE-2270
Project: Lucene - Java
Issue Type: Bug
Affects Versions: 2.9
Reporter:
[
https://issues.apache.org/jira/browse/LUCENE-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-1452:
-
Comment: was deleted
(was: [buy cheap tramadol|http://ptl.sys.virginia.edu/@api/deki/files/257
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833493#action_12833493
]
Yonik Seeley commented on LUCENE-2262:
--
bq. yonik, that's not what this
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833481#action_12833481
]
Yonik Seeley commented on LUCENE-2262:
--
It doesn't seem like this type of b
On Fri, Feb 12, 2010 at 1:50 AM, Shay Banon wrote:
> On Thu, Feb 11, 2010 at 5:41 PM, Yonik Seeley
>> It really shouldn't be heavily used.
>> For a sorted search, get() is called once per segment in the index.
>> There is no synchronization to retrieve per-document valu
On Thu, Feb 11, 2010 at 9:54 AM, Shay Banon wrote:
> I would like to try and improve concurrency in Lucene in several places,
> and thought I would start with FieldCacheImpl. The implementation is heavily
> synchronized on both a global map and on creation values for a pretty
> heavily used pat
[
https://issues.apache.org/jira/browse/LUCENE-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830603#action_12830603
]
Yonik Seeley commented on LUCENE-2252:
--
The thing about stored fields is that
[
https://issues.apache.org/jira/browse/LUCENE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828633#action_12828633
]
Yonik Seeley commented on LUCENE-2232:
--
A branch mispredict can be more co
[
https://issues.apache.org/jira/browse/LUCENE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828218#action_12828218
]
Yonik Seeley commented on LUCENE-2232:
--
bq. Has it been tried to unroll get
On Thu, Jan 28, 2010 at 3:49 PM, Grant Ingersoll wrote:
> Could we get the Channel (and other necessary classes) implementation from
> Apache Harmony
Public JDK methods don't have the low level stuff to implement our
own, so rolling our own or using Harmony would require native code...
not a goo
On Thu, Jan 28, 2010 at 8:24 AM, Michael McCandless
wrote:
> Bummer.
>
> So the only viable workarounds are 1) don't use Thread.interrupt (nor,
> things like Future.cancel, which in turn use Thread.interrupt) with
> NIOFSDir, or 2) we fix NIOFSDir to reopen the channel AND the app must
> make a de
[
https://issues.apache.org/jira/browse/LUCENE-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802972#action_12802972
]
Yonik Seeley commented on LUCENE-2221:
--
bq. Results from Intel I7 - an improve
On Wed, Jan 20, 2010 at 11:21 AM, Dawid Weiss wrote:
> Is there anyone with access to an Intel I7-machine? I'd be curious
> what the results of this benchmark are, given the new JVM intrinsics
> introduced in HotSpot 1.7:
FYI, the AMD Phenom also has the POPCNT instruction.
-Yonik
http://www.luc
[
https://issues.apache.org/jira/browse/LUCENE-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802887#action_12802887
]
Yonik Seeley edited comment on LUCENE-2221 at 1/20/10 4:3
[
https://issues.apache.org/jira/browse/LUCENE-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802887#action_12802887
]
Yonik Seeley commented on LUCENE-2221:
--
If you only tested 32 bit on the P4,
[
https://issues.apache.org/jira/browse/LUCENE-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802885#action_12802885
]
Yonik Seeley commented on LUCENE-1990:
--
bq. In the aligned case, and with the r
[
https://issues.apache.org/jira/browse/LUCENE-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802854#action_12802854
]
Yonik Seeley commented on LUCENE-1990:
--
bq. Using aligned ints would save
[
https://issues.apache.org/jira/browse/LUCENE-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801880#action_12801880
]
Yonik Seeley commented on LUCENE-2221:
--
Ah yeah, missed that.
In fact it appear
[
https://issues.apache.org/jira/browse/LUCENE-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801856#action_12801856
]
Yonik Seeley commented on LUCENE-2221:
--
bq. I'm sure Yonik has implemented
[
https://issues.apache.org/jira/browse/LUCENE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801457#action_12801457
]
Yonik Seeley commented on LUCENE-2198:
--
bq. Only in the case that having mult
[
https://issues.apache.org/jira/browse/LUCENE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801442#action_12801442
]
Yonik Seeley commented on LUCENE-2198:
--
bq. If we start to discuss about such to
[
https://issues.apache.org/jira/browse/LUCENE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801437#action_12801437
]
Yonik Seeley commented on LUCENE-2198:
--
One random thought is to wonder how
[
https://issues.apache.org/jira/browse/LUCENE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801429#action_12801429
]
Yonik Seeley commented on LUCENE-2213:
--
bq. The thing is, if we blindly add
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved LUCENE-2216.
--
Resolution: Fixed
Fix Version/s: 3.1
Committed in trunk. Thanks for bringing this up
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801275#action_12801275
]
Yonik Seeley commented on LUCENE-2216:
--
Microbenchmarks will always be misleadin
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801270#action_12801270
]
Yonik Seeley commented on LUCENE-2216:
--
bq. For what it's worth, I ch
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801266#action_12801266
]
Yonik Seeley commented on LUCENE-2216:
--
bq. my argument is that ideally it shoul
[
https://issues.apache.org/jira/browse/LUCENE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801261#action_12801261
]
Yonik Seeley commented on LUCENE-2213:
--
Instead of masking with 7fff... you can
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801249#action_12801249
]
Yonik Seeley edited comment on LUCENE-2216 at 1/16/10 6:3
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801249#action_12801249
]
Yonik Seeley commented on LUCENE-2216:
--
bq. I agree that having hashCode mutate
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801235#action_12801235
]
Yonik Seeley commented on LUCENE-2216:
--
bq. This is only true if there is hap
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801200#action_12801200
]
Yonik Seeley commented on LUCENE-2216:
--
bq. To me this implementation cannot be
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-2216:
-
Attachment: LUCENE-2216.patch
I haven't tested this patch, but this seems like a s
[
https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801182#action_12801182
]
Yonik Seeley commented on LUCENE-2216:
--
Thanks Dawid!
hashCode and equals prob
[
https://issues.apache.org/jira/browse/LUCENE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved LUCENE-2197.
--
Resolution: Fixed
committed.
> StopFilter should not create a new CharArraySet if the gi
On Tue, Jan 12, 2010 at 6:27 PM, Marvin Humphrey wrote:
> return (targetSize >> 3) + (targetSize < 9 ? 3 : 6) + targetSize;
>
> For input values of 9 or greater, all that formula does is multiply by 1.125
> and add 6. (Values enumerated below my sig.)
>
> The comment appears to have originated
[
https://issues.apache.org/jira/browse/LUCENE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798040#action_12798040
]
Yonik Seeley commented on LUCENE-2197:
--
Sorry Simon... I think I just got fe
[
https://issues.apache.org/jira/browse/LUCENE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-2197:
-
Attachment: LUCENE-2197.patch
Here's a patch that reverts to the previous behavior of usin
[
https://issues.apache.org/jira/browse/LUCENE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797784#action_12797784
]
Yonik Seeley commented on LUCENE-2197:
--
Comment from LUCENE-2094 the other issue
[
https://issues.apache.org/jira/browse/LUCENE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797779#action_12797779
]
Yonik Seeley commented on LUCENE-2197:
--
bq. Yet, according to the javadoc,
[
https://issues.apache.org/jira/browse/LUCENE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797740#action_12797740
]
Yonik Seeley commented on LUCENE-2094:
--
I obviously haven't had the chanc
[
https://issues.apache.org/jira/browse/LUCENE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797701#action_12797701
]
Yonik Seeley commented on LUCENE-2195:
--
It's not quite the same - no method
[
https://issues.apache.org/jira/browse/LUCENE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797692#action_12797692
]
Yonik Seeley commented on LUCENE-2195:
--
Seems that this patch would just slow th
[
https://issues.apache.org/jira/browse/LUCENE-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790360#action_12790360
]
Yonik Seeley commented on LUCENE-2156:
--
ensureOpen() is to help catch co
[
https://issues.apache.org/jira/browse/LUCENE-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788925#action_12788925
]
Yonik Seeley commented on LUCENE-2142:
--
+1
> FieldCache.getStringIndex sho
[
https://issues.apache.org/jira/browse/LUCENE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787669#action_12787669
]
Yonik Seeley commented on LUCENE-1377:
--
bq. solr users benefit on the next rel
[
https://issues.apache.org/jira/browse/LUCENE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787637#action_12787637
]
Yonik Seeley commented on LUCENE-1377:
--
bq. Anything which isn't Solr
[
https://issues.apache.org/jira/browse/LUCENE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787626#action_12787626
]
Yonik Seeley commented on LUCENE-2135:
--
bq. Hmm... this actually gets tricky to
[
https://issues.apache.org/jira/browse/LUCENE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787601#action_12787601
]
Yonik Seeley commented on LUCENE-1377:
--
bq. maybe this just gives another reason
[
https://issues.apache.org/jira/browse/LUCENE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787600#action_12787600
]
Yonik Seeley commented on LUCENE-1377:
--
bq. Who is this "we" of which
[
https://issues.apache.org/jira/browse/LUCENE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787586#action_12787586
]
Yonik Seeley commented on LUCENE-1377:
--
There are some downsides for Solr: if t
[
https://issues.apache.org/jira/browse/LUCENE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787514#action_12787514
]
Yonik Seeley commented on LUCENE-2135:
--
bq. A better approach is to don IR-k
On Tue, Dec 8, 2009 at 10:25 AM, Michael McCandless
wrote:
> Sorry, right, test passed on trunk, but it's still not valid even on
> trunk (I think?). Ie TermEnum.term() is undefined until you've called
> next?
You're thinking TermDocs I think - TermEnum.term() is defined to be
positioned on or a
[
https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784990#action_12784990
]
Yonik Seeley commented on LUCENE-1483:
--
That's strange... looks like Sorte
[
https://issues.apache.org/jira/browse/LUCENE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783829#action_12783829
]
Yonik Seeley edited comment on LUCENE-2094 at 11/30/09 8:1
[
https://issues.apache.org/jira/browse/LUCENE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783829#action_12783829
]
Yonik Seeley commented on LUCENE-2094:
--
bq. Yes it causes. If you have an old i
[
https://issues.apache.org/jira/browse/LUCENE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783796#action_12783796
]
Yonik Seeley commented on LUCENE-2094:
--
> > Why? What undesirable things
1 - 100 of 1775 matches
Mail list logo
