olr/commit/bf9db95f218f49bac8e7971eb953a9fd9d13a2f0#diff-269ae02e56283ced3ce781cce21b3147R563
sincerely
hongtai
送信元: "Staley, Phil R - DCF"
Reply-To: "d...@lucene.apache.org"
日付: 2020年3月2日 月曜日 22:38
宛先: solr_user lucene_apache ,
"d...@lucene.apache.org"
件名: Re: strange behavior of solr query p
I believe we are experiencing the same thing.
We recently upgraded to our Drupal 8 sites to SOLR 8.3.1. We are now getting
reports of certain patterns of search terms resulting in an error that reads,
“The website encountered an unexpected error. Please try again later.”
Below is a list of
See example/films/README.txt
The “name” field is guessed incorrectly (because the first film has name=“.45”,
so indexing errors once it hits a name value that is no longer numeric. The
README provides a command to define the name field *before* indexing. If
you’ve indexed and had the name fie
Is there any error message in the log when Solr stops indexing the file at
line 2046?
Regards,
Edwin
On 2 September 2015 at 17:17, Long Yan wrote:
> Hey,
> I have created a core with
> bin\solr create -c mycore
>
> I want to index the csv sample files from solr-5.2.1
>
> If I index film.csv und
