[jira] Created: (LUCENE-509) Performance optimization when retrieving a single field from a document

Performance optimization when retrieving a single field from a document --- Key: LUCENE-509 URL: http://issues.apache.org/jira/browse/LUCENE-509 Project: Lucene - Java Type: Improvement Components:

[jira] Updated: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=all ] Steven Tamm updated LUCENE-509: --- Attachment: DocField.patch Adds Field IndexReader.docField(int doc, String fieldName) which is more efficient than document(doc).getField(fieldName) > Performanc

[jira] Commented: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=comments#action_12368559 ] Doug Cutting commented on LUCENE-509: - This seems like a fine idea. But unless I'm mistaken, there's a bug when fields are strings that contain characters > 127. With st

[jira] Created: (LUCENE-510) IndexOutput.writeString() should write length in bytes

IndexOutput.writeString() should write length in bytes -- Key: LUCENE-510 URL: http://issues.apache.org/jira/browse/LUCENE-510 Project: Lucene - Java Type: Improvement Components: Store Versions: 2.1

[jira] Commented: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=comments#action_12368563 ] Steven Tamm commented on LUCENE-509: Ahh yes. I actually just hit this problem with Japanese... I'll post a fix soon. > Performance optimization when retrieving a singl

[jira] Commented: (LUCENE-446) FunctionQuery - score based on field value

[ http://issues.apache.org/jira/browse/LUCENE-446?page=comments#action_12368570 ] Yonik Seeley commented on LUCENE-446: - This version is now slightly out of date. For now, consider the definitive version to be in Solr: http://incubator.apache.org/solr ht

Re: 1.9 RC1

Hi, I have just updated to lucene 1.9, and hit a problem with the mentioned optimization. I have applied it to the my JdbcBufferedOutput (I only duplicate the code because the BUFFER_SIZE is final), and I hit a problem. In the following code fragment (the method is writeBytes): ...

Re: 1.9 RC1

Shay Banon wrote: ... } else { // is data larger then buffer? if (length > BUFFER_SIZE) { // we flush the buffer if (bufferPosition > 0) flush(); // and write data at once flushBuffer(b, length); } else { ... the bufferStart is not

[jira] Updated: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=all ] Steven Tamm updated LUCENE-509: --- Attachment: DocField_2.patch Now calls readChar() instead of just skipping. > Performance optimization when retrieving a single field from a document > -

[jira] Closed: (LUCENE-323) [PATCH] MultiFieldQueryParser and BooleanQuery do not provide adequate support for queries across multiple fields

