Lucene4 Plug-in (deprecated)

compared with
Version 8 by reneta.popova
on Sep 18, 2014 15:07.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
* {code}urn\\:join:joinValue{code} is a query in the form field:value. However, since the field name contains {{:}}, we need to escape it with backslash. The backslash, however is also an escaping character in SPARQL, and therefore we need to escape it again so that the plugin will see a single backslash. Forward slashes are also special Lucene syntax and need to be escaped as well.
This means that if the join predicate is {nolink}http://example.com/slash{nolink}, the proper query would be "+(query) +http\\:\/\/example.com\/slash:joinValue".
* also note that whatever the original FTS query is, the best is to put it in brackets, with plus in front. If you ask for "query +urn\\:join:joinValue" then Lucene will return all entities that match either _query_ OR _urn\\:join:joinValue_ which is not the intent.
{code}"query +urn\\:join:joinValue"{code} then Lucene will return all entities that match either _query_ OR _
{code}urn\\:join:joinValue{code} which is not the intent.

h5. Optional joins