thanks hossman. will post it at java-user
hossman wrote:
>
>
> 1)
> http://wiki.apache.org/lucene-java/LuceneFAQ#head-adee7c1d869aa20101733944da79e15a1a2e7dfa
>
> FAQ: "Why do I have a deletable file (and old segment files remain) after
> running optimize?"
>
> 2) http://people.apache.org/~ho
1)
http://wiki.apache.org/lucene-java/LuceneFAQ#head-adee7c1d869aa20101733944da79e15a1a2e7dfa
FAQ: "Why do I have a deletable file (and old segment files remain) after
running optimize?"
2) http://people.apache.org/~hossman/#java-dev
Please Use "[EMAIL PROTECTED]" Not "[EMAIL PROTECTED]"
You
I managed to optimize my index successfully. The problem that I'm having now
is when I check the index using Lucene Index Toolbox there are a few files
in the index itself is deletable. I understand that optimize method will
merge the index files but How come there is still deletable index files i
: Here is how the span highlighter I have been working on uses the Memory
: contrib (I think I copied this from another contrib that has a dependency):
You might want to take a look at contrib/xml-query-parser/build.xml as a
slightly better example of this. It uses to test if the
dependency h
[
https://issues.apache.org/jira/browse/LUCENE-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1223:
---
Attachment: LUCENE-1223.patch
Attached patch that just propagates the "binary" value
lazy fields don't enforce binary vs string value
Key: LUCENE-1223
URL: https://issues.apache.org/jira/browse/LUCENE-1223
Project: Lucene - Java
Issue Type: Bug
Components: Index
[
https://issues.apache.org/jira/browse/LUCENE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577637#action_12577637
]
Michael McCandless commented on LUCENE-1217:
OK the new patch passes all tests
[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eks Dev updated LUCENE-1219:
Attachment: LUCENE-1219.patch
this one keeps addition of new methods localized to AbstractField, does not
[
https://issues.apache.org/jira/browse/LUCENE-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ning Li updated LUCENE-1035:
Attachment: LUCENE-1035.contrib.patch
Re-do as a contrib package. Creating BufferPooledDirectory with your
: I think, if you give it the same name, it just grays out the old ones. See
: https://issues.apache.org/jira/browse/LUCENE-550 for an example.
:
: Thus, I prefer #3, but am fine with #2 as well. #3 makes it easier, IMO, to
: find the latest.
use the same name if the patch serves the same purp
[
https://issues.apache.org/jira/browse/LUCENE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eks Dev updated LUCENE-1217:
Attachment: Lucene-1217-take1.patch
new patch, fixes isBinary status in LazyField
> use isBinary cached v
[
https://issues.apache.org/jira/browse/LUCENE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577601#action_12577601
]
Eks Dev commented on LUCENE-1217:
-
hah, this bug just justified this patch :)
sorry, I
[
https://issues.apache.org/jira/browse/LUCENE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577598#action_12577598
]
Michael McCandless commented on LUCENE-1217:
Actually seeing a test failure wi
[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577597#action_12577597
]
Eks Dev commented on LUCENE-1219:
-
I do not know for sure if this is something we could no
[
https://issues.apache.org/jira/browse/LUCENE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577591#action_12577591
]
Eks Dev commented on LUCENE-1217:
-
thanks fof looking into it!
Subclassing now with backwa
: Thanks Hoss!
I did the easy book-keeping part ... you're the guy fixing the bugs and
merging them into the release branches :)
-Hoss
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTE
[
https://issues.apache.org/jira/browse/LUCENE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1222:
-
Fix Version/s: 2.4
2.3.2
targeted for 2.3.2 bug fix release
> IndexWriter.doAfterFlu
[
https://issues.apache.org/jira/browse/LUCENE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1199:
-
Fix Version/s: 2.3.2
targeted for 2.3.2 bug fix release
> NullPointerException in IndexModifier.close()
[
https://issues.apache.org/jira/browse/LUCENE-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1210:
-
Fix Version/s: 2.3.2
targeted for 2.3.2 bug fix release
> IndexWriter & ConcurrentMergeScheduler deadlo
[
https://issues.apache.org/jira/browse/LUCENE-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1200:
-
Fix Version/s: 2.3.2
targeted for 2.3.2 bug fix release
> IndexWriter.addIndexes* can deadlock in rare
[
https://issues.apache.org/jira/browse/LUCENE-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1208:
-
Fix Version/s: 2.3.2
targeted for 2.3.2 bug fix release
> Deadlock case in IndexWriter on exception jus
Thanks Hoss!
Mike
On Mar 11, 2008, at 3:28 PM, Hoss Man (JIRA) wrote:
[ https://issues.apache.org/jira/browse/LUCENE-1198?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated LUCENE-1198:
-
Fix Version/s: 2.3.2
target
[
https://issues.apache.org/jira/browse/LUCENE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1198:
-
Fix Version/s: 2.3.2
targeted for 2.3.2 bug fix release
> Exception in DocumentsWriter.ThreadState.init
[
https://issues.apache.org/jira/browse/LUCENE-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1197:
-
Fix Version/s: 2.3.2
targeted for 2.3.2 bug fix release
> IndexWriter can flush too early when flushing
[
https://issues.apache.org/jira/browse/LUCENE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1191:
-
Fix Version/s: 2.3.2
targeted for 2.3.2 bug fix release
> If IndexWriter hits OutOfMemoryError it shoul
[
https://issues.apache.org/jira/browse/LUCENE-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1207:
-
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
Fix Version/s: (was: 2.3.1)
[
https://issues.apache.org/jira/browse/LUCENE-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577563#action_12577563
]
Yonik Seeley commented on LUCENE-1221:
--
If there is a real character that doesn't app
[
https://issues.apache.org/jira/browse/LUCENE-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577561#action_12577561
]
Marcel Reutegger commented on LUCENE-1221:
--
I'll see if I can build some kind of
[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577551#action_12577551
]
Michael McCandless commented on LUCENE-1219:
Hmm ... one problem is Fieldable
[
https://issues.apache.org/jira/browse/LUCENE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577547#action_12577547
]
Michael McCandless commented on LUCENE-1217:
Patch looks good. I will commit
[
https://issues.apache.org/jira/browse/LUCENE-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577544#action_12577544
]
Marcel Reutegger commented on LUCENE-1221:
--
> How/why are you seeing/using this c
[
https://issues.apache.org/jira/browse/LUCENE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1222.
Resolution: Fixed
> IndexWriter.doAfterFlush not being called when there are no de
IndexWriter.doAfterFlush not being called when there are no deletions flushed
-
Key: LUCENE-1222
URL: https://issues.apache.org/jira/browse/LUCENE-1222
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/LUCENE-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577513#action_12577513
]
Michael McCandless commented on LUCENE-1221:
Hmmm ... 0x is one of the "in
[
https://issues.apache.org/jira/browse/LUCENE-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated LUCENE-1221:
-
Attachment: OddTermTest.java
Test to reproduce the issue.
> DocumentsWriter truncates t
DocumentsWriter truncates term text at \u
-
Key: LUCENE-1221
URL: https://issues.apache.org/jira/browse/LUCENE-1221
Project: Lucene - Java
Issue Type: Bug
Components: Index
Affect
thanks,
I get it now, matter of taste :)
I would opt for,
#3 if you fix bugs from previous patch, decorate javadoc..., but you leave
things mainly as they are
#2 is better to mark interface, approach change or something more substantial
- Original Message
From: Grant Ingersoll <[EMA
[
https://issues.apache.org/jira/browse/LUCENE-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-1220.
-
Resolution: Invalid
Lucene knows nothing about PDFs. It is up to your application to ha
I think, if you give it the same name, it just grays out the old
ones. See https://issues.apache.org/jira/browse/LUCENE-550 for an
example.
Thus, I prefer #3, but am fine with #2 as well. #3 makes it easier,
IMO, to find the latest.
-Grant
On Mar 11, 2008, at 10:26 AM, Michael McCandle
PDF search is not working
-
Key: LUCENE-1220
URL: https://issues.apache.org/jira/browse/LUCENE-1220
Project: Lucene - Java
Issue Type: Test
Reporter: Akshya kumar
I uploaded pdf file in my repository and
I like #2.
I don't think we should delete/replace attachments in Jira. The
history can be useful.
Mike
eks dev wrote:
Michael, others
what is Lucene/Jira best practice for new versions of the same patch:
1. delete existing / add new patch wit the same name
2. add new patch with some fu
Michael, others
what is Lucene/Jira best practice for new versions of the same patch:
1. delete existing / add new patch wit the same name
2. add new patch with some funky version e.g. "Jira-1219-take3.patch"
3. just add new patch with the same name
?
[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eks Dev updated LUCENE-1219:
Attachment: LUCENE-1219.patch
Michael McCandless had some nice ideas on how to make getValue() change
pe
tip with extra checks is good, deprecate even better, I will update patch
- Original Message
From: Michael McCandless <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Tuesday, 11 March, 2008 2:45:56 PM
Subject: Re: Ideas to refactor Filed
Hello!
Responses below:
eks dev wr
Hello!
Responses below:
eks dev wrote:
Moin Moin Michael,
for the first issue I have crated LUCENE-1217, and for the second
one I have some questions.
if we maintain length and offset internally in Field than we have
one, imo, theoretical "legacy performance problem" as we need to
crea
[
https://issues.apache.org/jira/browse/LUCENE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1217:
--
Assignee: Michael McCandless
> use isBinary cached variable instead of instanc
[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1219:
--
Assignee: Michael McCandless
> support array/offset/ length setters for Field
[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eks Dev updated LUCENE-1219:
Attachment: LUCENE-1219.patch
> support array/offset/ length setters for Field with binary data
>
[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eks Dev updated LUCENE-1219:
Attachment: (was: LUCENE-1219.patch)
> support array/offset/ length setters for Field with binary data
[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eks Dev updated LUCENE-1219:
Attachment: LUCENE-1219.patch
all tests pass with this patch.
some polish needed and probably more testi
OK I've backported fixes for these issues to the 2.3 branch!
Mike
Michael Busch wrote:
Michael McCandless (JIRA) wrote:
[ https://issues.apache.org/jira/browse/LUCENE-1208?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel&focusedCommentId=12576941#action_12576941 ]
support array/offset/ length setters for Field with binary data
---
Key: LUCENE-1219
URL: https://issues.apache.org/jira/browse/LUCENE-1219
Project: Lucene - Java
Issue Type: Improv
Moin Moin Michael,
for the first issue I have crated LUCENE-1217, and for the second one I have
some questions.
if we maintain length and offset internally in Field than we have one, imo,
theoretical "legacy performance problem" as we need to
create new byte[length] and copy in order to prese
[
https://issues.apache.org/jira/browse/LUCENE-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiroaki Kawai updated LUCENE-1218:
--
Attachment: PassTokenizer.java
> PassTokenizerFilter that pass text in a Token
> -
PassTokenizerFilter that pass text in a Token
-
Key: LUCENE-1218
URL: https://issues.apache.org/jira/browse/LUCENE-1218
Project: Lucene - Java
Issue Type: New Feature
Components: Analysis
[
https://issues.apache.org/jira/browse/LUCENE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eks Dev updated LUCENE-1217:
Attachment: LUCENE-1217.patch
> use isBinary cached variable instead of instanceof in Filed
>
use isBinary cached variable instead of instanceof in Filed
---
Key: LUCENE-1217
URL: https://issues.apache.org/jira/browse/LUCENE-1217
Project: Lucene - Java
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen resolved LUCENE-1213.
-
Resolution: Fixed
Lucene Fields: [Patch Available] (was: [New])
Committed, thanks Trejka
[
https://issues.apache.org/jira/browse/LUCENE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576880#action_12576880
]
doronc edited comment on LUCENE-1213 at 3/11/08 1:00 AM:
--
Tre
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577326#action_12577326
]
Paul Elschot commented on LUCENE-584:
-
>From the traceback I suppose this happened at t
60 matches
Mail list logo
