Shawn,
That just did it. I didn't realize that I hadn't specified the uniqueKey in the
schema.xml; Once I did it, its working now. Thanks for the pointers.!!
On Jun 3, 2013, at 4:23 PM, Shawn Heisey wrote:
> On 6/3/2013 1:58 PM, PeriS wrote:
>> You got the point; I do have a the unique key de
On 6/3/2013 1:58 PM, PeriS wrote:
You got the point; I do have a the unique key defined, but for some reason,
when i run the delta-import; a new entry is created for the same record with a
new unique key. Its almost somehow it doesn't detect the existing record.
If the new document has a diff
Shawn,
You got the point; I do have a the unique key defined, but for some reason,
when i run the delta-import; a new entry is created for the same record with a
new unique key. Its almost somehow it doesn't detect the existing record.
On Jun 3, 2013, at 3:51 PM, Shawn Heisey wrote:
> On 6/3
On 6/3/2013 12:35 PM, PeriS wrote:
I noticed the delta-import is creating a new indexed entry on top of the
existing one..is that normal?
Not sure what you are asking here, so I'll give an answer to the
question I think you're asking: If you have a uniqueKey defined in your
schema, then new
I noticed the delta-import is creating a new indexed entry on top of the
existing one..is that normal?
On Jun 2, 2013, at 10:31 PM, Lance Norskog wrote:
> Let's assume that the Solr record includes the database record's timestamp
> field.You can make a more complex DIH stack that does a Solr
Let's assume that the Solr record includes the database record's
timestamp field.You can make a more complex DIH stack that does a Solr
query with the SolrEntityProcessor. You can do a query that gets the
most recent timestamp in the index, and then use that in the DB update
command.
On 06/02
