Hi
I've read the analysis package.html and I found two issues:
1) The code sample under Invoking the Analyzer is broken. It calls
incrementToken() but inside the while it prints 'ts' (which is TokenStream)
and then do "t = ts.next()", which no longer works. That's an easy fix, so I
don't think a
[
https://issues.apache.org/jira/browse/LUCENE-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781102#action_12781102
]
Simon Willnauer commented on LUCENE-2068:
-
Robert, we can take the MatchV. Version
Hi Shai,
Thanks for the suggestions!
About your points:
1) This is really wrong, we can easily fix it for 3.1. Lucene 3.0 is
already in the vote phase and 2.9x is also already out.
2) Maybe the explanation is not so good. This text comes especially
from the 2.9 old to new TS
Eek, that's kinda spooky... that we didn't get to the root cause. I
sure hope Lucene is not to blame ;)
Mike
On Sat, Nov 21, 2009 at 9:21 PM, Robert Muir wrote:
> i sent a note to infrastructure about this, they reindexed, and everything
> is fixed now.
>
> On Sat, Nov 21, 2009 at 10:20 AM, Uwe
[
https://issues.apache.org/jira/browse/LUCENE-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781110#action_12781110
]
Michael McCandless commented on LUCENE-2075:
{quote}
bq. BTW the flex branch f
[
https://issues.apache.org/jira/browse/LUCENE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1278#action_1278
]
Thomas Mueller commented on LUCENE-1877:
> take it somewhere other than this close
[
https://issues.apache.org/jira/browse/LUCENE-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781112#action_12781112
]
Michael McCandless commented on LUCENE-2075:
bq. in both cases, its slower th
Thanks Uwe.
About (3), I use copyTo, not clone. I used the word 'clone' just out of
habit. I'll read more about captureState, but I think copyTo works fine for
me.
Abour (2), I still think it's confusing. When I read addAttribute, I get an
impression as if by calling this method, it is guaranteed
[
https://issues.apache.org/jira/browse/LUCENE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781113#action_12781113
]
Thomas Mueller commented on LUCENE-1877:
> detect the wakeup / polling interval ex
About (3): CopyTo is also only availabe for AttributeImpls, but not for the
interfaces (you have to cast first) and then you are warned. If you copyTo()
on a TernmAttribute, it may also copy other attributes with it, if
TermAttribute and PosIncr. Attribute are all implemented by the same
AttributeI
Perhaps copyTo works for me because I reference Token, but like I said it's
working for me ...
Thanks for the tip regarding clearAttributes(). I assume I'll get the same
behavior if I clear the attributes one by one, defaulting their values to
whatever are my defaults.
Well ... IMO as a user, the
Abvout clearAttributes: Just the warning if your clear the attributes one by
one, you have two problems:
- you can only clear attributes you know about. E.g. most
Tokenizers just set TermAttribute and OffsetAttribute (because only these
two attributes are interesting). The PosIncr attribu
AttributeSource.addAttribute should only accept interfaces, the missing test
leads to problems with Token.TOKEN_ATTRIBUTE_FACTORY
-
Key: LUCENE-2088
[
https://issues.apache.org/jira/browse/LUCENE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2088:
--
Attachment: LUCENE-2088.patch
Here the patch, will commit soon and respawn 3.0.
I will also m
[
https://issues.apache.org/jira/browse/LUCENE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781122#action_12781122
]
Earwin Burrfoot commented on LUCENE-2088:
-
bq. && Attribute.class.isAssignableFrom
If you use it type unsafe without generics, it will break. And we need it
for 2.9.
I was thinking about both variants and thought it would be better to leave
it in. I will merge this now to 2.9, too.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@theta
[
https://issues.apache.org/jira/browse/LUCENE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781124#action_12781124
]
Uwe Schindler commented on LUCENE-2088:
---
If you use it type unsafe without generics,
[
https://issues.apache.org/jira/browse/LUCENE-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2087:
--
Fix Version/s: 3.0
> Remove recursion in NumericRangeTermEnum
> --
[
https://issues.apache.org/jira/browse/LUCENE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2088:
--
Attachment: LUCENE-2088-test.patch
This patch shows how you can break.
As Shai said, the prob
[
https://issues.apache.org/jira/browse/LUCENE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781129#action_12781129
]
Uwe Schindler commented on LUCENE-2088:
---
Thinking about it more and reading
http://
[
https://issues.apache.org/jira/browse/LUCENE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781131#action_12781131
]
Uwe Schindler commented on LUCENE-2088:
---
But its no problem anymore, the sun bug is
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781134#action_12781134
]
Michael McCandless commented on LUCENE-1606:
Are we going to deprecate contrib
explore using automaton for fuzzyquery
--
Key: LUCENE-2089
URL: https://issues.apache.org/jira/browse/LUCENE-2089
Project: Lucene - Java
Issue Type: Wish
Components: Search
Reporter:
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781135#action_12781135
]
Robert Muir commented on LUCENE-1606:
-
bq. Are we going to deprecate contrib/regex wit
Hi,
I have built the artifacts for the final release of "Apache Lucene Java
3.0.0" a second time, because of a bug in the TokenStream API (found by Shai
Erera, who wanted to make "bad" things with addAttribute, breaking its
behaviour, LUCENE-2088) and an improvement in NumericRangeQuery (to preven
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781136#action_12781136
]
Mark Miller commented on LUCENE-2089:
-
bq. (i will assign this to him, I know he is it
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2089:
Description:
Mark brought this up on LUCENE-1606 (i will assign this to him, I know he is
itching
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2089:
Description:
Mark brought this up on LUCENE-1606 (i will assign this to him, I know he is
itching
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781138#action_12781138
]
Uwe Schindler commented on LUCENE-2089:
---
bq. ha - too much wine last night to laugh
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781139#action_12781139
]
Robert Muir commented on LUCENE-2089:
-
by the way, the only open impl of this algorith
was this why i saw strange benchmark results?
On Sun, Nov 22, 2009 at 9:52 AM, wrote:
> Author: mikemccand
> Date: Sun Nov 22 14:52:02 2009
> New Revision: 883088
>
> URL: http://svn.apache.org/viewvc?rev=883088&view=rev
> Log:
> LUCENE-1458 (on flex branch): small optimization to terms dict cac
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781140#action_12781140
]
Robert Muir commented on LUCENE-2089:
-
I hope its obvious from the benchmark why we sh
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781142#action_12781142
]
Mark Miller commented on LUCENE-2089:
-
I'll take a look anyway - too bad I can't find
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781144#action_12781144
]
Robert Muir commented on LUCENE-2089:
-
bq. I'll take a look anyway - too bad I can't f
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781149#action_12781149
]
Mark Miller commented on LUCENE-2089:
-
bq. we can precompute the tables with that algo
No, not really... just an optimization I found when hunting ;)
I'm working now on an AutomatonTermsEnum that uses the flex API
directly, to test that performance.
One of the major challenges with flex is the 4-way testing required.
Ie, you can have a non-flex or flex index, and then you can acces
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781151#action_12781151
]
Robert Muir commented on LUCENE-2089:
-
Mark, they would get large fast, but i think we
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781154#action_12781154
]
Robert Muir commented on LUCENE-2089:
-
Another twist, is that we have to support the '
On Sun, Nov 22, 2009 at 11:23 AM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> No, not really... just an optimization I found when hunting ;)
>
> I'm working now on an AutomatonTermsEnum that uses the flex API
> directly, to test that performance.
>
>
I didn't mean to 'bail out' on thi
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781155#action_12781155
]
Michael McCandless commented on LUCENE-1606:
{quote}
bq. Are we going to depre
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781156#action_12781156
]
Robert Muir commented on LUCENE-1606:
-
bq. Would be good to call out what's different
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781157#action_12781157
]
Mark Miller commented on LUCENE-2089:
-
bq. Mark, they would get large fast, but i thin
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781160#action_12781160
]
Michael McCandless commented on LUCENE-1606:
I don't have any wording -- I don
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781161#action_12781161
]
Robert Muir commented on LUCENE-2089:
-
bq. Generally, if you have any kind of length t
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781162#action_12781162
]
Robert Muir commented on LUCENE-1606:
-
bq. If it's "only" that the syntax is different
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781162#action_12781162
]
Robert Muir edited comment on LUCENE-1606 at 11/22/09 5:06 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781167#action_12781167
]
Mark Miller commented on LUCENE-2089:
-
Right, I wouldn't expect it to be great with a
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781168#action_12781168
]
Robert Muir commented on LUCENE-1606:
-
we call this out nicely in the current RegexQue
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781170#action_12781170
]
Robert Muir commented on LUCENE-2089:
-
Mark maybe, though it also depends largely on t
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781170#action_12781170
]
Robert Muir edited comment on LUCENE-2089 at 11/22/09 5:44 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781173#action_12781173
]
Mark Miller commented on LUCENE-2089:
-
bq. the constant prefix is just an optimizatio
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781174#action_12781174
]
Robert Muir commented on LUCENE-2089:
-
bq. With a prefix of 1 again? Yeah - you really
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781174#action_12781174
]
Robert Muir edited comment on LUCENE-2089 at 11/22/09 6:01 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781175#action_12781175
]
Mark Miller commented on LUCENE-2089:
-
bq. we must "use" the prefix, so the results ar
On Sun, Nov 22, 2009 at 11:31 AM, Robert Muir wrote:
>> No, not really... just an optimization I found when hunting ;)
>>
>> I'm working now on an AutomatonTermsEnum that uses the flex API
>> directly, to test that performance.
>>
>
> I didn't mean to 'bail out' on this
You didn't 'bail out'; I
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781178#action_12781178
]
Michael McCandless commented on LUCENE-1606:
OK that warning seems good. Mayb
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781175#action_12781175
]
Mark Miller edited comment on LUCENE-2089 at 11/22/09 6:06 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781179#action_12781179
]
Robert Muir commented on LUCENE-2089:
-
bq. Basically, what I'm saying is the old Fuzzy
Mike, I guess what I am implying is should i even bother with lucene-1606
and trunk?
or instead, should i be helping you, looking at TermsEnum, and working on
integrating it into flex?
On Sun, Nov 22, 2009 at 1:05 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> On Sun, Nov 22, 2009
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781175#action_12781175
]
Mark Miller edited comment on LUCENE-2089 at 11/22/09 6:12 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781180#action_12781180
]
Mark Miller commented on LUCENE-2089:
-
bq. if it requires more edits than that, go wit
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1606:
---
Attachment: LUCENE-1606-flex.patch
First cut @ cutting over to flex API attached --
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781182#action_12781182
]
Robert Muir commented on LUCENE-2089:
-
bq. I wouldnt really like it if it was default
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781183#action_12781183
]
Robert Muir commented on LUCENE-1606:
-
bq. Looks like flex API is faster for the slow
I think you should keep doing all LUCENE-1606 work (and, any other
issues) on trunk, and then we merge down to flex branch once it's
committed?
We shouldn't hold up any trunk features because flex is
coming... merging down every so often seems manageable so far (Mark?).
I'm hoping to finish flex
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781185#action_12781185
]
Robert Muir commented on LUCENE-1606:
-
Mike, I think your port to TermsEnum is correct
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781188#action_12781188
]
Michael McCandless commented on LUCENE-1606:
{quote}
One question, is it possi
ok, I only ask because some rework of this enum could be necessary to take
advantage of the new api.
examples include changing it to use char[] (easy) to prevent lots of string
creation, which was unavoidable with TermEnum since it is based on string.
i will never mention this again, but it could
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781190#action_12781190
]
Robert Muir commented on LUCENE-1606:
-
bq. Oh, that'd be great! It would be faster. I
[
https://issues.apache.org/jira/browse/LUCENE-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Kindgren updated LUCENE-1260:
---
Attachment: Lucene-1260-2.patch
I've added the old static methods again, but made them depre
bq. merging down every so often seems manageable so far (Mark?).
Yeah, this has been working great from my perspective.
Michael McCandless wrote:
> I think you should keep doing all LUCENE-1606 work (and, any other
> issues) on trunk, and then we merge down to flex branch once it's
> committed?
>
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781204#action_12781204
]
Mark Miller commented on LUCENE-2089:
-
bq. we find the nice n where this is almost as
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781205#action_12781205
]
Robert Muir commented on LUCENE-2089:
-
bq. but you will notice both the Lucene qp and
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781206#action_12781206
]
Mark Miller commented on LUCENE-2089:
-
I think it makes sense to allow leading ? - ???
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781207#action_12781207
]
Robert Muir commented on LUCENE-2089:
-
mark, you are right.
plus, the qp does not thr
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781208#action_12781208
]
Mark Miller commented on LUCENE-2089:
-
solr doesnt even allow for a constant prefix wi
[
https://issues.apache.org/jira/browse/LUCENE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781209#action_12781209
]
Simon Willnauer commented on LUCENE-2072:
-
I just added a testcase to check if the
[
https://issues.apache.org/jira/browse/LUCENE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-2072.
-
Resolution: Later
once jakarta-regexp fixes their issues we can go on and upgrade. for n
Yeah I think there will be lots of optimizing we can do, after flex lands.
Maybe stick w/ String for now? But open an issue, today, to remind us
to cutover to char[] post-flex?
Doing all processing in UTF8 is tantalizing too ;) This would mean no
conversion of the terms data on iterating from t
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781213#action_12781213
]
Michael McCandless commented on LUCENE-1606:
bq. it would be nice I think if T
On Sun, Nov 22, 2009 at 3:50 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> Yeah I think there will be lots of optimizing we can do, after flex lands.
>
> Maybe stick w/ String for now? But open an issue, today, to remind us
> to cutover to char[] post-flex?
>
ok, i'll create one.
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781214#action_12781214
]
Robert Muir commented on LUCENE-1606:
-
bq. I agree... though, this requires state (Uni
On Sun, Nov 22, 2009 at 3:52 PM, Robert Muir wrote:
>
> On Sun, Nov 22, 2009 at 3:50 PM, Michael McCandless
> wrote:
>>
>> Yeah I think there will be lots of optimizing we can do, after flex lands.
>>
>> Maybe stick w/ String for now? But open an issue, today, to remind us
>> to cutover to char[
convert automaton to char[] based processing and TermRef / TermsEnum api
Key: LUCENE-2090
URL: https://issues.apache.org/jira/browse/LUCENE-2090
Project: Lucene - Java
I guess here is where I just say that unicode and java are optimized for
utf-16 processing, and so while I agree with byte[] being available in
places like this for flex indexing,
I'm already nervous about seeing code / optimizations that only work well
with latin-1, and are very slow / buggy for a
[
https://issues.apache.org/jira/browse/LUCENE-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2068:
Attachment: LUCENE_2068.patch
added a CHANGES.txt entry. Will commit soon.
> fix reverseS
[
https://issues.apache.org/jira/browse/LUCENE-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-2068.
-
Resolution: Fixed
Commited in revision 883149
> fix reverseStringFilter for unicode 4.0
On Sun, Nov 22, 2009 at 4:06 PM, Robert Muir wrote:
> I guess here is where I just say that unicode and java are optimized for
> utf-16 processing
I agree, though leaving things as UTF8 works fine for low level stuff
(sorting, comparing equality, etc.)?
> and so while I agree with byte[] being a
On Sun, Nov 22, 2009 at 4:16 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> On Sun, Nov 22, 2009 at 4:06 PM, Robert Muir wrote:
> > I guess here is where I just say that unicode and java are optimized for
> > utf-16 processing
>
> I agree, though leaving things as UTF8 works fine fo
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781219#action_12781219
]
Michael McCandless commented on LUCENE-1606:
Besides TermsEnum.. TermRef is us
Hi,
As a non-counting vote:
+1 to release these artifacts as Lucene 3.0
I tested lucene-core.3.0.0.jar with my updated application, no problems
occurred. QueryParser search works, fieldcache/sorting works, numeric range
works. Reopen also works correct, no leftover open files. MMPaDirectory on
6
On Sun, Nov 22, 2009 at 4:19 PM, Robert Muir wrote:
>> What places specifically are you worried about?
>
> places like AutomatonQuery, where I found myself wanting to consider the
> option of processing byte[], when I know this is very bad!
Ahh OK :) Well you got the better of yourself before i
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781220#action_12781220
]
Robert Muir commented on LUCENE-1606:
-
bq. We can discuss this under the new [separate
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781221#action_12781221
]
Michael McCandless commented on LUCENE-1606:
bq. is there a jira issue for thi
[
https://issues.apache.org/jira/browse/LUCENE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781222#action_12781222
]
Michael McCandless commented on LUCENE-2090:
Spinoff from LUCENE-1606.
> conv
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781223#action_12781223
]
Robert Muir commented on LUCENE-1606:
-
bq. I thought you were about to open one!
I op
[
https://issues.apache.org/jira/browse/LUCENE-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781224#action_12781224
]
Michael McCandless commented on LUCENE-1260:
Patch looks good! Thanks Johan.
> Hi,
>
> As a non-counting vote:
>
> +1 to release these artifacts as Lucene 3.0
>
> I tested lucene-core.3.0.0.jar with my updated application, no problems
> occurred. QueryParser search works, fieldcache/sorting works, numeric
> range
> works. Reopen also works correct, no leftover open files
[
https://issues.apache.org/jira/browse/LUCENE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-2089:
Attachment: Moman-0.1.tar.gz
>From Moman author:
Absolutely. Sorry for the missing links. I had s
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781227#action_12781227
]
Robert Muir commented on LUCENE-1606:
-
bq. Actually... wouldn't we need to convert to
1 - 100 of 116 matches
Mail list logo
