[jira] Commented: (LUCENE-1713) Rename RangeQuery -> TermRangeQuery

[ https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726721#action_12726721 ] Uwe Schindler commented on LUCENE-1713: --- After committing this, I will open an issue

[jira] Updated: (LUCENE-1713) Rename RangeQuery -> TermRangeQuery

[ https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1713: -- Attachment: RangeQuery.java LUCENE-1713-backwards-branch.patch

[jira] Updated: (LUCENE-1713) Rename RangeQuery -> TermRangeQuery

[ https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1713: -- Attachment: RangeFilter.java > Rename RangeQuery -> TermRangeQuery > -

[jira] Commented: (LUCENE-1727) Order of stored Fields not maintained

[ https://issues.apache.org/jira/browse/LUCENE-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726705#action_12726705 ] Yonik Seeley commented on LUCENE-1727: -- bq. it was the entire basis for adding the Fi

[jira] Updated: (LUCENE-1726) IndexWriter.readerPool create new segmentReader outside of sync block

[ https://issues.apache.org/jira/browse/LUCENE-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rutherglen updated LUCENE-1726: - Attachment: LUCENE-1726.patch We don't block accessing readers in the IW.readerPool when

Re: [jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

Mark, I agree. its not really a good "option". Just saying that trec content that isn't ISO-8859-1 does exist :) I like Shai's idea of having a configurable option, this is more obvious. On Thu, Jul 2, 2009 at 5:23 PM, Mark Miller wrote: > bq. (For this I actually ran it with -Dfile.encoding=UTF-

Re: [jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

bq. (For this I actually ran it with -Dfile.encoding=UTF-8 to prevent this problem), so its "configurable" already...but not obvious. Right, I considered this option, but it changes the default encoding for the whole JVM - probably going to be fine for running benchmark, but not ideal in terms of

[jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

[ https://issues.apache.org/jira/browse/LUCENE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726685#action_12726685 ] Robert Muir commented on LUCENE-1730: - I'd like this to be configurable. I used this p

[jira] Commented: (LUCENE-1727) Order of stored Fields not maintained

[ https://issues.apache.org/jira/browse/LUCENE-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726679#action_12726679 ] Hoss Man commented on LUCENE-1727: -- bq. It's a good reminder to avoid documenting how som

Re: test-tag does not really test against 2.4, it tests against a branch from trunk on 2008-11-29

FYI, You can always create a branch from a specific revision. Don't know if this would help. On Jul 2, 2009, at 4:44 PM, Uwe Schindler wrote: When doing LUCENE-1723, I restored the old state of RangeQuery & Co from Lucene 2.4.1 and added all new things from 2.9 to the new renamed TermRangeQ

test-tag does not really test against 2.4, it tests against a branch from trunk on 2008-11-29

When doing LUCENE-1723, I restored the old state of RangeQuery & Co from Lucene 2.4.1 and added all new things from 2.9 to the new renamed TermRangeQuery & Co classes. Suddenly all tests in test-tag, that should easily pass the RangeQuery tests, failed. The source of the problem: the 2.4 backwards

[jira] Commented: (LUCENE-1488) issues with standardanalyzer on multilingual text

[ https://issues.apache.org/jira/browse/LUCENE-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726670#action_12726670 ] Robert Muir commented on LUCENE-1488: - Earwin, you are absolutely correct. though i w

[jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

[ https://issues.apache.org/jira/browse/LUCENE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726612#action_12726612 ] Shai Erera commented on LUCENE-1730: You're right, I didn't think in that direction. I

[jira] Commented: (LUCENE-1708) Improve the use of isDeleted in the indexing code

[ https://issues.apache.org/jira/browse/LUCENE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726614#action_12726614 ] Shai Erera commented on LUCENE-1708: bq. it was a quick back and forth at the end. Got

[jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

[ https://issues.apache.org/jira/browse/LUCENE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726596#action_12726596 ] Mark Miller commented on LUCENE-1730: - The trec data you are using is ISO-8859-1. Woul

[jira] Issue Comment Edited: (LUCENE-1708) Improve the use of isDeleted in the indexing code

[ https://issues.apache.org/jira/browse/LUCENE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726593#action_12726593 ] Mark Miller edited comment on LUCENE-1708 at 7/2/09 11:05 AM: --

[jira] Commented: (LUCENE-1708) Improve the use of isDeleted in the indexing code

[ https://issues.apache.org/jira/browse/LUCENE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726593#action_12726593 ] Mark Miller commented on LUCENE-1708: - bq. There is a paragraph in CHANGES under "Chan

[jira] Commented: (LUCENE-1698) Change backwards-compatibility policy

[ https://issues.apache.org/jira/browse/LUCENE-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726590#action_12726590 ] Mark Miller commented on LUCENE-1698: - I agree. I think we have the tools we need, we

[jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

[ https://issues.apache.org/jira/browse/LUCENE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726582#action_12726582 ] Shai Erera commented on LUCENE-1730: I don't understand - the change is in TrecContent

[jira] Commented: (LUCENE-1708) Improve the use of isDeleted in the indexing code

[ https://issues.apache.org/jira/browse/LUCENE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726580#action_12726580 ] Shai Erera commented on LUCENE-1708: There is a paragraph in CHANGES under "Changes to

[jira] Commented: (LUCENE-1698) Change backwards-compatibility policy

[ https://issues.apache.org/jira/browse/LUCENE-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726575#action_12726575 ] Hoss Man commented on LUCENE-1698: -- -0 (Note: this proposal is remeniscent of Grant'

[jira] Commented: (LUCENE-1488) issues with standardanalyzer on multilingual text

[ https://issues.apache.org/jira/browse/LUCENE-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726571#action_12726571 ] Earwin Burrfoot commented on LUCENE-1488: - bq. There is no morphological processin

[jira] Commented: (LUCENE-1708) Improve the use of isDeleted in the indexing code

[ https://issues.apache.org/jira/browse/LUCENE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726563#action_12726563 ] Mark Miller commented on LUCENE-1708: - I suppose, to be fair, we do mention that we mi

[jira] Commented: (LUCENE-1713) Rename RangeQuery -> TermRangeQuery

[ https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726559#action_12726559 ] Uwe Schindler commented on LUCENE-1713: --- After comparing the old 2.4.1 javadocs with

[jira] Commented: (LUCENE-1708) Improve the use of isDeleted in the indexing code

[ https://issues.apache.org/jira/browse/LUCENE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726543#action_12726543 ] Mark Miller commented on LUCENE-1708: - I cant find the back compat discussion on this.

Re: changes-to-html

Steven A Rowe wrote: On 7/2/2009 at 9:52 AM, Mark Miller wrote: Looks like there is a little issue - New Features is coming under Bug Fixes. Its just kind of getting merged. There is a space in front of "New features". Header detection requires no leading whitespace, to distinguish h

RE: changes-to-html

On 7/2/2009 at 9:52 AM, Mark Miller wrote: > Looks like there is a little issue - New Features is coming under Bug > Fixes. Its just kind of getting merged. There is a space in front of "New features". Header detection requires no leading whitespace, to distinguish headers from stuff that belong

[jira] Updated: (LUCENE-1713) Rename RangeQuery -> TermRangeQuery

[ https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1713: -- Attachment: (was: LUCENE-1713.patch) > Rename RangeQuery -> TermRangeQuery > -

[jira] Updated: (LUCENE-1713) Rename RangeQuery -> TermRangeQuery

[ https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1713: -- Attachment: LUCENE-1713.patch correct patch. > Rename RangeQuery -> TermRangeQuery >

[jira] Updated: (LUCENE-1713) Rename RangeQuery -> TermRangeQuery

[ https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1713: -- Attachment: RangeFilter.java RangeQuery.java LUCENE-1713.patch

[jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

[ https://issues.apache.org/jira/browse/LUCENE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726507#action_12726507 ] Mark Miller commented on LUCENE-1730: - I think that it makes sense to make the default

Bug in DocInvertedPerField?

I hit NPE in DocInvertedPerField in the following scenario: 1) Create IndexWriter w/ a null Analyzer. 2) Add two fields to a Document, w/ a TokenStream (or one as not analyzed and one as TokenStream, or two not analyzed). 3) Add the document to the IndexWriter. The NPE comes from processFields (lin

[jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

[ https://issues.apache.org/jira/browse/LUCENE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726493#action_12726493 ] Shai Erera commented on LUCENE-1730: Thanks. Took me a while to think in that directio

[jira] Updated: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

[ https://issues.apache.org/jira/browse/LUCENE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated LUCENE-1730: --- Attachment: LUCENE-1730.patch All tests pass. > TrecContentSource should use a fixed encoding, rath

[jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

[ https://issues.apache.org/jira/browse/LUCENE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726492#action_12726492 ] Mark Miller commented on LUCENE-1730: - nice catch > TrecContentSource should use a fi

[jira] Created: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

TrecContentSource should use a fixed encoding, rather than system dependent --- Key: LUCENE-1730 URL: https://issues.apache.org/jira/browse/LUCENE-1730 Project: Lucene - Java

Re: svn commit: r790581 - /lucene/java/trunk/src/java/org/apache/lucene/search/RangeTermEnum.java

Thats a pretty simple conflict resolution. I think trying to lock down code while issues are in progress is generally not a great idea. More cons than pros in my mind. Generally, the onus is on the patch writer to continue to resolve conflicts until they commit AFAICT. That said, I have no p

Re: [jira] Commented: (LUCENE-1707) Don't use ensureOpen() excessively in IndexReader and IndexWriter

Can somebody try to revert the change and test it on Windows? On Thu, Jul 2, 2009 at 4:44 PM, Robert Muir wrote: > well then I have no idea why it doesn't fail. Except that perhaps its > EOL-related (as Shai said), and that the failure is somehow > platform-dependent due to newline differences b

RE: svn commit: r790581 - /lucene/java/trunk/src/java/org/apache/lucene/search/RangeTermEnum.java

Hrm, my work for LUCENE-1713 conflicted... I already added this to the renamed class. Please do not commit any changes to Range* classes before LUCENE-1713 is resolved. - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Mes

changes-to-html

Looks like there is a little issue - New Features is coming under Bug Fixes. Its just kind of getting merged. 13. LUCENE-1681: Fix infinite loop caused by a call to DocValues methods getMinValue, getMaxValue, getAverageValue. (Simon Willnauer via Mark Miller) New features 14. LUCENE-1411: Ad

Re: [jira] Commented: (LUCENE-1707) Don't use ensureOpen() excessively in IndexReader and IndexWriter

well then I have no idea why it doesn't fail. Except that perhaps its EOL-related (as Shai said), and that the failure is somehow platform-dependent due to newline differences between windows and unix (and the way these are encoded in UTF-16/stored in SVN)? I don't do really any work with files in

Re: [jira] Commented: (LUCENE-1707) Don't use ensureOpen() excessively in IndexReader and IndexWriter

Hudson runs all the tests and emails java-dev if any of them fail. On Thu, Jul 2, 2009 at 9:37 AM, Robert Muir (JIRA) wrote: > >[ > https://issues.apache.org/jira/browse/LUCENE-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726479#action_1272647

[jira] Commented: (LUCENE-1707) Don't use ensureOpen() excessively in IndexReader and IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726479#action_12726479 ] Robert Muir commented on LUCENE-1707: - bq. Why doesn't Hudson encounter this problem?

[jira] Commented: (LUCENE-1707) Don't use ensureOpen() excessively in IndexReader and IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726475#action_12726475 ] Shai Erera commented on LUCENE-1707: so do we need to change those back to not eol-sty

[jira] Commented: (LUCENE-1707) Don't use ensureOpen() excessively in IndexReader and IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726462#action_12726462 ] Robert Muir commented on LUCENE-1707: - my code was a little out of date. I am now expe

[jira] Commented: (LUCENE-1728) Move SmartChineseAnalyzer & resources to own contrib project

[ https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726458#action_12726458 ] Robert Muir commented on LUCENE-1728: - great, I like this too. any preference on names

[jira] Commented: (LUCENE-1728) Move SmartChineseAnalyzer & resources to own contrib project

[ https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726456#action_12726456 ] Simon Willnauer commented on LUCENE-1728: - bq. Simon, are you referring to Uwe's a

[jira] Commented: (LUCENE-1728) Move SmartChineseAnalyzer & resources to own contrib project

[ https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726453#action_12726453 ] Robert Muir commented on LUCENE-1728: - bq. I really like this approach as it keeps the

[jira] Issue Comment Edited: (LUCENE-1729) RuntimeException "no terms in field MODIFIED" in an empty index

[ https://issues.apache.org/jira/browse/LUCENE-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726415#action_12726415 ] Uwe Schindler edited comment on LUCENE-1729 at 7/2/09 2:58 AM: -

[jira] Commented: (LUCENE-1729) RuntimeException "no terms in field MODIFIED" in an empty index

[ https://issues.apache.org/jira/browse/LUCENE-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726415#action_12726415 ] Uwe Schindler commented on LUCENE-1729: --- The AUTO Sort option and FieldCache are dep

[jira] Created: (LUCENE-1729) RuntimeException "no terms in field MODIFIED" in an empty index

RuntimeException "no terms in field MODIFIED" in an empty index --- Key: LUCENE-1729 URL: https://issues.apache.org/jira/browse/LUCENE-1729 Project: Lucene - Java Issue Type: Bug

[jira] Commented: (LUCENE-1720) TimeLimitedIndexReader and associated utility class

[ https://issues.apache.org/jira/browse/LUCENE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726382#action_12726382 ] Shai Erera commented on LUCENE-1720: bq. Stop() removes a thread from 1) or 2) Minor

Contrib-Commiter access to ant scripts & docs/

While we where discussing issue https://issues.apache.org/jira/browse/LUCENE-1728 (moving chinese smart analyzer to sep. contrib) I realized that such a refactoring can hardly be done by a contrib commiter as it would include changing docs and ant scripts (javadoc) in /trunk etc. I would like to co

[jira] Commented: (LUCENE-1728) Move SmartChineseAnalyzer & resources to own contrib project

[ https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726362#action_12726362 ] Simon Willnauer commented on LUCENE-1728: - bq. After creating the new contrib, do