[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621036#action_12621036
]
Eks Dev commented on LUCENE-1219:
---------------------------------
bq. could we instead add this to Field:
byte[] binaryValue(byte[] result)
this is exactly where I started, but then realized I am missing actual length
we read in LazyField, without it you would have to relocate each time, except
in case where your buffer length equals toRead in LazyField... simply, the
question is, how the caller of byte[] getBinaryValue(String name, byte[]
result) could know what is the length in this returned byte[]
Am I missing something obvious?
> 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: Improvement
> Components: Index
> Reporter: Eks Dev
> Assignee: Michael McCandless
> Priority: Minor
> Attachments: LUCENE-1219.extended.patch, LUCENE-1219.patch,
> LUCENE-1219.patch, LUCENE-1219.patch, LUCENE-1219.patch,
> LUCENE-1219.take2.patch, LUCENE-1219.take3.patch
>
>
> currently Field/Fieldable interface supports only compact, zero based byte
> arrays. This forces end users to create and copy content of new objects
> before passing them to Lucene as such fields are often of variable size.
> Depending on use case, this can bring far from negligible performance
> improvement.
> this approach extends Fieldable interface with 3 new methods
> getOffset(); gettLenght(); and getBinaryValue() (this only returns reference
> to the array)
>
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
