You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Trejkaz (JIRA)" <ji...@apache.org> on 2017/05/31 05:03:04 UTC
[jira] [Commented] (LUCENE-6917) Deprecate and rename
NumericField/RangeQuery to LegacyNumeric
[ https://issues.apache.org/jira/browse/LUCENE-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030636#comment-16030636 ]
Trejkaz commented on LUCENE-6917:
---------------------------------
Did this ever hit the dev list? Google can't seem to find it. I'm wondering if a fix was ever found. Not because I'm seeing it when building Lucene - but because I'm seeing the same error when trying to build our own stuff. And clean does seem to stop it sometimes, but for some people it doesn't, so I'm trying to figure out whether anyone knows the actual cause. It's a bit of a vague error message.
> Deprecate and rename NumericField/RangeQuery to LegacyNumeric
> -------------------------------------------------------------
>
> Key: LUCENE-6917
> URL: https://issues.apache.org/jira/browse/LUCENE-6917
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 6.0
>
> Attachments: LUCENE-6917-broken-javadocs.patch, LUCENE-6917.patch, LUCENE-6917.patch, LUCENE-6917.patch
>
>
> DimensionalValues seems to be better across the board (indexing time, indexing size, search-speed, search-time heap required) than NumericField, at least in my testing so far.
> I think for 6.0 we should move {{IntField}}, {{LongField}}, {{FloatField}}, {{DoubleField}} and {{NumericRangeQuery}} to {{backward-codecs}}, and rename with {{Legacy}} prefix?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org