[ https://issues.apache.org/jira/browse/LUCENE-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481102#comment-14481102 ]
Michael McCandless commented on LUCENE-5989: -------------------------------------------- I think now that LUCENE-5879 is in, as a dark/unusable feature, we should add BinaryField (this issue) to at least shed a bit of light on it. With BinaryField, apps can efficiently prefix and range search anything they can convert to/from byte[], e.g. BigInteger/Decimal, InetAddress (LUCENE-5596), int/long/float/double, etc. On the LUCENE-6005 branch there is also a half-precision float (2 bytes). I don't think Lucene's lack of schema is a justifiable reason to block progress here. > Add BinaryField, to index a single binary token > ----------------------------------------------- > > Key: LUCENE-5989 > URL: https://issues.apache.org/jira/browse/LUCENE-5989 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Michael McCandless > Assignee: Michael McCandless > Fix For: 5.0, Trunk > > Attachments: LUCENE-5989.patch > > > 5 years ago (LUCENE-1458) we "enabled" fully binary terms in the > lowest levels of Lucene (the codec APIs) yet today, actually adding an > arbitrary byte[] binary term during indexing is far from simple: you > must make a custom Field with a custom TokenStream and a custom > TermToBytesRefAttribute, as far as I know. > This is supremely expert, I wonder if anyone out there has succeeded > in doing so? > I think we should make indexing a single byte[] as simple as indexing > a single String. > This is a pre-cursor for issues like LUCENE-5596 (encoding IPv6 > address as byte[16]) and LUCENE-5879 (encoding native numeric values > in their simple binary form). -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org