[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546148
]
Michael Busch commented on LUCENE-584:
--
{quote}
1. introduce Matcher as superclass of Scorer and adapt javadocs
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546072
]
Michael Busch commented on LUCENE-1058:
---
I'm quite busy currently with other stuff. Feel free to go ahead ;)
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546069
]
Grant Ingersoll commented on LUCENE-1058:
-
OK, looks good to me and is much simpler. Only thing that gets c
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546062
]
Michael Busch commented on LUCENE-1058:
---
I like the TeeTokenFilter! +1
> New Analyzer for buffering tokens
>
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546058
]
Yonik Seeley commented on LUCENE-1058:
--
I think having the "tee" solves the many-to-many case... you can have m
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546052
]
Yonik Seeley commented on LUCENE-1058:
--
Very similar to what I came up with I think... (all untested, etc)
{co
[
https://issues.apache.org/jira/browse/LUCENE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546051
]
Doug Cutting commented on LUCENE-1044:
--
> How about if we don't sync every single commit point?
I'm confused.
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546050
]
Michael Busch commented on LUCENE-1058:
---
We need to change the CachingTokenFilter a bit (untested code):
{cod
[
https://issues.apache.org/jira/browse/LUCENE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546042
]
Michael McCandless commented on LUCENE-1044:
How about if we don't sync every single commit point?
I t
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546040
]
Grant Ingersoll commented on LUCENE-1058:
-
OK, I am trying not be fixated on the Analyzer. I guess I haven
[
https://issues.apache.org/jira/browse/LUCENE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546039
]
Michael McCandless commented on LUCENE-1044:
Woops, the last line in the table above is wrong (it's a co
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546031
]
Michael Busch commented on LUCENE-1058:
---
I think the ideas here make sense, e. g. to have a buffering
TokenFil
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546028
]
Yonik Seeley commented on LUCENE-1058:
--
I dunno... it feels like we should have the right generic solution
(ma
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546022
]
Grant Ingersoll commented on LUCENE-1058:
-
Any objection to me committing the CachedAnalyzer and CachedToken
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546004
]
Yonik Seeley commented on LUCENE-1058:
--
{quote}To some extent, I was thinking that this could help optimize Sol
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546002
]
Grant Ingersoll commented on LUCENE-1058:
-
{quote}
What if they wanted 3 fields instead of two?
{quote}
True
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545999
]
Yonik Seeley commented on LUCENE-1058:
--
{quote}As for the convoluted cross-field logic, I don't think it is all
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545995
]
Grant Ingersoll commented on LUCENE-1058:
-
{quote}
Maybe I'm missing something?
{quote}
No, I don't think y
[
https://issues.apache.org/jira/browse/LUCENE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1044:
---
Attachment: LUCENE-1044.take4.patch
OK I did a simplistic patch (attached) whereby F
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545966
]
Yonik Seeley commented on LUCENE-1058:
--
Maybe I'm not looking at it the right way yet, but I'm not sure this fe
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545959
]
Michael Busch commented on LUCENE-1058:
---
Grant,
I'm not sure why we need this patch.
For the testcase that y
DateTools with DAY resoltion dosn't work depending on your timezone
---
Key: LUCENE-1070
URL: https://issues.apache.org/jira/browse/LUCENE-1070
Project: Lucene - Java
Issue Type
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-1058:
Attachment: LUCENE-1058.patch
fixed a failing test
> New Analyzer for buffering tokens
>
[
https://issues.apache.org/jira/browse/LUCENE-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545921
]
Michael McCandless commented on LUCENE-1069:
This is the thread that spawned this issue:
http://www
[
https://issues.apache.org/jira/browse/LUCENE-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1069.
Resolution: Fixed
I just committed this. Thanks for catching this & reporting it
[
https://issues.apache.org/jira/browse/LUCENE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545919
]
Grant Ingersoll commented on LUCENE-935:
Done.
> Improve maven artifacts
> ---
>
>
[
https://issues.apache.org/jira/browse/LUCENE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1067.
Resolution: Fixed
I just committed this. Thanks Grant for catching this.
> TestS
[
https://issues.apache.org/jira/browse/LUCENE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545909
]
Michael McCandless commented on LUCENE-1067:
Thanks for the review Yonik! I'll commit shortly.
> TestS
[
https://issues.apache.org/jira/browse/LUCENE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545904
]
Yonik Seeley commented on LUCENE-1067:
--
Looks good, +1
> TestStressIndexing has intermittent failures
> --
On Nov 27, 2007 11:20 AM, robert engels <[EMAIL PROTECTED]> wrote:
> Can you describe exactly how the lockless commits affects this? Or
> could a reader be accessing the same RAMFile as a writer?
No read/commit lock exists any more... so a writer could be in the
process of writing the segments.nnn
[
https://issues.apache.org/jira/browse/LUCENE-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1069:
---
Attachment: LUCENE-1069.patch
Attached patch (with new unit test) fixes it. I plan
CheckIndex incorrectly sees deletes as index corruption
---
Key: LUCENE-1069
URL: https://issues.apache.org/jira/browse/LUCENE-1069
Project: Lucene - Java
Issue Type: Bug
Componen
Can you describe exactly how the lockless commits affects this? Or
could a reader be accessing the same RAMFile as a writer?
Seems that this really deviates from the simplicity of the write-once
design of the original Lucene.
Do writers share the same underlying RAMDirectory? Seems this wou
[
https://issues.apache.org/jira/browse/LUCENE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1067:
---
Attachment: LUCENE-1067.patch
Attached patch. All tests pass. I plan to commit in a
[
https://issues.apache.org/jira/browse/LUCENE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545885
]
Michael McCandless commented on LUCENE-1067:
OK I think this is just a thread safety issue on RAMFile.
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-1058:
Attachment: LUCENE-1058.patch
Added some more documentation, plus a test showing it is bad
[
https://issues.apache.org/jira/browse/LUCENE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545846
]
gsingers edited comment on LUCENE-1058 at 11/27/07 6:11 AM:
---
Added some more docum
I am the guy who throw the question about the Acronym - Host detection anomaly
in the StandardAnalyzer class.
Thanks to Shai Erera for traslating the discussion into the developers' list. I
am surprised about Chris Hostetter's response, as this issue was treated by
Erik Hatcher in Novemeber 2
Ooops, the issue number is 1064, not 1067.
sorry for the confusion.
On Nov 27, 2007 2:10 PM, Shai Erera <[EMAIL PROTECTED]> wrote:
> Hey guys,
>
> No one has commented on this feature yet. The change is very simple. I
> don't mind doing it myself, if you explain me the process ... do I just
> com
Hey guys,
No one has commented on this feature yet. The change is very simple. I don't
mind doing it myself, if you explain me the process ... do I just commit the
change and then one of the committers need to approve, or my part in this
issue is the patch I sent?
Cheers,
Shai Erera
Ok
I opened https://issues.apache.org/jira/browse/LUCENE-1068 and attached the
patch files.
I don't know if and how you can deprecate a JFlex grammar though.
On Nov 27, 2007 1:43 PM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> Yes, please open a JIRA issue and submit your patches.
>
> I wonder
[
https://issues.apache.org/jira/browse/LUCENE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1068:
---
Attachment: standardTokenizerImpl.patch
This is the result of re-compiling the JFlex fixed file. Not
[
https://issues.apache.org/jira/browse/LUCENE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1068:
---
Attachment: standardTokenizerImpl.jflex.patch
This fixes the JFlex definition file. The change simpl
[
https://issues.apache.org/jira/browse/LUCENE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1067:
--
Assignee: Michael McCandless
> TestStressIndexing has intermittent failures
>
Invalid behavior of StandardTokenizerImpl
-
Key: LUCENE-1068
URL: https://issues.apache.org/jira/browse/LUCENE-1068
Project: Lucene - Java
Issue Type: Bug
Components: Analysis
Rep
Yes, please open a JIRA issue and submit your patches.
I wonder if there is anyway to deprecate functionality in a JFlex
grammar? That is, is there anyway we can communicate to people that
both will be supported through 2.9 and then the correct way will be
supported in 3.x?
-Grant
On No
TestStressIndexing has intermittent failures
Key: LUCENE-1067
URL: https://issues.apache.org/jira/browse/LUCENE-1067
Project: Lucene - Java
Issue Type: Bug
Reporter: Grant Ingersoll
I opened https://issues.apache.org/jira/browse/LUCENE-1067 to track
the issue.
On Nov 27, 2007, at 6:10 AM, Michael McCandless wrote:
OK I just ran the test 5 times, also on quad Mac Pro, and got the
error to occur as well!
Ugh.
I will track it down.
Mike
"Grant Ingersoll" <[EMAIL PRO
OK I just ran the test 5 times, also on quad Mac Pro, and got the error to
occur as well!
Ugh.
I will track it down.
Mike
"Grant Ingersoll" <[EMAIL PROTECTED]> wrote:
> OK, I have seen this twice in the last two days:
> Testsuite: org.apache.lucene.index.TestStressIndexing
> [junit] Test
"Doug Cutting (JIRA)" <[EMAIL PROTECTED]> wrote on 26/11/2007 20:14:43:
> > I found out however that delaying the syncs (but intending tosync) also
> means keeping the file handles open [...]
>
> Not necessarily. You could just queue the file names for sync,
> close them, and then have the backgr
50 matches
Mail list logo
