[
https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733538#action_12733538
]
Simon Willnauer commented on LUCENE-1728:
-
Robert, I have looked at this patch and
[
https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733544#action_12733544
]
Robert Muir commented on LUCENE-1728:
-
Simon, I agree with you, there is a ton of work
[
https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733547#action_12733547
]
Simon Willnauer commented on LUCENE-1728:
-
bq. I don't want to sound like a compla
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733549#action_12733549
]
Michael McCandless commented on LUCENE-1567:
How are we going to migrate the s
This is more of a general question than lucene specific.
Is it possible to combine Dictionary based compression and Indexing, so that
indexing algorithm can use dictionary (hash table) created by compression
algorithm (or, the other way) ? are there any systems already doing like
this? is it poss
[
https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733552#action_12733552
]
Robert Muir commented on LUCENE-1728:
-
Simon OK, I will work on a patch that tries to
[
https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733556#action_12733556
]
Simon Willnauer commented on LUCENE-1728:
-
bq. Other than package structure, is th
[
https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733560#action_12733560
]
Robert Muir commented on LUCENE-1728:
-
Simon, yes some things may have to be public th
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733563#action_12733563
]
Michael McCandless commented on LUCENE-1644:
bq. couldn't you consider FILTER
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733578#action_12733578
]
Robert Muir commented on LUCENE-1644:
-
Mike, I see your point, I believe two things ar
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733580#action_12733580
]
Michael McCandless commented on LUCENE-1693:
OK I looked at the latest patch!
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733582#action_12733582
]
Michael McCandless commented on LUCENE-1644:
Your results seem to agree w/ Uwe
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733591#action_12733591
]
Michael McCandless commented on LUCENE-1567:
bq. How are we going to migrate t
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733593#action_12733593
]
Robert Muir commented on LUCENE-1644:
-
Mike: > 100M docs. it does not fit in os cache
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733598#action_12733598
]
Michael McCandless commented on LUCENE-1644:
bq. Mike: > 100M docs. it does no
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733603#action_12733603
]
Grant Ingersoll commented on LUCENE-1567:
-
OK, I have submitted the IP Clearance t
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733604#action_12733604
]
Grant Ingersoll commented on LUCENE-1693:
-
One of the things that works really wel
One of the things that seems to work really well in Solr for
documentation is that people seem to be of the mindset that any time
some new feature is developed or a significant change is being made, a
Wiki page is added/updated. I think this would be a really good habit
for us in Lucene to
[
https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733605#action_12733605
]
Tim Smith commented on LUCENE-1754:
---
If making NonMatchingScorer public, i suggest poten
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733637#action_12733637
]
Michael McCandless commented on LUCENE-1644:
Maybe, we simply go back to the b
[
https://issues.apache.org/jira/browse/LUCENE-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733662#action_12733662
]
Koji Sekiguchi commented on LUCENE-1752:
The patch was tested on their environment
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733676#action_12733676
]
Robert Muir commented on LUCENE-1644:
-
Mike, I am afraid that might hurt some people's
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733676#action_12733676
]
Robert Muir edited comment on LUCENE-1644 at 7/21/09 9:14 AM:
--
It would be great to get some repeatable tests for this type of thing into
the benchmark contrib. I had started work on that sometime back, but I don't
think I have it around anymore.
On Tue, Jul 21, 2009 at 12:14 PM, Robert Muir (JIRA) wrote:
>
>[
> https://issues.apache.org/jira/browse/LUCE
Mark I agree, plus multitermquery is pretty complex to benchmark wrt this issue
Because the behavior of someone using it for Trie is really different
than someone like me using it for natural language.
it will probably fit a different distribution (maybe not zipf) and
creating a heuristic to meet
[
https://issues.apache.org/jira/browse/LUCENE-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733740#action_12733740
]
Jason Rutherglen commented on LUCENE-1750:
--
{quote}We cannot merge A w/ D, becaus
bq. * Are we going to keep Token.java or not? (Current patch still has it
deprecated).
I need to know this as well - I have to make a new Token class for the
Highlighter package if this one is deprecated. It would seem a convenience to
keep it around.
On Tue, Jul 21, 2009 at 8:51 AM, Grant Ingers
[
https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733748#action_12733748
]
Shai Erera commented on LUCENE-1754:
So if we agree that scorer() cannot return null,
[
https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733753#action_12733753
]
Yonik Seeley commented on LUCENE-1754:
--
bq. So if we agree that scorer() cannot retur
[
https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733756#action_12733756
]
Tim Smith commented on LUCENE-1754:
---
Here's a couple of use cases where a Query should r
[
https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733759#action_12733759
]
Shai Erera commented on LUCENE-1754:
bq. hence one would get a cast exception if "retu
[
https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733760#action_12733760
]
Shai Erera commented on LUCENE-1754:
bq. BooleanQuery could then also do instanceof ch
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733761#action_12733761
]
Uwe Schindler commented on LUCENE-1693:
---
Mark Miller on java-dev:
bq. * Are we goin
[
https://issues.apache.org/jira/browse/LUCENE-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733762#action_12733762
]
Shai Erera commented on LUCENE-1750:
bq. I think we can refine this to only merge cont
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733765#action_12733765
]
Uwe Schindler commented on LUCENE-1693:
---
{quote}
bq. * Are we going to keep Token.ja
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733769#action_12733769
]
Michael McCandless commented on LUCENE-1644:
bq. In this case the filter would
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733770#action_12733770
]
Shai Erera commented on LUCENE-1076:
So Mike - just to clarify. If I have 3 segments:
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733771#action_12733771
]
Michael McCandless commented on LUCENE-1076:
Well... one option might be "the
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733775#action_12733775
]
Robert Muir commented on LUCENE-1644:
-
Mike, that heuristic sounds really promising to
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733778#action_12733778
]
Shai Erera commented on LUCENE-1076:
Well ... what I was thinking of is that even if t
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733780#action_12733780
]
Michael McCandless commented on LUCENE-1076:
maxDoc() is computed by simply su
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733781#action_12733781
]
Mark Miller commented on LUCENE-1644:
-
bq. Or we can punt on any smarts altogether for
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733782#action_12733782
]
Shai Erera commented on LUCENE-1076:
But how is a new doc ID allocated? Not by calling
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733783#action_12733783
]
Shai Erera commented on LUCENE-1076:
Besides Mike, there's something I don't understan
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733786#action_12733786
]
Robert Muir commented on LUCENE-1644:
-
Mike, sorry to flip back and forth on this sinc
Hey all, ready to get Lucene 2.9 out? Here are the remaining issues. I think
we are very close. There are 17 issues, but 3 of them are sub tasks of
another, so there is less than there looks.
ISSUE - SUMMARY - ASSIGNEE - LAST UPDATED
LUCENE-1504 SerialChainFilter should use DocSet API rather the
On Tue, Jul 21, 2009 at 9:13 PM, Mark Miller wrote:
> Hey all, ready to get Lucene 2.9 out? Here are the remaining issues. I think
> we are very close. There are 17 issues, but 3 of them are sub tasks of
> another, so there is less than there looks.
>
> ISSUE - SUMMARY - ASSIGNEE - LAST UPDATED
>
>
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733819#action_12733819
]
Michael McCandless commented on LUCENE-1076:
bq. But how is a new doc ID alloc
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733822#action_12733822
]
Michael McCandless commented on LUCENE-1076:
bq. if I merge two consecutive s
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733831#action_12733831
]
Tim Smith commented on LUCENE-1076:
---
i suppose you could do a preliminary round of mergi
[
https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1644:
---
Attachment: LUCENE-1644.patch
Attached rough patch -- javadocs are missing/not
updat
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733844#action_12733844
]
Jason Rutherglen commented on LUCENE-1076:
--
{quote}if I merge two consecutive seg
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1693:
--
Attachment: LUCENE-1693.patch
Updated patch that has the following changes:
- Updated QueryPar
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733857#action_12733857
]
Michael Busch commented on LUCENE-1693:
---
I agree - we should keep Token and not dep
[
https://issues.apache.org/jira/browse/LUCENE-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1738:
-
Attachment: LUCENE-1738.patch
* Added copy parameter that calls resolveExternalSegments
Couldn't we just update the description of the Jira issue itself so that
it reflects the current state of the patch? Often the inital description
of a Jira issue is never updated after the issue is created, even though
the patch and goals changed as discussions happened. I think that would
be m
Hmm... of course for big things like e.g. "Flexible Indexing" a wiki
page is useful, in case the feature is developed in multiple Jira
issues. But e.g. for the TokenStream patch we could just update the
description of 1693.
Michael
On 7/21/09 4:17 PM, Michael Busch wrote:
Couldn't we just up
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733889#action_12733889
]
Adriano Crestani commented on LUCENE-1486:
--
Hi,
I'm trying to understand what ki
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733893#action_12733893
]
Mark Miller commented on LUCENE-1486:
-
You might check the test class - it has a few b
: Couldn't we just update the description of the Jira issue itself so that it
: reflects the current state of the patch? Often the inital description of a
: Jira issue is never updated after the issue is created, even though the patch
: and goals changed as discussions happened. I think that would
> EG you could imagine an addIndexes* call getting started,
> completing a few merges. Then, concurrently, CMS picks & chooses
> some of those added external segments to merge with some of the
> original segments. Then addIndexes hits an exception. What do we
> do?
An exception due to an IO error
On 7/21/09 4:23 PM, Chris Hostetter wrote:
for those not familiar with the process happening in solr, there isn't a
seperate wiki page for every jira issue -- there is a seperate jira page
for each major component/feature. people submitting patches which add new
OK, I agree this makes sens
: OK, I agree this makes sense and would be good for major features.
:
: Btw: For the new TokenStream API I wrote in the original patch (JIRA-1422) a
: quite elaborate section in the package.html of the analysis package.
Yeah ... whenever javadocs make sense, they're probably better then wiki
d
On Tue, Jul 21, 2009 at 7:26 PM, Jason
Rutherglen wrote:
>> EG you could imagine an addIndexes* call getting started,
>> completing a few merges. Then, concurrently, CMS picks & chooses
>> some of those added external segments to merge with some of the
>> original segments. Then addIndexes hits an
On Tue, Jul 21, 2009 at 7:45 PM, Chris
Hostetter wrote:
> To me, the key is to make sure all functionality is documented *somewhere*
> before it gets committed. if it makes sense in javadocs great, if it's
> too widespread to fit neatly into the javadoc method/class/package
> structure, a wiki ti
[
https://issues.apache.org/jira/browse/LUCENE-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1747:
---
Fix Version/s: (was: 2.9)
3.1
Moving out... Simon (or anyone)
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adriano Crestani updated LUCENE-1486:
-
Attachment: junit_complex_phrase_qp_07_21_2009.patch
Thanks for the quick response Mark!
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733922#action_12733922
]
Adriano Crestani commented on LUCENE-1567:
--
{quote}
How are we going to migrate t
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733925#action_12733925
]
Michael Busch commented on LUCENE-1567:
---
{quote}
Wow, I'm scaried now, do you know a
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-1693:
--
Attachment: lucene-1693.patch
Uwe's latest patch with these changes:
- Token is not deprecate
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733931#action_12733931
]
Michael Busch commented on LUCENE-1693:
---
I think the points listed in the descriptio
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733933#action_12733933
]
Mark Miller commented on LUCENE-1486:
-
You may have to wait for the author, Mark Harwo
[
https://issues.apache.org/jira/browse/LUCENE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733937#action_12733937
]
Michael Busch commented on LUCENE-1460:
---
Now that LUCENE-1693 is almost committed, w
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733940#action_12733940
]
Michael Busch commented on LUCENE-1486:
---
Looking at the problems Adriano is seeing i
> LUCENE-1448 add getFinalOffset() to TokenStream Michael Busch 24/Jun/09
>
> This still needs to be addressed or pushed - the patch is good for
the old API but needs an update to the new API - sounds like the method of
> doing this has been worked out,
> but still needs to be addressed. If
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1749:
-
Attachment: LUCENE-1749.patch
More progress building on Mark's patch.
added some sanity checking that r
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733946#action_12733946
]
Mark Miller commented on LUCENE-1486:
-
I originally thought it might live in contrib a
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733946#action_12733946
]
Mark Miller edited comment on LUCENE-1486 at 7/21/09 6:43 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733949#action_12733949
]
Robert Muir commented on LUCENE-1460:
-
Michael, I think we should try to coordinate ti
[
https://issues.apache.org/jira/browse/LUCENE-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733952#action_12733952
]
Robert Muir commented on LUCENE-1628:
-
Mark, I think we should figure out a plan with
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733955#action_12733955
]
Hoss Man commented on LUCENE-1749:
--
note to self: of the contribs, TestRemoteSort had two
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733956#action_12733956
]
Adriano Crestani commented on LUCENE-1486:
--
{quote}
I see what Adriano was talkin
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733957#action_12733957
]
Mark Miller commented on LUCENE-1486:
-
{quote}
I think a user would expect a ParseExce
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733958#action_12733958
]
Mark Miller commented on LUCENE-1486:
-
bq. Well, if you guessed his intention correctl
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733961#action_12733961
]
Adriano Crestani commented on LUCENE-1486:
--
{quote}
I'll admit, the ... non exact
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733966#action_12733966
]
Mark Miller commented on LUCENE-1486:
-
bq. I think contrib would be a good place for n
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733982#action_12733982
]
Michael Busch commented on LUCENE-1486:
---
{quote}
It only supports a limited subset o
[
https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733986#action_12733986
]
Michael Busch commented on LUCENE-1728:
---
So we are going to move everything currentl
[
https://issues.apache.org/jira/browse/LUCENE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733987#action_12733987
]
Michael Busch commented on LUCENE-1460:
---
{quote}
Michael, I think we should try to c
[
https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733989#action_12733989
]
Robert Muir commented on LUCENE-1728:
-
yeah, except smart chinese analyzer. I am testi
[
https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1728:
Attachment: LUCENE-1728.txt
Simon, here is the new patch. It also has the changes to build.xml and
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734015#action_12734015
]
Luis Alves commented on LUCENE-1486:
I share same opinion as Michael,
the implementati
[
https://issues.apache.org/jira/browse/LUCENE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734016#action_12734016
]
Simon Willnauer commented on LUCENE-1460:
-
bq. It seems like 1728 is ready to comm
93 matches
Mail list logo
