LUCENE-1954 and 2.9.1

2009-10-28 Thread Bernd Fondermann
Hi,

Probably I'm too late to the party pointing out that LUCENE-1954 is
especially suited to be applied to the 2.9.x line.
The patch is obsolete for 3.x/TRUNK.

  Bernd

-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Updated: (LUCENE-1954) InitiatedIndex: CCE on casting NumericField to Field

2009-10-07 Thread Bernd Fondermann (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Fondermann updated LUCENE-1954:
-

Attachment: instantiated_writer_fieldable.patch

 InitiatedIndex: CCE on casting NumericField to Field
 

 Key: LUCENE-1954
 URL: https://issues.apache.org/jira/browse/LUCENE-1954
 Project: Lucene - Java
  Issue Type: Bug
  Components: contrib/*
Affects Versions: 2.9
Reporter: Bernd Fondermann
Priority: Minor
 Attachments: instantiated_writer_fieldable.patch


 An unchecked cast to ListField throws a ClassCastException when applied to, 
 for example, a NumericField.
 Appearently, this has been fixed trunk, but for a 2.9.1 release, this could 
 be helpful.
 The patch can be applied against the 2.9.0 tag.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Created: (LUCENE-1954) InitiatedIndex: CCE on casting NumericField to Field

2009-10-07 Thread Bernd Fondermann (JIRA)
InitiatedIndex: CCE on casting NumericField to Field


 Key: LUCENE-1954
 URL: https://issues.apache.org/jira/browse/LUCENE-1954
 Project: Lucene - Java
  Issue Type: Bug
  Components: contrib/*
Affects Versions: 2.9
Reporter: Bernd Fondermann
Priority: Minor
 Attachments: instantiated_writer_fieldable.patch

An unchecked cast to ListField throws a ClassCastException when applied to, 
for example, a NumericField.
Appearently, this has been fixed trunk, but for a 2.9.1 release, this could be 
helpful.
The patch can be applied against the 2.9.0 tag.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Created: (LUCENE-1920) Make MultiReader.isOptimized() return a useful result

2009-09-18 Thread Bernd Fondermann (JIRA)
Make MultiReader.isOptimized() return a useful result
-

 Key: LUCENE-1920
 URL: https://issues.apache.org/jira/browse/LUCENE-1920
 Project: Lucene - Java
  Issue Type: Improvement
  Components: Index
Reporter: Bernd Fondermann
Priority: Minor


The MultiReader statically returns FALSE on any isOptimized() call.
This makes it unusable as the source index for an InstantiatedIndex, which 
checks initially if the source index is optimized and aborts if not.
The attached patch iterates all sub readers and returns TRUE if all of them are 
optimized.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Updated: (LUCENE-1920) Make MultiReader.isOptimized() return a useful result

2009-09-18 Thread Bernd Fondermann (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Fondermann updated LUCENE-1920:
-

Attachment: MultiReader_isOptimized.patch

 Make MultiReader.isOptimized() return a useful result
 -

 Key: LUCENE-1920
 URL: https://issues.apache.org/jira/browse/LUCENE-1920
 Project: Lucene - Java
  Issue Type: Improvement
  Components: Index
Reporter: Bernd Fondermann
Priority: Minor
 Attachments: MultiReader_isOptimized.patch


 The MultiReader statically returns FALSE on any isOptimized() call.
 This makes it unusable as the source index for an InstantiatedIndex, which 
 checks initially if the source index is optimized and aborts if not.
 The attached patch iterates all sub readers and returns TRUE if all of them 
 are optimized.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Commented: (LUCENE-1920) Make MultiReader.isOptimized() return a useful result

2009-09-18 Thread Bernd Fondermann (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12757377#action_12757377
 ] 

Bernd Fondermann commented on LUCENE-1920:
--

Thank you all for taking the time to review the patch.
I'm not that familiar with the inner workings of Lucene and the full (intented) 
contract of isOptimized().

Just a few observations I made by looking at Lucene's source more closely:

+ My patch was originally crafted and tested against 2.4.0-RELEASE.
However, InstantiatedIndex in TRUNK no longer throws an exception on 
non-optimized wrapped indizes, see LUCENE-1578. 
So this no longer should be a problem (although I don't know if this is tested 
well enough) and the patch can be looked at conservatively.

+ Nevertheless, I think it's releasonable (from a user's perspecitve) to expect 
a behavior like the patch is providing.

+ This is supported by ParallelReader.isOptimized() (see LUCENE-832), which is 
doing essentially the same thing like the proposed patch for MultiReader.
 So this behavior is already implemented in a similar Reader.



 Make MultiReader.isOptimized() return a useful result
 -

 Key: LUCENE-1920
 URL: https://issues.apache.org/jira/browse/LUCENE-1920
 Project: Lucene - Java
  Issue Type: Improvement
  Components: Index
Reporter: Bernd Fondermann
Priority: Minor
 Attachments: MultiReader_isOptimized.patch


 The MultiReader statically returns FALSE on any isOptimized() call.
 This makes it unusable as the source index for an InstantiatedIndex, which 
 checks initially if the source index is optimized and aborts if not.
 The attached patch iterates all sub readers and returns TRUE if all of them 
 are optimized.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Created: (LUCENE-1886) Improve Javadoc

2009-09-02 Thread Bernd Fondermann (JIRA)
Improve Javadoc
---

 Key: LUCENE-1886
 URL: https://issues.apache.org/jira/browse/LUCENE-1886
 Project: Lucene - Java
  Issue Type: Improvement
  Components: Analysis
Reporter: Bernd Fondermann




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Updated: (LUCENE-1886) Improve Javadoc

2009-09-02 Thread Bernd Fondermann (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Fondermann updated LUCENE-1886:
-

Attachment: javadoc.patch

 Improve Javadoc
 ---

 Key: LUCENE-1886
 URL: https://issues.apache.org/jira/browse/LUCENE-1886
 Project: Lucene - Java
  Issue Type: Improvement
  Components: Analysis
Reporter: Bernd Fondermann
 Attachments: javadoc.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Created: (LUCENE-1803) Wrong javadoc on LowerCaseTokenizer.normalize

2009-08-12 Thread Bernd Fondermann (JIRA)
Wrong javadoc on LowerCaseTokenizer.normalize
-

 Key: LUCENE-1803
 URL: https://issues.apache.org/jira/browse/LUCENE-1803
 Project: Lucene - Java
  Issue Type: Bug
  Components: Javadocs
Reporter: Bernd Fondermann
 Attachments: LowerCaseTokenizer_javadoc.patch

The javadoc on LowerCaseTokenizer.normalize seems to be copy/paste from 
LetterTokenizer.isTokenChar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Updated: (LUCENE-1803) Wrong javadoc on LowerCaseTokenizer.normalize

2009-08-12 Thread Bernd Fondermann (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Fondermann updated LUCENE-1803:
-

Attachment: LowerCaseTokenizer_javadoc.patch

 Wrong javadoc on LowerCaseTokenizer.normalize
 -

 Key: LUCENE-1803
 URL: https://issues.apache.org/jira/browse/LUCENE-1803
 Project: Lucene - Java
  Issue Type: Bug
  Components: Javadocs
Reporter: Bernd Fondermann
 Attachments: LowerCaseTokenizer_javadoc.patch


 The javadoc on LowerCaseTokenizer.normalize seems to be copy/paste from 
 LetterTokenizer.isTokenChar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Created: (LUCENE-1740) Lucli: Command to change the Analyzer

2009-07-10 Thread Bernd Fondermann (JIRA)
Lucli: Command to change the Analyzer
-

 Key: LUCENE-1740
 URL: https://issues.apache.org/jira/browse/LUCENE-1740
 Project: Lucene - Java
  Issue Type: New Feature
  Components: contrib/*
Affects Versions: 2.9
Reporter: Bernd Fondermann
 Fix For: 2.9


Currently, Lucli is hardcoded to use StandardAnalyzer. The provided patch 
introduces a command analyzer to specify a different Analyzer class. 
If something fails, StandardAnalyzer is the fall-back.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Updated: (LUCENE-1740) Lucli: Command to change the Analyzer

2009-07-10 Thread Bernd Fondermann (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Fondermann updated LUCENE-1740:
-

Attachment: analyzer_command.patch

Patch adding 'analyzer' command

 Lucli: Command to change the Analyzer
 -

 Key: LUCENE-1740
 URL: https://issues.apache.org/jira/browse/LUCENE-1740
 Project: Lucene - Java
  Issue Type: New Feature
  Components: contrib/*
Affects Versions: 2.9
Reporter: Bernd Fondermann
 Fix For: 2.9

 Attachments: analyzer_command.patch


 Currently, Lucli is hardcoded to use StandardAnalyzer. The provided patch 
 introduces a command analyzer to specify a different Analyzer class. 
 If something fails, StandardAnalyzer is the fall-back.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Created: (LUCENE-1633) Copy/Paste-Typo in toString() for SpanQueryFilter

2009-05-12 Thread Bernd Fondermann (JIRA)
Copy/Paste-Typo in toString() for SpanQueryFilter
-

 Key: LUCENE-1633
 URL: https://issues.apache.org/jira/browse/LUCENE-1633
 Project: Lucene - Java
  Issue Type: Bug
Reporter: Bernd Fondermann
Priority: Trivial


   public String toString() {
-return QueryWrapperFilter( + query + );
+return SpanQueryFilter( + query + );
   }

says it all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Updated: (LUCENE-1633) Copy/Paste-Typo in toString() for SpanQueryFilter

2009-05-12 Thread Bernd Fondermann (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Fondermann updated LUCENE-1633:
-

Attachment: fix_SpanQueryFilter_toString.patch

 Copy/Paste-Typo in toString() for SpanQueryFilter
 -

 Key: LUCENE-1633
 URL: https://issues.apache.org/jira/browse/LUCENE-1633
 Project: Lucene - Java
  Issue Type: Bug
Reporter: Bernd Fondermann
Priority: Trivial
 Attachments: fix_SpanQueryFilter_toString.patch


public String toString() {
 -return QueryWrapperFilter( + query + );
 +return SpanQueryFilter( + query + );
}
 says it all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org