rew" can have the important information "1" stripped
> out if I tokenize it.
>
> So what would be a good way to avoid single digit only and single letter
> only queries, from the Solr end?
> Or should I not do this at the Solr end at all?
>
> Could someone p
51, Erick Erickson wrote:
>
> You’re seeing consistent results here because you started with a _new_
> collection that had no old segments lying around.
==
Konstantinos Koukouvis
konstantinos.koukou...@mecenat.com
Using Golang and Sol
bility for use of or reliance on the
> contents of this email by any person save by the intended recipient(s) to the
> extent agreed in a Deloitte LLP engagement contract.
>
> Opinions, conclusions and other information in this email which have not been
> delivered by way of the business of Deloitte LLP are neither given nor
> endorsed by it.
==
Konstantinos Koukouvis
konstantinos.koukou...@mecenat.com
Using Golang and Solr? Try this: https://github.com/mecenat/solr
gt;
> Regards,
> Jayadevan
======
Konstantinos Koukouvis
konstantinos.koukou...@mecenat.com
Using Golang and Solr? Try this: https://github.com/mecenat/solr
>
>
>> On Sep 2, 2020, at 2:21 AM, Konstantinos Koukouvis
>> wrote:
>>
>> Hi everybody, sorry in advance if I’m using the mailing list wrong, this is
>> the first time I’m attempting such a thing.
>>
>> To all you gophers out there we at Mecenat
Hi everybody, sorry in advance if I’m using the mailing list wrong, this is the
first time I’m attempting such a thing.
To all you gophers out there we at Mecenat, have been working at a new solr
client wrapper with focus on single solr instance usage, that supports the
search API, schema API a
