[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adriano Crestani updated LUCENE-1567:
-
Attachment: lucene_trunk_FlexQueryParser_2009july29_v11.patch
{quote}
The warnings occur
[
https://issues.apache.org/jira/browse/LUCENE-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1628:
Attachment: LUCENE-1628.patch
add lowercasefilter, consistent with the arabic analyzer, its userfr
[
https://issues.apache.org/jira/browse/LUCENE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1758:
Attachment: LUCENE-1758.patch
add lowercasefilter, and replace TODO: more tests with some tests.
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736982#action_12736982
]
Luis Alves commented on LUCENE-1567:
Hi Uwe,
{quote}
Will it be possible to specify so
: SortField.equals() and hashCode() contain a hint:
:
: /** Returns true if o is equal to this. If a
:* {...@link SortComparatorSource} (deprecated) or {...@link
:* FieldCache.Parser} was provided, it must properly
:* implement equals (unless a singleton is always used). */
:
:
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736966#action_12736966
]
Mark Miller commented on LUCENE-1486:
-
Okay thanks. I think we should pull it for 2.9.
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736965#action_12736965
]
Luis Alves commented on LUCENE-1486:
My understanding is that with "New flexible query
[
https://issues.apache.org/jira/browse/LUCENE-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1695:
Attachment: LUCENE-1695.patch
To trunk
> Update the Highlighter to use the new TokenStream API
>
[
https://issues.apache.org/jira/browse/LUCENE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736923#action_12736923
]
Karl Wettin commented on LUCENE-625:
bq. Karl, did you ever proceed on this patch? I'm
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1749:
Attachment: LUCENE-1749.patch
Updates:
* merged in updated ram usage estimator code
* updated mos
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736879#action_12736879
]
Michael Busch commented on LUCENE-1567:
---
{quote}
Could you also please fix the javad
[
https://issues.apache.org/jira/browse/LUCENE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736858#action_12736858
]
Jason Rutherglen commented on LUCENE-625:
-
Karl, did you ever proceed on this patch
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736851#action_12736851
]
Mark Miller commented on LUCENE-1486:
-
If we don't have a clear path for this very soo
> > My suggestion was to write the build script in a way that it checks out
> the
> > branch with the same revision number as the current base dir (trunk).
>
> I think this would work, as long as we always commit top-level and
> back-compat tag in one transaction (commit)?
>
> (And, even if we do
On Wed, Jul 29, 2009 at 4:31 PM, Uwe Schindler wrote:
> My suggestion was to write the build script in a way that it checks out the
> branch with the same revision number as the current base dir (trunk).
I think this would work, as long as we always commit top-level and
back-compat tag in one tra
On Wed, Jul 29, 2009 at 4:06 PM, Shai Erera wrote:
>> Or the undelete methods in IndexReader could just acquire the write lock?
>
> I'll need to open IndexReader w/ readOnly=false if I want to delete/undelete
> a document, no? And then I'll need to acquire the write lock, just like any
> other "wri
Thanks for the hint, Shai!
It is related, but the reason behind the tags was clear to me.
My suggestion was to write the build script in a way that it checks out the
branch with the same revision number as the current base dir (trunk).
Alternatively instead of putting a tag name into common
>
> Or the undelete methods in IndexReader could just acquire the write lock?
>
I'll need to open IndexReader w/ readOnly=false if I want to delete/undelete
a document, no? And then I'll need to acquire the write lock, just like any
other "write" operation done through IndexReader, right?
Or do y
On Wed, Jul 29, 2009 at 3:05 PM, Shai Erera wrote:
> Yes of course. I meant to create an undeleteDoc variant for every deleteDoc.
> So if IndexWriter has deleteDocuments(Term), I will add
> undeleteDocuments(Term). If IndexReader has deleteDocument(int), I will add
> undeleteDocument(int).
OK.
>
Uwe - I asked this question a while ago on LUCENE-1529 and this is an answer
Mike gave:
http://issues.apache.org/jira/browse/LUCENE-1529?focusedCommentId=12699177&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12699177
I think it's related to what you ask
Shai
On
[
https://issues.apache.org/jira/browse/LUCENE-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler closed LUCENE-1762.
-
Resolution: Fixed
Committed revision: 799025
This is without CHANGES.txt updates, because nothin
[
https://issues.apache.org/jira/browse/LUCENE-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1762:
--
Description:
No big deal.
growTermBuffer(int newSize) was using correct, but slightly hard t
Yes of course. I meant to create an undeleteDoc variant for every deleteDoc.
So if IndexWriter has deleteDocuments(Term), I will add
undeleteDocuments(Term). If IndexReader has deleteDocument(int), I will add
undeleteDocument(int).
It is up to the caller to make sure whatever he undeletes was inde
I do it that way:
- Checkout the backwards branch (not the tag) to
trunk/tags/lucene_2_4_back_compat_tests. I have this checkout everytime
there, I update it regularily together with trunk.
- Place and leave a build.properties files with the following line
in your trunk dir:
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736750#action_12736750
]
Mark Miller commented on LUCENE-1749:
-
bq. And then there is explain - IndexSearcher p
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1766.
Resolution: Fixed
> Add Thread-Safety note to IndexWriter JavaDoc
> --
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736732#action_12736732
]
Mark Miller commented on LUCENE-1749:
-
bq. figure out why previously mentioned tests a
[
https://issues.apache.org/jira/browse/LUCENE-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736724#action_12736724
]
Simon Willnauer commented on LUCENE-1767:
-
Jason, I would expect a sizeOf method t
[
https://issues.apache.org/jira/browse/LUCENE-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1767:
-
Attachment: LUCENE-1767.patch
Added sizeOf method
> Add sizeof to OpenBitSet
>
Add sizeof to OpenBitSet
Key: LUCENE-1767
URL: https://issues.apache.org/jira/browse/LUCENE-1767
Project: Lucene - Java
Issue Type: Improvement
Components: Index
Affects Versions: 2.4.1
Repo
[
https://issues.apache.org/jira/browse/LUCENE-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved LUCENE-1752.
-
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [New])
Thanks Koji!
> inc
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736696#action_12736696
]
Simon Willnauer commented on LUCENE-1766:
-
looks good. private final Object is rat
I think it's not documented anywhere... roughly these are the steps:
* Make mods to tags/lucene_2_4_.../* so "ant test-tag" passes
* Use "svn switch" to switch that tags checkout from a "tag" to the
2_4 back compat branch
* Commit from that dir & plant a new tag
* Update common-build.xm
+1
Though not by docID (since they aren't reliable in context of
IndexWriter)... and it should be undeleteDocuments (with an "s") since
it could affect more than one doc.
Mike
On Wed, Jul 29, 2009 at 10:55 AM, Shai Erera wrote:
> Hi
>
> I think such methods are useful for a Lucene app, which nee
Is their a wiki page on how to handle updating the back compat tests? I
found some mail regarding it, but most of what I found was older. The latest
I saw talked about the separate branch, and updating that branch with fixes
if you need too - but I see now it seems to work with tags?
Do I update th
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1766:
---
Attachment: LUCENE-1766.patch
OK another rev!
I backed away from giving particulars
[
https://issues.apache.org/jira/browse/LUCENE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736674#action_12736674
]
Mark Miller commented on LUCENE-1748:
-
This is going to require a patch to the 2.4 bac
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736662#action_12736662
]
Uwe Schindler commented on LUCENE-1567:
---
Just a question: Will it be possible to spe
[
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
checkpoint: refactored the sanity checking code into a utility class and w
[
https://issues.apache.org/jira/browse/LUCENE-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1763:
---
Attachment: LUCENE-1763.patch
Adds a ctor w/ IndexWriter to MergePolicy, LogMergePolicy, and its ext
Hi
I think such methods are useful for a Lucene app, which needs to rollback a
single document delete. Today, IndexReader offers undeleteAll(), which is a
bit extreme. There are two scenarios for this, that I know of:
1) (recently showed up on the user list) I'd like to synchronize documents
on di
[
https://issues.apache.org/jira/browse/LUCENE-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736646#action_12736646
]
Mark Miller commented on LUCENE-1695:
-
So without further objection, I'm going to comm
[
https://issues.apache.org/jira/browse/LUCENE-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736643#action_12736643
]
Michael McCandless commented on LUCENE-1763:
I think subclassing LMP is also e
[
https://issues.apache.org/jira/browse/LUCENE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736634#action_12736634
]
Robert Muir commented on LUCENE-1460:
-
Michael, sorry to leave it incomplete, I think
[
https://issues.apache.org/jira/browse/LUCENE-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736629#action_12736629
]
Mark Miller commented on LUCENE-1752:
-
Thanks Koji - I had forgotten about this one. I
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-1766:
Attachment: LUCENE-1766.patch
Added small but important fact about the synchronization Obj
[
https://issues.apache.org/jira/browse/LUCENE-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated LUCENE-1752:
---
Fix Version/s: 2.9
I'd like set 2.9. With the patch, highlighter works on our production
en
[
https://issues.apache.org/jira/browse/LUCENE-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736617#action_12736617
]
Shai Erera commented on LUCENE-1763:
I don't mind doing that ... but note that LMP's m
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1766:
---
Attachment: LUCENE-1766.patch
IndexReader & IndexSearcher as well.
> Add Thread-Saf
[
https://issues.apache.org/jira/browse/LUCENE-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736614#action_12736614
]
Michael McCandless commented on LUCENE-1763:
How about we:
* Simply change
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reopened LUCENE-1766:
I'll add to IndexReader & IndexSearcher as well.
> Add Thread-Safety note to IndexWri
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736557#action_12736557
]
Simon Willnauer commented on LUCENE-1766:
-
We don't afaik.
> Add Thread-Safety no
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1766.
Resolution: Fixed
OK thanks Simon!
> Add Thread-Safety note to IndexWriter JavaDo
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736556#action_12736556
]
Uwe Schindler commented on LUCENE-1766:
---
By the way: Do we have a TS note for IndexR
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736551#action_12736551
]
Simon Willnauer commented on LUCENE-1766:
-
looks good to me.
> Add Thread-Safety
[
https://issues.apache.org/jira/browse/LUCENE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736548#action_12736548
]
Michael McCandless commented on LUCENE-1758:
bq. perhaps both this and LUCENE-
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1766:
---
Attachment: LUCENE-1766.patch
Tweaked the wording... Simon if this looks OK to you I
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1766:
--
Assignee: Michael McCandless
> Add Thread-Safety note to IndexWriter JavaDoc
>
[
https://issues.apache.org/jira/browse/LUCENE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-1766:
Attachment: LUCENE-1766.patch
> Add Thread-Safety note to IndexWriter JavaDoc
> --
Add Thread-Safety note to IndexWriter JavaDoc
-
Key: LUCENE-1766
URL: https://issues.apache.org/jira/browse/LUCENE-1766
Project: Lucene - Java
Issue Type: Improvement
Affects Versions: 2.9
I'm guessing it was the empty source file I accidentally left in for
LUCENE-1754, that Hoss removed (thanks!). I think clover saw that as
an attempt to instrument a source in the empty-string package.
I'm unfamiliar w/ how to configure clover, but I agree we should make
sure it's testing coverage
[
https://issues.apache.org/jira/browse/LUCENE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736525#action_12736525
]
Richard Marr commented on LUCENE-1690:
--
There's also another problem I've just notice
incorrect doc description of fielded query syntax
-
Key: LUCENE-1765
URL: https://issues.apache.org/jira/browse/LUCENE-1765
Project: Lucene - Java
Issue Type: Bug
Components: Other
This seems to be fixed now. But there is something completely wrong with
clover:
If you look into the clover reports, there are a lot of classes having 0%
code coverage, but there are tests available (e.g. my new NumericRange
things). Also *all* contribs have 0%.
After thinking a little bit about
64 matches
Mail list logo
