[
https://issues.apache.org/jira/browse/LUCENE-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rudi Quark closed LUCENE-1399.
--
Resolution: Fixed
Fix Version/s: 2.4
This issue seems to be fixed by 2.4 version.
> NullPointe
[
https://issues.apache.org/jira/browse/LUCENE-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633653#action_12633653
]
Michael McCandless commented on LUCENE-1342:
Sorry -- I don't know which speci
[
https://issues.apache.org/jira/browse/LUCENE-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633654#action_12633654
]
Michael McCandless commented on LUCENE-1399:
Super thanks Rudi!
> NullPointer
[
https://issues.apache.org/jira/browse/LUCENE-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reopened LUCENE-1399:
> NullPointerException issue with single IndexWriter instance shared among
> multiple
[
https://issues.apache.org/jira/browse/LUCENE-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1399.
Resolution: Duplicate
Dup of LUCENE-1335.
> NullPointerException issue with singl
[
https://issues.apache.org/jira/browse/LUCENE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633656#action_12633656
]
Michael McCandless commented on LUCENE-1393:
Indeed this is fixed; we once aga
Paul Elschot wrote:
I had another look at SegmentTermDocs.skipTo() and at
SegmentTermPositions, and I think I'm beginning to get
your point.
Could it be doable per skipInterval docs?
Almost ... but not quite, except maybe for the first segment being
merged.
The problem is, the new skip data
Deprecation of autoCommit in 2.4 leads to compile problems, when autoCommit
should be false
---
Key: LUCENE-1401
URL: https://issues.apache.org/jira/browse/LUCENE-1401
[
https://issues.apache.org/jira/browse/LUCENE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1401:
---
Affects Version/s: 2.9
Fix Version/s: 2.9
2.4
> Depre
[
https://issues.apache.org/jira/browse/LUCENE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1401:
--
Assignee: Michael McCandless
> Deprecation of autoCommit in 2.4 leads to compi
[
https://issues.apache.org/jira/browse/LUCENE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633662#action_12633662
]
Michael McCandless commented on LUCENE-1401:
Achieving the migration from aut
Here is what I'm trying to do:
say a lucene document:
name: abc ^10
organization: xyz ^3
^10 and ^3 are boosts in the document.
now if I query name: abc ^5 AND organization: xyz this will work.
but if I query (default_field): abc^5 AND xyz this won't work.
Now what I want is that a text can be
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1402:
--
Fix Version/s: (was: 2.4)
Affects Version/s: 2.4
> CheckIndex API changed without
CheckIndex API changed without backwards compaitibility
---
Key: LUCENE-1402
URL: https://issues.apache.org/jira/browse/LUCENE-1402
Project: Lucene - Java
Issue Type: Bug
Componen
[
https://issues.apache.org/jira/browse/LUCENE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LUCENE-1380:
--
Attachment: LUCENE-1380-PositionFilter.patch
> If you really want to do this change is this la
[
https://issues.apache.org/jira/browse/LUCENE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LUCENE-1380:
--
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
Summary: Patch f
[
https://issues.apache.org/jira/browse/LUCENE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633756#action_12633756
]
Steven Rowe commented on LUCENE-1380:
-
A couple of comments on the PositionFilter patc
Op Tuesday 23 September 2008 10:56:04 schreef Michael McCandless:
> Paul Elschot wrote:
> > I had another look at SegmentTermDocs.skipTo() and at
> > SegmentTermPositions, and I think I'm beginning to get
> > your point.
> >
> > Could it be doable per skipInterval docs?
>
> Almost ... but not quite
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1402:
--
Assignee: Michael McCandless
> CheckIndex API changed without backwards compai
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633785#action_12633785
]
Michael McCandless commented on LUCENE-1402:
Good point -- I'll restore the ol
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1402:
---
Attachment: LUCENE-1402.patch
Attached patch. I plan to commit later today.
I rena
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633812#action_12633812
]
Uwe Schindler commented on LUCENE-1402:
---
I did not realize about LUCENE-1354, so I a
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633814#action_12633814
]
Uwe Schindler commented on LUCENE-1402:
---
In principle, by making each Checkindex an
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633821#action_12633821
]
Uwe Schindler commented on LUCENE-1402:
---
And I found a bug in CheckIndex.checkIndex(
StandardTokenizer - Improper Hostname Recognition
-
Key: LUCENE-1403
URL: https://issues.apache.org/jira/browse/LUCENE-1403
Project: Lucene - Java
Issue Type: Bug
Affects Versions: 2.3.2, 2
Paul Elschot wrote:
So, adding a document offset from the documents/frequencies
into the positions/payloads for each document would allow:
- bulk copying of the position/payloads during merging, and
- a more efficient implementation of TermPositions.skipTo()
in that decoding the positions
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633840#action_12633840
]
Michael McCandless commented on LUCENE-1402:
Good comments all around Uwe; I'l
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1402:
--
Attachment: LUCENE-1402-uwe.patch
I hope you did not start to do a patch. I created one, that
NPE in NearSpansUnordered.isPayloadAvailable()
---
Key: LUCENE-1404
URL: https://issues.apache.org/jira/browse/LUCENE-1404
Project: Lucene - Java
Issue Type: Bug
Components: Query/Scorin
[
https://issues.apache.org/jira/browse/LUCENE-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Smith updated LUCENE-1404:
--
Attachment: SpanQueryTest.java
unit test that causes exception attached
> NPE in NearSpansUnordered.i
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633858#action_12633858
]
Michael McCandless commented on LUCENE-1402:
Thanks Uwe. I'll merge yours wit
Hi,
When people add new issues to JIRA they most often don't set the "Fix Version"
field. Would it not be better to have a default value for that field, so that
new entries don't get forgotten when we filter by "Fix Version" looking for
issues to fix for the next release? If every issue had "
[
https://issues.apache.org/jira/browse/LUCENE-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Smith updated LUCENE-1404:
--
Fix Version/s: 2.4
> NPE in NearSpansUnordered.isPayloadAvailable()
> ---
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633851#action_12633851
]
thetaphi edited comment on LUCENE-1402 at 9/23/08 12:38 PM:
I think it makes more sense to leave fix version to committers when
they assign them self to the issue. I say this because of the hundreds
of open and unreviewed issues that one would have to update in the
tracker between each release.
23 sep 2008 kl. 21.33 skrev Otis Gospodnetic:
Hi,
Wh
Op Tuesday 23 September 2008 20:26:18 schreef Michael McCandless:
> Paul Elschot wrote:
> > So, adding a document offset from the documents/frequencies
> > into the positions/payloads for each document would allow:
> > - bulk copying of the position/payloads during merging, and
> > - a more effi
Isn't that update thing something that can be done in a single automated JIRA
step? I believe I've seen people do that.
Maybe my thinking/work style is different, but I find having to manually
setting Fix Version as one extra thing I need to do. I don't necessarily
assign things to myself, bu
[
https://issues.apache.org/jira/browse/LUCENE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1401:
---
Attachment: LUCENE-1401.patch
Attached patch that removes the new deprecated ctors,
[
https://issues.apache.org/jira/browse/LUCENE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1402:
---
Attachment: LUCENE-1402.patch
OK I merged the two patches.
Uwe, I prefer to keep Ch
[
https://issues.apache.org/jira/browse/LUCENE-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1404:
--
Assignee: Michael McCandless
> NPE in NearSpansUnordered.isPayloadAvailable()
[
https://issues.apache.org/jira/browse/LUCENE-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633945#action_12633945
]
Michael McCandless commented on LUCENE-1404:
I can confirm this... I'll commit
On 23-Sep-08, at 12:33 PM, Otis Gospodnetic wrote:
Hi,
When people add new issues to JIRA they most often don't set the
"Fix Version" field. Would it not be better to have a default value
for that field, so that new entries don't get forgotten when we
filter by "Fix Version" looking for
42 matches
Mail list logo
