Hi,
I checked that and collection data will be erased only when I will use
clean=true and optimize=true (first query).
1. clean=true ; optimize=true
webapp=/solr path=/dataimport
params={core=example_collection&optimize=true&indent=on&commit=true&name=dataimport&clean=true&wt=json&command=full-import&_=1657098443936&verbose=true}
status=0 QTime=5
2. clean=true
webapp=/solr path=/dataimport
params={core=example_collection&indent=on&commit=true&name=dataimport&clean=true&wt=json&command=full-import&_=1657098443936&verbose=true}
status=0 QTime=4
3. clean=false ; optimize=true
webapp=/solr path=/dataimport
params={core=example_collection&optimize=true&indent=on&commit=true&name=dataimport&clean=false&wt=json&command=full-import&_=1657098443936&verbose=true}
status=0 QTime=5
Does this should work like that? I know that in Solr 7.1 that situation
never happened.
Best Regards,
Michal
On 7/4/22 14:23, Mikhail Khludnev wrote:
Hello, Michal.
I don't think so. I'd rather bark on clean=true. I suppose you can find a
detailed answer in the log.
On Mon, Jul 4, 2022 at 2:51 PM Michał Świątkowski
<[email protected]> wrote:
Hello All,
I'm using Solr-8.11.1 in cloud mode with OpenJDK8. From Solr-8 I noticed
that full-update with option 'optimize' (e.g.
/dataimport?command=full-import&clean=true&commit=true&wt=json&*optimize=true*)
removes all collection data and during the update collection is empty.
Does anyone know is this is a bug or new feature?
Thanks,
Michal
