Text-based search interface returns empty response for specific hits

Support Bug
1

The response body is really empty, as opposed to a JSON response indicating that there are no search results.
As a side effect, the web UI throws a TypeError, as it expected a valid response, such as {"term":"blah","results":[]}.

stardog-text-search-error
stardog-text-search-error.png778×200 21.5 KB

The hits (should) exist, but they contain accented characters (e.g. õáè).

2

Hi,

Can you try using the command line? What kind of behaviour are you seeing there?
Is there any error in stardog.log?

-pedro

3

This is Stardog Community 5.0.1.

4

Hi Pedro,

The following both work, for a literal with funky characters (e.g. “Blah Blõáèh”):

./stardog query search -q “Blah” meta

SELECT DISTINCT ?s ?p ?l ?score
WHERE {
?s ?p ?l.
(?l ?score) tag:stardog:api:property:textMatch (‘Blah’ 100).
}

There is no trace in the logs when the search fails.

It’s the other search interface /annex/[db]/search, which fails as described.

Cheers,
Dann

5

Hi Dann,

I can’t replicate this behaviour. Can you try updating to the latest version of Stardog (5.0.5.1)? If the problem still persists, can you share some data and queries so I can try to replicate the problem locally?

Thanks,
-pedro

6

Hi Pedro,

Sorry for the delay: I just upgraded to 5.1.0 and the issue is gone.

Cheers,
Dann

1 Like