In SPARQL I can perform the following query in order to retrieve the fields and the total count in one query result (I know it can be more optimal with a WITH clause where to store the query, but it is not compatible with SPARQL):
Which returns something like this (s fields matched the specific predicate and filter I provided on the query):
+-------+----------------------------------------+| total | s |+-------+----------------------------------------+| 150 | http://the/path/to/the/subject || 150 | http://the/path/to/another/subject || 150 | http://the/path/to/yet/another/subject |+-------+----------------------------------------+
I want to do the same for full text search queries, which can be used as follows ?s bds:search “something” .
However, composing a query with the same structure as the previous one, does not work:
In SPARQL I can perform the following query in order to retrieve the fields and the total count in one query result (I know it can be more optimal with a WITH clause where to store the query, but it is not compatible with SPARQL):
Which returns something like this (s fields matched the specific predicate and filter I provided on the query):
I want to do the same for full text search queries, which can be used as follows
?s bds:search “something” .However, composing a query with the same structure as the previous one, does not work:
Even though, those subqueries return the correct result separately.
I see. It is related to the bug: https://jira.blazegraph.com/browse/BLZG-1198
There is a plan on fixing that?
Last edit: Didac 2017-09-07