Bumping this in case someone that has any idea missed it.
On Wed, Mar 31, 2021 at 11:14 AM Thomas Karampelas
wrote:
> Hi,
>
> I run solr 8.4.1 and I issue the following query on edismax parser:
> *defType=edismax&q=Title:(word1 for word2) &pf=Title&q.op=AND*
>
> The parsed query edismax comes ou
>
> query could be extended to something like Title:(word1 for word2)
> OR Abstract:(word3) which I do not know how to express it via qf
how would you like your pf to work with this?
What is the final query you aim to?
Probably in your case it would be better to fully go "custom" and write
your q
Hi Drini,
I would recommend investigating the code a bit, that token filter is meant
to flat multiple terms at the same position to make it super simple so It
seems suspicious that merging two adjacent tokens putting generated
incorrect positions is what happens.
Have you checked the positionLength
Thanks for the answer Alessandro.
Well, I would expect it to extract the query text from the query (i.e.
extracting it from the field definition) , take the word1 for word2 and add
it add a phrase against the Title field. Essentially
+(
+(
+(+Title:word1 +Title_en:word2)))
(+
Perhaps Solr should come up with a basic auth wrapper requiring a randomly
generated token from the logs as a password printed at the very end of
startup messages. This of course needs to show up in zookeeper too so that
inter-node requests work. Nice if the UI at some point handles it, but as a
te
Hi Jason,
thank you for your reply.
I'm sorry I didn't see it before, I was going to write the same answer
that you posted.
I checked the source code of the Authorization Plugin and the problem
is the distinction between core and collections (in standalone mode
and Solr cloud respectively).
In fact