[
https://issues.apache.org/jira/browse/SOLR-14291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055102#comment-17055102
]
Houston Putman commented on SOLR-14291:
---------------------------------------
Also shouldn't the other parameters predicates be included besides just the end
parameter, they all have the same subtle regex issue.
Also the changed line can likely be modified to be: {{"^(" + END + ")$"}}
instead of {{"^e$|^end$"}}. This could easily be done for the START, HARDEND,
GAP and true predicates.
> OldAnalyticsRequestConverter should support fields names with dots
> ------------------------------------------------------------------
>
> Key: SOLR-14291
> URL: https://issues.apache.org/jira/browse/SOLR-14291
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: search, SearchComponents - other
> Reporter: Anatolii Siuniaev
> Priority: Trivial
> Attachments: SOLR-14291.patch, SOLR-14291.patch
>
>
> If you send a query with range facets using old olap-style syntax (see pdf
> [here|https://issues.apache.org/jira/browse/SOLR-5302]),
> OldAnalyticsRequestConverter just silently (no exception thrown) omits
> parameters like
> {code:java}
> olap.<request>.rangefacet.<field>.start
> {code}
> in case if _<field>_ has dots inside (for instance field name is
> _Project.Value_). And thus no range facets are returned in response.
> Probably the same happens in case of field faceting.
--
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
