[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719940#action_12719940
]
Uwe Schindler commented on LUCENE-1673:
---
bq. re: NumericField - it wouldn't have bac
I think the problem here is that the file was not renamed in SVN. As patches
in JIRA normally do not contain the rename (because they cannot applied with
all actions like renames automatically done), I think the rename got lost.
Renames only work correct, if the person who did the rename in his loc
[
https://issues.apache.org/jira/browse/LUCENE-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1692:
Attachment: LUCENE-1692.txt
add tests for dutchanalyzer.
this analyzer claims to implement snowba
History's not gone, just hard to get to. This is really manual, but afaik
you have to use the full URL @ 1 - revision_doomed_file_was_was_deleted_in
syntax:
svn log
http://svn.apache.org/repos/asf/lucene/java/trunk/src/java/org/apache/lucene/index/multisegmentreader.j...@782405|
less
Maybe this
See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/860/changes
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
yes it is. just needs a volunteer to help me commit the patch.
On Tue, Jun 16, 2009 at 6:15 AM, Yonik Seeley wrote:
> On Mon, Jun 15, 2009 at 10:53 PM, Shai Erera wrote:
> > But note that Query has weight() and createWeight(), which I am still
> > confused about why we have two of them. Maybe I c
On Mon, Jun 15, 2009 at 10:53 PM, Shai Erera wrote:
> But note that Query has weight() and createWeight(), which I am still
> confused about why we have two of them. Maybe I can consolidate them to one?
createWeight() raw weight, and weight() is a top-level normalized weight.
I don't think they sh
In LUCENE-1630 I've deprecated createWeight in favor of a new
createQueryWeight, also protected. So I can change the new one to public.
But note that Query has weight() and createWeight(), which I am still
confused about why we have two of them. Maybe I can consolidate them to one?
Anyway, I thin
The JavaDoc suggests that one can't have a tokenStreamValue and a
StringValue or binaryValue at the same time... any good reason for
this restriction?
/** The value of the field as a String, or null. If null, the Reader value,
* binary value, or TokenStream value is used. Exactly one of str
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719888#action_12719888
]
Yonik Seeley commented on LUCENE-1673:
--
re: NumericField - it wouldn't have back-comp
I thought SVN's rename was supposed to preserve history?
I just wanted to look up the history of MultiTermEnum, and when I went
to the file (now in DirectoryReader renamed from MultiSegmentReader)
but all the history is gone before the last rename. IntelliJ and "svn
log" both showed only 3 version
Grant Ingersoll wrote:
1. What about Highlighter
I would guess Highlighter has not been updated because its kind of a
royal * :)
--
- Mark
http://www.lucidimagination.com
-
To unsubscribe, e-mail: java-dev-unsubscr
Mark Miller wrote:
Grant Ingersoll wrote:
On Jun 14, 2009, at 8:05 PM, Michael Busch wrote:
I'd be happy to discuss other API proposals that anybody brings up
here, that have the same advantages and are more intuitive. We could
also beef up the documentation and give a better example about
Grant Ingersoll wrote:
On Jun 14, 2009, at 8:05 PM, Michael Busch wrote:
I'd be happy to discuss other API proposals that anybody brings up
here, that have the same advantages and are more intuitive. We could
also beef up the documentation and give a better example about how to
convert a st
[
https://issues.apache.org/jira/browse/LUCENE-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1692:
Attachment: LUCENE-1692.txt
answered my own question, here's tests for brazilian as a start.
> C
+1
Mike
On Mon, Jun 15, 2009 at 5:47 PM, Yonik Seeley wrote:
> I'm simply trying to create a query wrapper class to hold some
> additional metadata, and delegate all operations to the wrapped query.
> Something as simple as that can't do it because of java
> permissions (outside of lucene).
>
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1673:
--
Attachment: LUCENE-1673.patch
Updated patch:
- Remove ShiftAttribute
- Rename TrieUtils and co
[
https://issues.apache.org/jira/browse/LUCENE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719811#action_12719811
]
Paul Elschot commented on LUCENE-1583:
--
Midnight here, still reading :)
The patch lo
Thanks Alan.
I cross posted this to the Lucene dev list where we are discussing using
madvise for minimizing unnecessary IO cache usage when merging segments
(where we really want the newly merged segments in the IO cache rather than
the old segment files).
How would the advise method work? Woul
+1
it''s a kind of a factory method anyway no need to be protected.
On Mon, Jun 15, 2009 at 11:47 PM, Yonik
Seeley wrote:
> I'm simply trying to create a query wrapper class to hold some
> additional metadata, and delegate all operations to the wrapped query.
> Something as simple as that can
[
https://issues.apache.org/jira/browse/LUCENE-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719799#action_12719799
]
Robert Muir commented on LUCENE-1692:
-
first I looked at BrazilianAnalyzer... out of c
I'm simply trying to create a query wrapper class to hold some
additional metadata, and delegate all operations to the wrapped query.
Something as simple as that can't do it because of java
permissions (outside of lucene).
protected Weight createWeight(Searcher searcher) throws IOException {
Sounds promising, but I have to think about if there are not
side-effects of this change other than a slowdown for people who create
multiple tokens (which would be acceptable as you said, because it's not
recommended anyway and should be rare).
On 6/15/09 1:46 PM, Uwe Schindler wrote:
Maybe
[
https://issues.apache.org/jira/browse/LUCENE-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1684.
Resolution: Fixed
> Add matchVersion to StandardAnalyzer
> ---
[
https://issues.apache.org/jira/browse/LUCENE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719781#action_12719781
]
Robert Muir commented on LUCENE-973:
very nice. although it might be a tad trickier to
yeah about 5 seconds in I saw that and decided to stick with what I know :)
On Mon, Jun 15, 2009 at 5:10 PM, Mark Miller wrote:
> I may do the Highlighter. Its annoying though - I'll have to break back
> compat because Token is part of the public API (Fragmenter, etc).
>
> Robert Muir wrote:
>>
>>
Done, tests pass.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Michael McCandless [mailto:luc...@mikemccandless.com]
> Sent: Monday, June 15, 2009 10:40 PM
> To: java-dev@lucene.apache.org
> Subject:
[
https://issues.apache.org/jira/browse/LUCENE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719776#action_12719776
]
Steven Rowe commented on LUCENE-973:
+1 from me for inclusion in 2.9.
Mark, as you wro
I may do the Highlighter. Its annoying though - I'll have to break back
compat because Token is part of the public API (Fragmenter, etc).
Robert Muir wrote:
Michael OK, I plan on adding some tests for the analyzers that don't have any.
I didn't try to migrate things such as highlighter, which
[
https://issues.apache.org/jira/browse/LUCENE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1541:
---
Fix Version/s: (was: 2.9)
3.1
OK, moving out to 3.1.
> Trie
Sorry,
I think these new issues may also be in 3.1 (not all), but I want to have
this trie stuff with a clean API before 2.9 and not deprecate parts of it
again in 3.1, shortly after release :-(
This issues are no hard changes, its just a little bit API cleanup you can
do in your freetime :-] --
[
https://issues.apache.org/jira/browse/LUCENE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719769#action_12719769
]
Uwe Schindler commented on LUCENE-1541:
---
I see no real use in it, it does not affect
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719767#action_12719767
]
Jason Rutherglen commented on LUCENE-1313:
--
TestThreadedOptimize is throwing a en
On Mon, Jun 15, 2009 at 4:42 PM, Mark Miller wrote:
> Remember the last time we started to push for 2.9 in Dec/Jan :)
Yes this is very much on my mind too!!
So maybe, it's a race between the trie* "group" of issues, and the other 28 ;)
Mike
-
[
https://issues.apache.org/jira/browse/LUCENE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719766#action_12719766
]
Michael McCandless commented on LUCENE-1541:
Uwe, what's the plan on this issu
Maybe change the deprecation wrapper around next() and next(Token) [the
default impl of incrementToken()] to check, if the retrieved token is not
identical to the attribute and then just copy the contents to the
instance-Token? This would be a slowdown, but only be the case for very rare
TokenStrea
Michael OK, I plan on adding some tests for the analyzers that don't have any.
I didn't try to migrate things such as highlighter, which are
definitely just as important, only because I'm not familiar with that
territory.
But I think I can figure out what the various language analyzers are
trying
Michael McCandless (JIRA) wrote:
We're forking off new 2.9 issues left and
right here!!
Evil :) You guys are like small team working against me.
We still have 29+- issue to wrap up though, so probably plenty of time.
I hope we can set a rough target date soon though - it really feels like
I agree. It's my fault, the task of changing the contribs (LUCENE-1460)
is assigned to me for a while now - I just haven't found the time to do
it yet.
It's great that you started the work on that! I'll try to review the
patch in the next couple of days and help with fixing the remaining
ones
On Mon, Jun 15, 2009 at 4:21 PM, Uwe Schindler wrote:
> And, in tests: test/o/a/l/index/store is somehow wrong placed. The class
> inside should be in test/o/a/l/store. Should I move?
Please do!
Mike
-
To unsubscribe, e-mail: j
I have implemented most of that actually (the interface part and Token
implementing all of them).
The problem is a paradigm change with the new API: the assumption is
that there is always only one single instance of an Attribute. With the
old API, it is recommended to reuse the passed-in token
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719761#action_12719761
]
Michael McCandless commented on LUCENE-1673:
OK let's open a new issue for how
Michael, again I am terrible with such things myself...
Personally I am impressed that you have the back compat, even if you
don't change any code at all I think some reformatting of javadocs
might make the situation a lot friendlier. I just listed everything
that came to my mind immediately.
I g
> And I don't like the *useNewAPI*() methods either. I spent a lot of time
> thinking about backwards compatibility for this API. It's tricky to do
> without sacrificing performance. In API patches I find myself spending
> more time for backwards-compatibility than for the actual new feature! :(
By the way, there is an empty "de" subdir in SVN inside analysis. Can this
be removed?
And, in tests: test/o/a/l/index/store is somehow wrong placed. The class
inside should be in test/o/a/l/store. Should I move?
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMai
This is excellent feedback, Robert!
I agree this is confusing; especially having a deprecated API and only a
experimental one that replaces the old one. We need to change that.
And I don't like the *useNewAPI*() methods either. I spent a lot of time
thinking about backwards compatibility for th
Some great points - especially the decision between a deprecated API,
and a new experimental one subject to change. Bit of a rock and a hard
place for a new user.
Perhaps we should add a little note with some guidance.
- Mark
Robert Muir wrote:
let me try some slightly more constructive fee
> there's also a stray bold tag gone haywire somewhere, possibly
> .incrementToken()
I fixed this. This was going me on my nerves the whole day when I wrote
javadocs for NumericTokenStream...
Uwe
-
To unsubscribe, e-mail: java-
let me try some slightly more constructive feedback:
new user looks at TokenStream javadocs:
http://hudson.zones.apache.org/hudson/job/Lucene-trunk/javadoc/org/apache/lucene/analysis/TokenStream.html
immediately they see deprecated, text in red with the words
"experimental", warnings in bold, the
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719738#action_12719738
]
Uwe Schindler commented on LUCENE-1673:
---
I think, I remove the ShiftAttribute in com
Mark, I'll see if I can get tests produced for some of those analyzers.
as a new user of the new api myself, I think I can safely say the most
confusing thing about it is having the old deprecated API mixed in the
javadocs with it :)
On Mon, Jun 15, 2009 at 2:53 PM, Mark Miller wrote:
> Robert Mu
> If you understood that, you'd be able to look
> at the actual token value if you were interested in what shift was
> used. So it's redundant, has a runtime cost, it's not currently used
> anywhere, and it's not useful to fields other than Trie. Perhaps it
> shouldn't exist (yet)?
You are right
> On Mon, Jun 15, 2009 at 3:00 PM, Uwe Schindler wrote:
> > There is a new Attribute called ShiftAttribute (or
> NumericShiftAttribute),
> > when trie range is moved to core. This attribute contains the shifted-
> away
> > bits from the prefix encoded value during trie indexing.
>
> I was wonderin
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719729#action_12719729
]
Uwe Schindler commented on LUCENE-1673:
---
bq. Did you think about / decide against ma
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719726#action_12719726
]
Uwe Schindler commented on LUCENE-1673:
---
{quote}
bq. This will apply to int/long/flo
On Mon, Jun 15, 2009 at 3:00 PM, Uwe Schindler wrote:
> There is a new Attribute called ShiftAttribute (or NumericShiftAttribute),
> when trie range is moved to core. This attribute contains the shifted-away
> bits from the prefix encoded value during trie indexing.
I was wondering about this
> Also, what about the case where one might have attributes that are meant
> for downstream TokenFilters, but not necessarily for indexing? Offsets
> and type come to mind. Is it the case now that those attributes are not
> automatically added to the index? If they are ignored now, what if I
Robert Muir wrote:
Mark, I created an issue for this.
Thanks Robert, great idea.
I just think you know, converting an analyzer to the new api is really
not that bad.
I don't either. I'm really just complaining about the initial
readability. Once you know whats up, its not too much differ
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719699#action_12719699
]
Yonik Seeley commented on LUCENE-1673:
--
bq. This will apply to int/long/float/double
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719692#action_12719692
]
Michael McCandless commented on LUCENE-1673:
bq. The only open point is the na
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719689#action_12719689
]
Michael McCandless commented on LUCENE-1673:
bq. So one using new code must al
Mark, I created an issue for this.
I just think you know, converting an analyzer to the new api is really
not that bad.
reverse engineering what one of them does is not necessarily obvious,
and is completely unrelated but necessary if they are to be migrated.
I'd be willing to assist with some o
Robert Muir wrote:
As Lucene's contrib hasn't been fully converted either (and its been quite
some time now), someone has probably heard that groan before.
hope this doesn't sound like a complaint,
Complaints are fine in any case. Every now and then, it might cause a
little rant from me o
[
https://issues.apache.org/jira/browse/LUCENE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1673:
--
Attachment: LUCENE-1673.patch
Updated patch:
- now with extended JavaDocs
- additional tests f
On Jun 14, 2009, at 8:05 PM, Michael Busch wrote:
I'd be happy to discuss other API proposals that anybody brings up
here, that have the same advantages and are more intuitive. We could
also beef up the documentation and give a better example about how
to convert a stream/filter from the
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719665#action_12719665
]
Jason Rutherglen commented on LUCENE-1313:
--
Just wanted to give an update on this
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1313:
-
Summary: Near Realtime Search (was: Realtime Search)
> Near Realtime Search
> -
Contrib analyzers need tests
Key: LUCENE-1692
URL: https://issues.apache.org/jira/browse/LUCENE-1692
Project: Lucene - Java
Issue Type: Test
Components: contrib/analyzers
Reporter: Robert Mu
>
> As Lucene's contrib hasn't been fully converted either (and its been quite
> some time now), someone has probably heard that groan before.
hope this doesn't sound like a complaint, but in my opinion this is
because many do not have any tests.
I converted a few of these and its just grunt work
Yonik Seeley wrote:
The high-level description of the new API looks good (being able to
add arbitrary properties to tokens), unfortunately, I've never had the
time to try and use it and give any constructive feedback.
As far as difficulty of use, I assume this only applies to
implementing your o
The high-level description of the new API looks good (being able to
add arbitrary properties to tokens), unfortunately, I've never had the
time to try and use it and give any constructive feedback.
As far as difficulty of use, I assume this only applies to
implementing your own TokenFilter? It see
On Jun 14, 2009, at 8:05 PM, Michael Busch wrote:
I'm not sure why this (currently having to implement next() too) is
such an issue for you. You brought it up at the Lucene meetup too.
No user will ever have to implement both (the new API and the old)
in their streams/filters. The only reas
[
https://issues.apache.org/jira/browse/LUCENE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719653#action_12719653
]
Richard Marr commented on LUCENE-1690:
--
Sounds reasonable although that'll take a lit
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1486:
Attachment: LUCENE-1486.patch
Reformatted to lucene formatting, removed author tag, removed a coup
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719639#action_12719639
]
Mark Miller commented on LUCENE-1486:
-
Should this go in contrib rather than core? Tha
[
https://issues.apache.org/jira/browse/LUCENE-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1630:
---
Attachment: LUCENE-1630.patch
ok - let's start iterating on the patch. Anyone volunteer to accept it
On Jun 15, 2009, at 12:19 PM, Michael McCandless wrote:
I don't think anything was "held back" in this effort. Grant, are you
referring to LUCENE-1458? That's "held back" simply because the only
person working on it (me) got distracted by other things to work on.
I'm sorry, I didn't mean to
[
https://issues.apache.org/jira/browse/LUCENE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719635#action_12719635
]
Mark Miller commented on LUCENE-973:
You guys looking for this for 2.9?
If so, any vol
[
https://issues.apache.org/jira/browse/LUCENE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719630#action_12719630
]
Mark Miller commented on LUCENE-1688:
-
If no one else claims this for 2.9, I guess I'l
[
https://issues.apache.org/jira/browse/LUCENE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned LUCENE-1583:
---
Assignee: Mark Miller
I guess I'll do this one.
You out there reading Paul Elschot? This lo
[
https://issues.apache.org/jira/browse/LUCENE-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned LUCENE-1650:
---
Assignee: Mark Miller
> Small fix in CustomScoreQuery JavaDoc
>
I thought the primary goal of switching to AttributeSource (yes, the
name is very generic...) was to allow extensibility to what's created
per-Token, so that an app could add their own attrs without costly
subclassing/casting per Token, independent of other other "things"
adding their tokens, etc.
Why do you hate 1.6 Uwe?
Mike
On Mon, Jun 15, 2009 at 12:10 PM, Uwe Schindler (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Uwe Schindler updated LUCENE-1606:
> --
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719623#action_12719623
]
Robert Muir commented on LUCENE-1606:
-
Uwe, ok.
Not to try to complicate things, but
[
https://issues.apache.org/jira/browse/LUCENE-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned LUCENE-1599:
---
Assignee: Mark Miller
> SpanRegexQuery and SpanNearQuery is not working with MultiSearcher
>
[
https://issues.apache.org/jira/browse/LUCENE-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719619#action_12719619
]
Mark Miller commented on LUCENE-1599:
-
Something is modifying the original query itsel
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1606:
--
Fix Version/s: (was: 2.9)
3.0
I move this to 3.0 (and not 3.1), because
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719612#action_12719612
]
Robert Muir commented on LUCENE-1606:
-
Uwe, sorry about this.
I did just verify autom
It would help if we have a target date, then I'll know how many more X's I
need to mark on the Calendar :)
On Mon, Jun 15, 2009 at 6:56 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> :)
>
> But those days are numbered!
>
> Mike
>
> On Mon, Jun 15, 2009 at 11:55 AM, Uwe Schindler wro
:)
But those days are numbered!
Mike
On Mon, Jun 15, 2009 at 11:55 AM, Uwe Schindler wrote:
> By the way:
> I compiled core and corresponding tests with an old JDK 1.4 version, I found
> locally on my machine. Works fine!
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
By the way:
I compiled core and corresponding tests with an old JDK 1.4 version, I found
locally on my machine. Works fine!
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Uwe Schindler (JIRA) [mailt
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719607#action_12719607
]
Uwe Schindler commented on LUCENE-1606:
---
So I tend to move this to 3.0 or 3.1, becau
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719606#action_12719606
]
Uwe Schindler commented on LUCENE-1606:
---
Doesn't seem to work, I will check the sour
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719605#action_12719605
]
Robert Muir commented on LUCENE-1606:
-
Uwe, you are correct, I just took a glance at t
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719602#action_12719602
]
Uwe Schindler commented on LUCENE-1606:
---
Robert: I applied the patch locally, one te
Super, thanks Uwe!
Mike
On Mon, Jun 15, 2009 at 8:46 AM, Uwe Schindler wrote:
> Committed into general site docs (developer-resources) and into trunk's docs
> (large patch, because navigation changed).
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMa
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1313:
---
Fix Version/s: (was: 2.9)
3.1
OK let's push it to 3.1. It's
[
https://issues.apache.org/jira/browse/LUCENE-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1595:
---
Attachment: LUCENE-1595.patch
Patch adds a checkObsoleteSettings to PerfTask to alert on the use of
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719571#action_12719571
]
Mark Miller commented on LUCENE-1606:
-
I don't think there is a problem with BSD. I kn
[
https://issues.apache.org/jira/browse/LUCENE-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1518:
Fix Version/s: (was: 2.9)
3.1
> Merge Query and Filter classes
> --
1 - 100 of 130 matches
Mail list logo
