lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11450) ComplexPhraseQParserPlugin not running charfilter for some multiterm queries in 6.x
Date Fri, 13 Oct 2017 13:41:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-11450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203573#comment-16203573
] 

Tim Allison commented on SOLR-11450:
------------------------------------

[~jpountz], thank you for your response!

Y, the changes in 7.x are fantastic.

Am I misunderstanding 6.x, though?  This test passes, which suggests that normalization was
working correctly for the classic queryparser in 6.x, but not the cpqp.  Or am I misunderstanding?

If your point is that this would be a breaking change for some users of cpqp and it therefore
doesn't belong in a bugfix release, I'm willing to accept that.

{noformat}
  @Test
  public void testCharFilter() {
    assertU(adoc("iso-latin1", "craezy traen", "id", "1"));
    assertU(commit());
    assertU(optimize());

    assertQ(req("q",  "iso-latin1:cr\u00E6zy")
            , "//result[@numFound='1']"
            , "//doc[./str[@name='id']='1']"
    );

    assertQ(req("q", "iso-latin1:tr\u00E6n")
            , "//result[@numFound='1']"
            , "//doc[./str[@name='id']='1']"
    );

    assertQ(req("q", "iso-latin1:c\u00E6zy~1")
            , "//result[@numFound='1']"
            , "//doc[./str[@name='id']='1']"
    );

    assertQ(req("q", "iso-latin1:cr\u00E6z*")
            , "//result[@numFound='1']"
            , "//doc[./str[@name='id']='1']"
    );

    assertQ(req("q", "iso-latin1:*\u00E6zy")
            , "//result[@numFound='1']"
            , "//doc[./str[@name='id']='1']"
    );

    assertQ(req("q", "iso-latin1:cr\u00E6*y")
            , "//result[@numFound='1']"
            , "//doc[./str[@name='id']='1']"
    );

    assertQ(req("q", "iso-latin1:/cr\u00E6[a-z]y/")
        , "//result[@numFound='1']"
        , "//doc[./str[@name='id']='1']"
    );

    assertQ(req("q", "iso-latin1:[cr\u00E6zx TO cr\u00E6zz]")
        , "//result[@numFound='1']"
        , "//doc[./str[@name='id']='1']"
    );
}
{noformat}

> ComplexPhraseQParserPlugin not running charfilter for some multiterm queries in 6.x 
> ------------------------------------------------------------------------------------
>
>                 Key: SOLR-11450
>                 URL: https://issues.apache.org/jira/browse/SOLR-11450
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.6.1
>            Reporter: Tim Allison
>            Priority: Minor
>              Labels: patch-with-test
>         Attachments: SOLR-11450-unit-test.patch, SOLR-11450.patch
>
>
> On the user list, [~bjarkebm] reported that the charfilter is not being applied in PrefixQueries
in the ComplexPhraseQParserPlugin in 6.x.  Bjarke fixed my proposed unit tests to prove this
failure. All appears to work in 7.x and trunk. If there are plans to release a 6.6.2, let's
fold this in.



--
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


Mime
View raw message