Re: Delete IDs with JDBC connector

Oh yes indeed, never mind, I missed that point. So all is ok Thanks Karl Le 27.04.2017 13:28, Karl Wright a écrit : > Hi Julien, > > The JDBC connector uses MODEL_ADD_CHANGE. The requirement for > MODEL_ADD_CHANGE is that seeding includes all documents between the time > ranges specified

Re: Delete IDs with JDBC connector

Hi Karl, yes your fix works. However, doesn't it break the logic of the delta feature provided by the seeding query that makes good use of the $(STARTTIME) and $(ENDTIME) variables ? For example, let assume that the docs in my database have a timestamp that indicates their last modification

Re: Delete IDs with JDBC connector

I committed a fix to trunk, and also uploaded a patch to the ticket. Please let me know if it works for you. Thanks, Karl On Wed, Apr 26, 2017 at 11:24 AM, wrote: > Oh OK so I finally don't have to investigate :) > > Thanks Karl ! > > Julien > > Le 26.04.2017

Re: Delete IDs with JDBC connector

Oh OK so I finally don't have to investigate :) Thanks Karl ! Julien Le 26.04.2017 17:20, Karl Wright a écrit : > Oh, never mind. I see the issue, which is that without the version query, > documents that don't appear in the result list *at all* are never removed > from the map. I'll

Re: Delete IDs with JDBC connector

CONNECTORS-1419. Karl On Wed, Apr 26, 2017 at 11:20 AM, Karl Wright wrote: > Oh, never mind. I see the issue, which is that without the version query, > documents that don't appear in the result list *at all* are never removed > from the map. I'll create a ticket. > > Karl

Re: Delete IDs with JDBC connector

Oh, never mind. I see the issue, which is that without the version query, documents that don't appear in the result list *at all* are never removed from the map. I'll create a ticket. Karl On Wed, Apr 26, 2017 at 11:10 AM, Karl Wright wrote: > Hi Julien, > > The delete

Re: Delete IDs with JDBC connector

Hi Julien, The delete logic in the connector is as follows: >> // Now, go through the original id's, and see which ones are still in the map. These // did not appear in the result and are presumed to be gone from the database, and thus must be deleted. for (String

Re: Delete IDs with JDBC connector

Hi Julien, How are you starting the job? If you use "Start minimal", deletion would not take place. If your job is a continuous one, this is also the case. Thanks, Karl On Wed, Apr 26, 2017 at 9:52 AM, wrote: > Hi the MCF community, > > I am using MCF 2.6

Delete IDs with JDBC connector

Hi the MCF community, I am using MCF 2.6 with the JDBC connector to crawl an Oracle Database and index the data into a Solr server, and it works very well. However, when I perform a delta re-crawl, the new IDs are correctly retrieved from the Database but those who have been deleted are not