You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2017/07/24 18:30:00 UTC
[jira] [Issue Comment Deleted] (SOLR-11093) implement
Points/Numeric support for graph query
[ https://issues.apache.org/jira/browse/SOLR-11093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-11093:
--------------------------------
Comment: was deleted
(was: Requiring DocValues for numerics on a GraphQuery is fine with me. Is there a back-compat concern?
Maybe LongSet could use more javadocs if it's going to be shared. The constructor should actually assert (or throw) that the argument is a power of 2. And it appears that the LongIterator returned *must* be used in a standard fashion in which hasNext is *always* called before next(); yes? Since the set size is known, maybe it could be adjusted to use a countDown integer approach, yet still be very fast/simple?)
> implement Points/Numeric support for graph query
> ------------------------------------------------
>
> Key: SOLR-11093
> URL: https://issues.apache.org/jira/browse/SOLR-11093
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Fix For: 7.0
>
> Attachments: SOLR-11093.patch, SOLR-11093.patch
>
>
> It looks like GraphQueryTest only has tests for strings. We should add tests for numeric fields and then enable points randomization.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org