[
https://issues.apache.org/jira/browse/SOLR-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051526#comment-17051526
]
Cassandra Targett edited comment on SOLR-11746 at 3/4/20, 6:54 PM:
-------------------------------------------------------------------
bq. This reminded me that I neglected to update the Ref Guide README
Scratch that, I did update it. I was looking at an old branch.
However, if you previously had all the pre-reqs already installed and upgraded
to the versions mentioned in the README, it would not update the asciidoctor
version [1]. To upgrade Asciidoctor, use:
{code}
gem upgrade asciidoctor
{code}
[1] The reason for this is because the asciidoctor gem is a dependency of
jekyll-asciidoc so new installs of the pre-reqs get asciidoctor as part of the
install of jekyll-asciidoc. When you upgrade jekyll-asciidoc, however, it does
not automatically update it's dependency, it only validates that it is already
installed.
Edit: Or, you could use the gradle build: {{./gradlew buildSite}} which
downloads the dependencies even if you have them already.
was (Author: ctargett):
bq. This reminded me that I neglected to update the Ref Guide README
Scratch that, I did update it. I was looking at an old branch.
However, if you previously had all the pre-reqs already installed and upgraded
to the versions mentioned in the README, it would not update the asciidoctor
version [1]. To upgrade Asciidoctor, use:
{code}
gem upgrade asciidoctor
{code}
[1] The reason for this is because the asciidoctor gem is a dependency of
jekyll-asciidoc so new installs of the pre-reqs get asciidoctor as part of the
install of jekyll-asciidoc. When you upgrade jekyll-asciidoc, however, it does
not automatically update it's dependency, it only validates that it is already
installed.
> 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
