Hi,
I am using Solr-6.4.2, did a query (*title*:("to order this report"~*0*))
on "*text_en*" field and matched ("title":"Forrester Research cites SAP
Hybris as a leader in B2B Order Management report").
As per my understanding, this could not match as there is a word "Management"
between "Order'
Joel,
Should I create a JIRA for making shortestPath return stream of tuples?
On Sun, Jan 14, 2018 at 11:52 PM, Karthik Ramachandran
wrote:
> Joel,
> Thanks, I did try using cartesianProduct then fetch, it is working as
> excepted. For my dataset has only 5 or 6 level for that shortestPath
>
Joel,
Thanks, I did try using cartesianProduct then fetch, it is working as
excepted. For my dataset has only 5 or 6 level for that shortestPath
response time is ~5 sec and with cartesianProduct and fetch I am getting
~6.5 sec. Is there any other way to achieve this?
For my use case graph query
Actually I think you can achieve what you're looking for by using the
cartesianProduct expression around the shortest expression. The construct
would look like this:
fetch(cartesianProduct(shortesPath()))
The link below describes how the cartesianProduct expression works:
https://lucene.apache.or
The shortestPath returns a list of node id's, and fetch expects a stream of
tuples. So they are not compatible currently. It think makes sense to
change shortestPath to return a stream of tuples so it can work with fetch
and other expressions.
Are you getting good performance with the shortestPath
Hi,
I have some data in WKT string format (either POLYGON or MULTIPOLYGON) and I’d
like to index it in Solr 7.0. As there are multiple polygons in every WKT
string, I’d ideally like to index them multiValued BBoxField (couldn’t find
anywhere to confirm, but it looks like multiValued is a valid
Can shortestPath stream source be used with fetch?
With below streaming expression, we only get the path, are we doing
something wrong here?
fetch(collection,
shortestPath(collection, from="10", to="1", edge="id=parentid",
maxDepth="10"),
fl="id, name, other, details",
sort="nam
I started to use timeAllowed parameter in SOLR-6.5.1. And got too many (each
second) exceptions
null:java.lang.NullPointerException
at
org.apache.lucene.search.TimeLimitingCollector.needScores(TimeLimitingCollector.java:166)
caused to perfomance problems.
For reproducing exception need group=tr