n.
>
> 2> If we _don’t_ delete the configset, then you can wind up with
> obsolete configsets polluting Zookeeper…
>
> 3> If we make a copy of the configset every time we make a collection,
> then there can be a bazillion of them in a large installation.
>
>
ke
> sure I’ve uploaded the correct file to the correct place.
>
> I use the "bin/solr zk upconfig” command to move files back and forth
> FWIW, that
> avoids, say putting the individual file a in the wrong directory...
>
> Best,
> Erick
>
> > On Dec 4, 2020, at 9:
Hi,
When trying to modify the config.xml file for a collection I made a mistake
and the config was wrong. So I removed the collection to create it again
from a backend.
But, although I'm sure I'm using a correct config.xml, solr is still
complaining about the error in the older solrconfig.xml
I h
g "&debug=query" to the search and looking at the result
> parsed_query.toString() will show you what’s actually the result of the
> query parsing and may help.
>
> Best,
> Erick
>
> > On Mar 4, 2019, at 3:13 AM, Marisol Redondo <
> marisol.redondo.gar...@gm
s
[65 6d 70 6c 6f 69]
[63 61 72 65 72]
start
0
12
start
0
12
end
9
17
end
9
17
positionLength
1
1
positionLength
1
1
type
type
position
1
3
position
1
3
keyword
FALSE
FALSE
keyword
FALSE
FALSE
On Fri, 1 Mar 2019 at 15:51, Shawn Heisey wrote:
Hi.
When using the PorterStemFilter, I saw that the work "employing" is change
to "emploi" and my document is not found in the query to solr because of
that.
This also happens with other words that finish in -ying as annoying or
deploying.
It there any path for this filter or should I create a n
