Re: Sql server data import

2018-11-09 Thread Erick Erickson
Ok, what that means is you're letting Solr do its best to figure out what fields you should have in the schema and how they're defined. Almost invariably, you can do better by explicitly defining the fields you need in your schema rather than enabling add-unknown. It's fine for getting started,

Re: Sql server data import

2018-11-09 Thread Verthosa
Hello, i managed to fix the problem. I'm using Solr 7.5.0. My problem was that in the server logs i got "This Indexschema is not mutable" (i did not know about the logs folder, so i just found out 5 minutes ago). I fixed it by modifying solrconfig.xml to false*}" proce

RE: Sql server data import

2018-11-09 Thread Gu, Steve (CDC/DDPHSS/OS) (CTR)
What is "​" in the PublicId? Is it part of the data? Did you check if the special characters in your data cause the problem? Steve ### Error creating document : SolrInputDocument(fields: [PublicId=10065,​ Id=117]) -Original Message- From: Verthosa Sent: Friday, November 9,

Re: Sql server data import

2018-11-09 Thread Alexandre Rafalovitch
Which version of Solr is it? Because we have not used schema.xml for a very long time. It has been managed-schema instead. Also, have you tried using DIH example that uses database and modifying it just enough to read data from your database. Even if it has a lot of extra junk, this would test hal