Re: Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

The simplest test to see if there are duplicates is to check the maxDoc and numDocs in the admin UI. If they're different then you have duplicates. NOTE: this is not definitive, and you MUST NOT run optimize before you look. But it's quick. I'd delete all docs before trying this first though. Seco

Re:Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

hi guys, thank you very much for the help. sorry been so lated to reply. 1. "commit" didn't help. after commit, the 'numFound' of "*:*" query is still the same. 2. "id" field in every doc is generated by solr using UUID, i have idea how to check if there is a duplicated one. but i ass

Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

Both of us implied it, but to be completely clear - if you have a duplicate ID in your data set, SOLR will throw away previous documents with that ID and index the new one. That's fine if your duplicates really are duplicates - it's not OK if there's a problem in the data set and the duplicates ID

Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

Sweet - that's a good point - I ran into that too - I had not run the commit for the last "batch" (I was using SolrJ) and so numbers didn't match until I did. On Mon, Apr 4, 2016 at 9:50 PM, Binoy Dalal wrote: > 1) Are you sure you don't have duplicates? > 2) All of your records might have been

Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

The first question is whether you have duplicate ID's in your data set. I had the same kind of thing a few months back, freaked out, and spent a few hours trying to figure it out by coding extra logging etc... to keep track of every single count at every stage of the process.. All the numbers mat

Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

1) Are you sure you don't have duplicates? 2) All of your records might have been indexed but a new searcher may not have opened on the updated index yet. Try issuing a commit and see if that works. On Tue, 5 Apr 2016, 08:56 cqlangyi, wrote: > hi there, > > > i have an solr 5.2.1, when i do dat

solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

hi there, i have an solr 5.2.1, when i do data import, after the job is done, it's shown 165,191 rows processed successfully. but when i query with *:*, the "numFound" shown only 163,349 docs in index. when i tred to do it again, , it's shown 165,191 rows processed successfully. but the *:

Re: Mysql data import issue

to achieve that? Thanks, Sriram -- View this message in context: http://lucene.472066.n3.nabble.com/Mysql-data-import-issue-tp4253998p4254210.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Mysql data import issue

On 29 January 2016 at 04:13, vsriram30 wrote: > Hi, > I am using Solr 4.6.1 and I am trying to import my data from mysql to solr. > > In mysql, I have a table with columns, > id, legacyid, otherfields... > [...] > But still I get mysql id field to solr id field mapping. Please let me know > how

Mysql data import issue

olr id field mapping. Please let me know how to prevent this from happening. Thanks, Sriram -- View this message in context: http://lucene.472066.n3.nabble.com/Mysql-data-import-issue-tp4253998.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Data import issue

Do you have a full stack trace? A bit hard to help without that. On 24 Dec 2015 2:54 pm, "Midas A" wrote: > Hi , > > > Please provide the steps to resolve the issue. > > > com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: > Communications link failure during rollback(). Transa

Data import issue

Hi , Please provide the steps to resolve the issue. com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Communications link failure during rollback(). Transaction resolution unknown.