[ http://issues.apache.org/jira/browse/LUCENE-323?page=all ] Yonik Seeley closed LUCENE-323: --- Fix Version: 1.9 Resolution: Fixed Assign To: (was: Lucene Developers) OK, closing this bug. We can open separate bugs for any alternate Simil

[jira] Commented: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=comments#action_12368577 ] Doug Cutting commented on LUCENE-509: - That looks good. Thanks. Can you please also add a test case that uses multi-byte characters? Other than that, I'm +1 for comittin

[jira] Commented: (LUCENE-500) Lucene 2.0 requirements - Remove all deprecated code

[ http://issues.apache.org/jira/browse/LUCENE-500?page=comments#action_12368578 ] Daniel Naber commented on LUCENE-500: - DateField should not be removed, as that would mean people cannot easily access date values created with Lucene 1.4. I know the fact

RE: 1.9 RC1

We just discovered this problem as well. Here's a test case that fails without the fix. Index: src/test/org/apache/lucene/index/TestCompoundFile.java === --- src/test/org/apache/lucene/index/TestCompoundFile.java (revision 382277) ++

[jira] Created: (LUCENE-511) New BufferedIndexOutput optimization fails to update bufferStart

New BufferedIndexOutput optimization fails to update bufferStart Key: LUCENE-511 URL: http://issues.apache.org/jira/browse/LUCENE-511 Project: Lucene - Java Type: Bug Components: Store Versions:

[jira] Updated: (LUCENE-511) New BufferedIndexOutput optimization fails to update bufferStart

[ http://issues.apache.org/jira/browse/LUCENE-511?page=all ] Shay Banon updated LUCENE-511: -- Attachment: RAMOutputTest.java > New BufferedIndexOutput optimization fails to update bufferStart >

[jira] Updated: (LUCENE-511) New BufferedIndexOutput optimization fails to update bufferStart

[ http://issues.apache.org/jira/browse/LUCENE-511?page=all ] Shay Banon updated LUCENE-511: -- Attachment: BufferedIndexOutput.java > New BufferedIndexOutput optimization fails to update bufferStart > --

Re: 1.9 RC1

Steven Tamm wrote: We just discovered this problem as well. Here's a test case that fails without the fix. Can you please attach this patch file to: http://issues.apache.org/jira/browse/LUCENE-511 Thanks, Doug - To unsubsc

Re: 1.9 RC1

Filed the bug, https://issues.apache.org/jira/browse/LUCENE-511 . Also added the simple fix, it seems to work, and I think the rest of the method is ok. Shay On 2 Mar 2006, at 19:19, Doug Cutting wrote: Shay Banon wrote: ... } else { // is data larger then buffer? if (le

[jira] Commented: (LUCENE-511) New BufferedIndexOutput optimization fails to update bufferStart

[ http://issues.apache.org/jira/browse/LUCENE-511?page=comments#action_12368584 ] Doug Cutting commented on LUCENE-511: - Can you please package this as a single patch file, generated with 'svn diff' while connected to the Lucene root? Thanks! > New Bu

[jira] Commented: (LUCENE-511) New BufferedIndexOutput optimization fails to update bufferStart

[ http://issues.apache.org/jira/browse/LUCENE-511?page=comments#action_12368585 ] Shay Banon commented on LUCENE-511: --- My lucene root is not as clean as it should be. Don't have time to do that, sorry... . Simple copy and paste the BufferedIndexOutput to

[jira] Commented: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=comments#action_12368587 ] Yonik Seeley commented on LUCENE-509: - It would be nice if one could get just a few fields in an efficient manner too. Off the top of my head, I can't think of a good way t

[jira] Commented: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=comments#action_12368589 ] Yonik Seeley commented on LUCENE-509: - The other limitation of this API is that it only returns a single field value. Of course that's a bonus when you know there is only a

[jira] Commented: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=comments#action_12368590 ] Mark Harwood commented on LUCENE-509: - >It would be nice if one could get just a few fields in an efficient manner >too. I'd like to see that too. I put some code togeth

[jira] Commented: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=comments#action_12368591 ] Doug Cutting commented on LUCENE-509: - You could: (a) add a FieldSelector interface and an IndexWriter method that creates a FieldSelector, then you could pass the FieldS

[jira] Resolved: (LUCENE-511) New BufferedIndexOutput optimization fails to update bufferStart

[ http://issues.apache.org/jira/browse/LUCENE-511?page=all ] Doug Cutting resolved LUCENE-511: - Fix Version: 2.0 1.9 Resolution: Fixed I have committed a patch for this. > New BufferedIndexOutput optimization fails to update b

[jira] Updated: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=all ] Steven Tamm updated LUCENE-509: --- Attachment: DocField_3.patch This includes a UTF-8 test. It fails with the first patch and works with the second. I specifically chose to return only the first

[jira] Updated: (LUCENE-511) New BufferedIndexOutput optimization fails to update bufferStart

[ http://issues.apache.org/jira/browse/LUCENE-511?page=all ] Steven Tamm updated LUCENE-511: --- Attachment: BufferedIndexOutput.patch Here's the files in patch format. > New BufferedIndexOutput optimization fails to update bufferStart >

DO NOT REPLY [Bug 23650] - docs out of order

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

[jira] Updated: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=all ] Steven Tamm updated LUCENE-509: --- Attachment: DocField_4.patch My previous change didn't affect MultiReader, so it was useless for some of our indexes (i.e. it would work but not be efficient) I

[jira] Updated: (LUCENE-509) Performance optimization when retrieving a single field from a document

[ http://issues.apache.org/jira/browse/LUCENE-509?page=all ] Steven Tamm updated LUCENE-509: --- Attachment: DocField_4b.patch Sorry about that. I didn't regenerate the patch after I added the test case. Apologies: this version works. > Performance optimi