[
https://issues.apache.org/jira/browse/SOLR-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049991#comment-17049991
]
Tomoko Uchida commented on SOLR-11746:
--------------------------------------
I did clean checkout from the Apache repo, and saw the build still doesn't work
for me.
{code}
git clone g...@github.com:apache/lucene-solr.git
cd lucene-solr/
ant -f solr/solr-ref-guide/build.xml build-site
...
build-site:
[java] Relative link points at id that doesn't exist in dest:
the-standard-query-parser.html#differences-between-lucenes-classic-query-parser-and-solrs-standard-query-parser
[java] ... source:
file:/mnt/hdd/tmp/lucene-solr/solr/build/solr-ref-guide/html-site/common-query-parameters.html
[java] Relative link points at id that doesn't exist in dest:
#differences-between-lucenes-classic-query-parser-and-solrs-standard-query-parser
[java] ... source:
file:/mnt/hdd/tmp/lucene-solr/solr/build/solr-ref-guide/html-site/the-standard-query-parser.html
[java] Processed 2610 links (1930 relative) to 3728 anchors in 262 files
[java] Total of 2 problems found
BUILD FAILED
{code}
I have not looked at the details yet, but the problem could occur only for me
(caused by my setups?).
> numeric fields need better error handling for prefix/wildcard syntax --
> consider uniform support for "foo:* == foo:[* TO *]"
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-11746
> URL: https://issues.apache.org/jira/browse/SOLR-11746
> Project: Solr
> Issue Type: Bug
> Affects Versions: 7.0
> Reporter: Chris M. Hostetter
> Assignee: Houston Putman
> Priority: Major
> Fix For: master (9.0), 8.5
>
> Attachments: SOLR-11746.patch, SOLR-11746.patch, SOLR-11746.patch,
> SOLR-11746.patch, SOLR-11746.patch, SOLR-11746.patch, SOLR-11746.patch,
> SOLR-11746.patch, SOLR-11746.patch, SOLR-11746.patch, SOLR-11746.patch
>
>
> On the solr-user mailing list, Torsten Krah pointed out that with Trie
> numeric fields, query syntax such as {{foo_d:\*}} has been functionality
> equivilent to {{foo_d:\[\* TO \*]}} and asked why this was not also supported
> for Point based numeric fields.
> The fact that this type of syntax works (for {{indexed="true"}} Trie fields)
> appears to have been an (untested, undocumented) fluke of Trie fields given
> that they use indexed terms for the (encoded) numeric terms and inherit the
> default implementation of {{FieldType.getPrefixQuery}} which produces a
> prefix query against the {{""}} (empty string) term.
> (Note that this syntax has aparently _*never*_ worked for Trie fields with
> {{indexed="false" docValues="true"}} )
> In general, we should assess the behavior users attempt a prefix/wildcard
> syntax query against numeric fields, as currently the behavior is largely
> non-sensical: prefix/wildcard syntax frequently match no docs w/o any sort
> of error, and the aformentioned {{numeric_field:*}} behaves inconsistently
> between points/trie fields and between indexed/docValued trie fields.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
