Identical TotalResults Cache Key for different queries

[margaretha]

Identical TotalResults Cache Key for different queries have cause the problem described in KorAP/Kalamar#218

Kustvakt uses query hash-codes as cache keys. It turns out that the following queries get the same hash-code:

Response response = target().path(API_VERSION).path("search")
                .queryParam("q", "[orth=populistischer]")
                .queryParam("ql", "poliqarp")
                .queryParam("cq", "availability!=QAO-NC-LOC:ids & corpusSigle = "
                        + "/SOL|[UTSZ][0-9][0-9]/ & pubDate in 1976")
                .queryParam("fields", "corpusSigle,textSigle,pubDate,pubPlace,"
                        + "availability,textClass")
                .queryParam("access-rewrite-disabled", "true").request().get();

Response response = target().path(API_VERSION).path("search")
                .queryParam("q", "[orth=populistisches]")
                .queryParam("ql", "poliqarp")
                .queryParam("cq", "availability!=QAO-NC-LOC:ids & corpusSigle = "
                        + "/SOL|[UTSZ][0-9][0-9]/ & pubDate in 1975")
                .queryParam("fields", "corpusSigle,textSigle,pubDate,pubPlace,"
                        + "availability,textClass")
                .queryParam("access-rewrite-disabled", "true").request().get();

[margaretha]

I didn't expect that Java would create the same hash-code for different queries. That happens appearently because Java hash-code method considers object structures rather than content so it misses small differences like populistischer v.s populistisches, and 1976 v.s 1975.

I have redeployed the test instance with a fix. It should create different keys now.