r.updateDocument(term,doc) method for inserts.
Cheers,
Mark
From: Grant Ingersoll
To: java-dev@lucene.apache.org
Sent: Mon, 29 March, 2010 13:11:56
Subject: Re: Incremental Field Updates
On Mar 29, 2010, at 2:26 AM, Mark Harwood wrote:
>
>
>>
&g
>Who ever said that some_condition should point to a unique document?
My assumption was, for now, we were still talking about the simpler case of
updating a single document.
If we extend the discussion to support set-based updates it's worth considering
the common requirements for updating set
>Variant d) sounds most logical? And enables all sorts of fun stuff.
So the duplicate-key docs can have different values for initial-insert fields
but partial updates will cause sharing of a common field value?
And subsequent same-key doc inserts do or don't share these previous
"partial-update
>I can delete by lucene-generated docId.
Which users used to have to find by first coding a primary-key-term search.
Delete by term removed this step to make life easier.
>If someone needs this, it can be built over lucene, without
>introducing it as a core feature and needlessly complicating
On 29 Mar 2010, at 07:45, Earwin Burrfoot wrote:
Of course introducing the idea of updates also introduces the notion of a
primary key and there's probably an entirely separate discussion to be had
around user-supplied vs Lucene-generated keys.
Not sure I see that need. Can you explain your re
Of course introducing the idea of updates also introduces the notion of a
primary key and there's probably an entirely separate discussion to be had
around user-supplied vs Lucene-generated keys.
Not sure I see that need. Can you explain your reasoning a bit more?
If you want to update a do
Of course introducing the idea of updates also introduces the notion of a
primary key and there's probably an entirely separate discussion to be had
around user-supplied vs Lucene-generated keys.
That aside, the biggest concern for me here is the impact that this is likely
to have on search -
[
https://issues.apache.org/jira/browse/LUCENE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850497#action_12850497
]
Mark Harwood commented on LUCENE-2306:
--
FYI, re changes to defaults. I try to
[
https://issues.apache.org/jira/browse/LUCENE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850494#action_12850494
]
Mark Harwood commented on LUCENE-2306:
--
bq. Should I commit?
Yes, thanks,
[
https://issues.apache.org/jira/browse/LUCENE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood resolved LUCENE-2306.
--
Resolution: Fixed
Fix Version/s: 3.1
Assignee: Mark Harwood
Committed in
>>Document doc = searcher.doc(i);
Isn't "i" your results order number as opposed to a lucene document id?
I.e. the first result could be document id 3,232,432 but you are asking for doc
#1
You need to get to doc id out of topDocs
Cheers
Mark
- Original Message
From: Dyutiman
To:
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835961#action_12835961
]
Mark Harwood commented on LUCENE-1486:
--
Double Ugh. Applying the patch for the
This is because phrases are expected to contain >1 clause and the
ComplexPhraseQueryParser was expecting a BooleanQuery from the base class
which is used to hold the elements in the phrase.
In this single-clause scenario I guess we could silently hide the error and
return whatever single query
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834819#action_12834819
]
Mark Harwood commented on LUCENE-1720:
--
bq. How do we proceed from here? Is the
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833902#action_12833902
]
Mark Harwood commented on LUCENE-1720:
--
bq. Mark, the only thing that remains i
[
https://issues.apache.org/jira/browse/LUCENE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833876#action_12833876
]
Mark Harwood edited comment on LUCENE-329 at 2/15/10 5:0
[
https://issues.apache.org/jira/browse/LUCENE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833876#action_12833876
]
Mark Harwood commented on LUCENE-329:
-
bq. consider simpler case
OK - but we nee
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833863#action_12833863
]
Mark Harwood commented on LUCENE-1720:
--
bq. BTW found and fixed a bu
[
https://issues.apache.org/jira/browse/LUCENE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833840#action_12833840
]
Mark Harwood commented on LUCENE-329:
-
My "best-practice" suggestion i
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833833#action_12833833
]
Mark Harwood commented on LUCENE-1720:
--
bq. Anyway, I'm putting that asid
[
https://issues.apache.org/jira/browse/LUCENE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833822#action_12833822
]
Mark Harwood commented on LUCENE-329:
-
The problem with ignoring IDF completel
[
https://issues.apache.org/jira/browse/LUCENE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833822#action_12833822
]
Mark Harwood commented on LUCENE-329:
-
The problem with ignoring IDF completel
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833013#action_12833013
]
Mark Harwood commented on LUCENE-1720:
--
bq. I think we should add some se
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1720:
-
Attachment: Lucene-1720.patch
Updated patch with TestTimeLimitingIndexReader and changes to
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832987#action_12832987
]
Mark Harwood commented on LUCENE-1720:
--
bq. I also want to a
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832721#action_12832721
]
Mark Harwood commented on LUCENE-1720:
--
bq. When's this ready to test with
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1720:
-
Attachment: Lucene-1720.patch
Moved ATM to o.a.l.util package
Added isProjectedToTimeout method
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832500#action_12832500
]
Mark Harwood commented on LUCENE-1720:
--
I'll pick this up
> TimeLimite
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832483#action_12832483
]
Mark Harwood commented on LUCENE-1720:
--
Agreed, might be useful to provide boo
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832470#action_12832470
]
Mark Harwood commented on LUCENE-1720:
--
The change to ATM isn't that big
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832444#action_12832444
]
Mark Harwood commented on LUCENE-1720:
--
Thanks for the updates, Shai.
Agree
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1720:
-
Attachment: ActivityTimeMonitor.java
TestTimeLimitedIndexReader.java
[
https://issues.apache.org/jira/browse/LUCENE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-725:
Attachment: NovelAnalyzer.java
Updated for new 3.0 APIs
> NovelAnalyzer - wraps your choice
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782521#action_12782521
]
Mark Harwood commented on LUCENE-1486:
--
Ugh. There's probably two separat
[
https://issues.apache.org/jira/browse/LUCENE-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768257#action_12768257
]
Mark Harwood commented on LUCENE-1999:
--
bq. and 2) you need it for every single
[
https://issues.apache.org/jira/browse/LUCENE-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768173#action_12768173
]
Mark Harwood commented on LUCENE-1999:
--
bq. couldn't the wrapper make a
[
https://issues.apache.org/jira/browse/LUCENE-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1999:
-
Attachment: matchflagger.patch
> Match spotter for all query ty
Match spotter for all query types
-
Key: LUCENE-1999
URL: https://issues.apache.org/jira/browse/LUCENE-1999
Project: Lucene - Java
Issue Type: New Feature
Affects Versions: 2.9
Reporter: Mark
I've been putting together some code to support highlighting of opaque query
clauses (cached filters, trie range, spatial etc etc) which shows some promise.
This is not intended as a replacement for the existing highlighter(s) which
deal with free-text but is instead concentrating on the hard-to
[
https://issues.apache.org/jira/browse/LUCENE-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762290#action_12762290
]
Mark Harwood commented on LUCENE-1910:
--
> 2 minutes to create a query b
[
https://issues.apache.org/jira/browse/LUCENE-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757924#action_12757924
]
Mark Harwood commented on LUCENE-1910:
--
Hi Thomas,
Following your request
>> It seems like something higher up must accept two rects and OR them together
>> during the searching?
That's the way I've done it before. It's like the old "Asteroids" arcade game
where as the ship drifts off-screen stage right it is simultaneously emerging
back from stage-left.
- Or
I think those boosts shown are reflecting the edit distance. What we can't see
from this is that the Similarity class used in execution is using the same IDF
for all terms. The other factors at play will be the term frequency in the doc,
its length and any doc boost.
I don't have access to the c
Despite making IDF a constant the edit distance should remain a factor
in the rankings so I would have thought this would give you what you
need.
Can you supply a more detailed example? Either print the rewritten
query or use the explain function
Cheers
Mark
On 27 Aug 2009, at 13:22, Ber
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748046#action_12748046
]
Mark Harwood commented on LUCENE-1486:
--
It does not stand on it's own
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1720:
-
Attachment: ActivityTimeMonitor.java
Had another run at ActivityTimeMonitor tonight and
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737270#action_12737270
]
Mark Harwood commented on LUCENE-1486:
--
No objections to pulling from core given
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: Lucene-1486 non default field.patch
Fix for phrases using QueryParser's non-de
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734355#action_12734355
]
Mark Harwood commented on LUCENE-1486:
--
{quote}
query: '(john OR jonathon)
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734349#action_12734349
]
Mark Harwood commented on LUCENE-1486:
--
{quote}for test checkMatches("\&q
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734337#action_12734337
]
Mark Harwood commented on LUCENE-1486:
--
bq. I think it's not a big deal
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734176#action_12734176
]
Mark Harwood commented on LUCENE-1720:
--
bq. Hey Mark. Have you made any prog
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734148#action_12734148
]
Mark Harwood commented on LUCENE-1486:
--
I'll try and catch up with so
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood closed LUCENE-1486.
Resolution: Fixed
Committed in 791579 - http://svn.apache.org/viewvc?rev=791579&view
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727685#action_12727685
]
Mark Harwood commented on LUCENE-1486:
--
Hi Mark,
Mind if I try committing this p
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726128#action_12726128
]
Mark Harwood commented on LUCENE-1720:
--
Maybe we should start by debugging
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726064#action_12726064
]
Mark Harwood commented on LUCENE-1720:
--
re points 1,2,3 - yep, will change.
re
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1720:
-
Attachment: ActivityTimeMonitor.java
Updated to allow >1 simultaneous timeout error to
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1720:
-
Attachment: (was: ActivityTimeMonitor.java)
> TimeLimitedIndexReader and associated util
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725741#action_12725741
]
Mark Harwood commented on LUCENE-1720:
--
bq. Ah, so we're assuming most acti
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725500#action_12725500
]
Mark Harwood commented on LUCENE-1720:
--
bq. Maybe we can benchmark this appr
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725197#action_12725197
]
Mark Harwood commented on LUCENE-1720:
--
bq. any custom Scorer which does a lo
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725176#action_12725176
]
Mark Harwood commented on LUCENE-1720:
--
bq. Oh, I did not mean to skip this c
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725164#action_12725164
]
Mark Harwood commented on LUCENE-1720:
--
Currently the class hinges on a "
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1720:
-
Attachment: ActivityTimedOutException.java
> TimeLimitedIndexReader and associated util
[
https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1720:
-
Attachment: TimeLimitedIndexReader.java
TestTimeLimitedIndexReader.java
Components: Index
Reporter: Mark Harwood
Assignee: Mark Harwood
Priority: Minor
An alternative to TimeLimitedCollector that has the following advantages:
1) Any reader activity can be time-limited rather than just single searches
e.g. the document retrieve phase.
2
Odd. I see you're responding to a message from Shai I didn't get. Some
mail being dropped somewhere along the line..
Why don't you use Thread.interrupt(), .isInterrupted() ?
Not sure where exactly you mean for that?
I'm not sure I understand that - how can a thread run >1 activity
simult
Aside, how about using a PQ for the threads' times, or a TreeMap.
That will save looping over the collection to find the next
candidate. Just an implementation detail though.
Shai
On Sat, Jun 27, 2009 at 3:31 AM, Mark Harwood
wrote:
Going back to my post re TimeLimitedIndexR
Going back to my post re TimeLimitedIndexReaders - here's an
incomplete but functional prototype:
http://www.inperspective.com/lucene/TimeLimitedIndexReader.java
http://www.inperspective.com/lucene/TestTimeLimitedIndexReader.java
The principle is that all reader accesses check a volatile vari
I think the Collector approach makes the most sense to me, since
it's the only object I fully control in the search process. I cannot
control Query implementations, and I cannot control the decisions
made by IndexSearcher. But I can always wrap someone else's
Collector with TLC and pass it
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723742#action_12723742
]
Mark Harwood commented on LUCENE-1486:
--
The fix was relatively straight-forward
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: LUCENE-1486.patch
Added fix for ConstantScoreQuery changes
> Wildcards, ORs
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719115#action_12719115
]
Mark Harwood commented on LUCENE-1486:
--
The primary reason (and perhaps n
+1
On 11 Jun 2009, at 21:32, Michael McCandless (JIRA) wrote:
[ https://issues.apache.org/jira/browse/LUCENE-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718629
#action_12718629 ]
Michael McCandless commented on LUCENE-1685:
-
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718573#action_12718573
]
Mark Harwood commented on LUCENE-1486:
--
Perhaps "hacky" was too st
Hi John/Grant.
I haven't done any more in developing WebLuke - although still use it regularly.
As Grant suggests there was an unease (mine) about bloating the Lucene
distribution size with GWT dependencies so it wasn't rolled into contrib.
However I guess I'm comfortable if no one else is conce
>When you create IndexReader, IndexWriter and others, you must pass in a
>Settings
> instance.
I think this would also help solve the steady growth of constructor variations
(18 in 2.4's IndexWriter vs 3 in Lucene 1.9).
- Original Message
From: Otis Gospodnetic
To: java-dev@luce
Welcome, Uwe.
Great work on the Trie piece - now if you could just settle the "Tree" vs "Try"
pronunciation dilemma .
:)
- Original Message
From: Mark Miller
To: java-dev@lucene.apache.org
Sent: Monday, 18 May, 2009 17:46:51
Subject: Re: Welcome Uwe Schindler as Lucene committ
[
https://issues.apache.org/jira/browse/LUCENE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703733#action_12703733
]
Mark Harwood commented on LUCENE-1621:
--
While we're poking around in this
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood resolved LUCENE-1500.
--
Resolution: Fixed
Assignee: Mark Harwood (was: Mark Harwood)
Committed in revision
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1500:
-
Attachment: Lucene-1500-NewException.patch
With updated Apache license header.
I'll c
[
https://issues.apache.org/jira/browse/LUCENE-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681531#action_12681531
]
Mark Harwood commented on LUCENE-1522:
--
I'm guessing that's not an
[
https://issues.apache.org/jira/browse/LUCENE-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood closed LUCENE-1559.
Resolution: Invalid
Working as designed with feature designed to prevent too-costly analysis
[
https://issues.apache.org/jira/browse/LUCENE-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681507#action_12681507
]
Mark Harwood commented on LUCENE-1559:
--
Ah. Try set
[
https://issues.apache.org/jira/browse/LUCENE-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681466#action_12681466
]
Mark Harwood commented on LUCENE-1559:
--
I ran a quick test and I dont think I c
[
https://issues.apache.org/jira/browse/LUCENE-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681344#action_12681344
]
Mark Harwood commented on LUCENE-1559:
--
>>Sorry...I don't know what
[
https://issues.apache.org/jira/browse/LUCENE-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681336#action_12681336
]
Mark Harwood commented on LUCENE-1559:
--
Can I close this then as it appears to b
[
https://issues.apache.org/jira/browse/LUCENE-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681323#action_12681323
]
Mark Harwood commented on LUCENE-1559:
--
Your code still imports POI and is
[
https://issues.apache.org/jira/browse/LUCENE-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681287#action_12681287
]
Mark Harwood commented on LUCENE-1559:
--
Sorry to be picky but can you submit a
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1500:
-
Attachment: Lucene-1500-NewException.patch
Added support for testing both Token start or end
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1500:
-
Attachment: (was: Lucene-1500-NewException.patch)
> Highlighter thr
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680125#action_12680125
]
Mark Harwood commented on LUCENE-1500:
--
Will submit a new patch ton
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: TestComplexPhraseQuery.java
Updated Junit test to test for phrases with clauses
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: (was: TestComplexPhraseQuery.java)
> Wildcards, ORs etc inside Phrase quer
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: ComplexPhraseQueryParser.java
Updated to cater for phrase clauses that produce no
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: (was: ComplexPhraseQueryParser.java)
> Wildcards, ORs etc inside Phrase quer
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677991#action_12677991
]
Mark Harwood commented on LUCENE-1500:
--
I struggle to see why endOffset Highlig
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677968#action_12677968
]
Mark Harwood commented on LUCENE-1500:
--
Isn't your example predicated on be
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677956#action_12677956
]
Mark Harwood commented on LUCENE-1500:
--
My thoughts were that this exception so
1 - 100 of 272 matches
Mail list logo
