context is available for each entity but the implementation just
stores one value for last_index_time.
If it stored the last_index_time per top-level entity it could return
the correct value from context.
Anyway raise an issue and I can provide a patch soon
something like this also shall be suppo
Would that context but available for *each* entity? @ present it
seems like there should be a last_index_time written for each top
level entity ... no?
Umm would it be possible to hack something like ${deltaimporter.[name
of entity].last_index_time} as is or are there too many moving parts
the if an entity is specified like entity=one&entity=two the command
will be run only for those entities. absence of the parameter entity
means all entities will be executed
the last_index_time is another piece which must be improved
It is hard to get usecases . If users can give me more usecase
Actually how does ${deltaimporter.last_index_time} know which entity
Im specifically updating? I feel like Im missing something, can it
work like that?
Thanks.
- Jon
On Sep 19, 2008, at 4:14 PM, Jon Baer wrote:
Question -
So if I issued a dataimport?command=delta-import&entity=one,two,t
Question -
So if I issued a dataimport?command=delta-import&entity=one,two,three
Would this also hit items w/o a delta-import like four,five,six, etc?
Im trying to set something up and I ended up with 28k+ documents which
seems more like a full import, so do I need to do something like delt