On Fri, Oct 3, 2008 at 9:20 PM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> > Now, my question. Let's say I have an initial set of ratings for a feed. > I then do a full import of the articles on that feed. Everything is peachy > so far. Then, I get a new rating for an existing article that I've already > indexed, thus the child entity (named "rating") > has a delta. However, when I run the delta-import, it doesn't pick up > any changes, since, I believe, the parent hasn't changed. Either that, or I > am doing something wrong. It seems like it is akin to the parentDeltaQuery > problem, but, of course, there is no parent query since there is no parent > table, in the DB sense, at least > not how I see it. The relevant logs are in [3]. > > Is this case handled? If not, Any suggestions for alternatives? Any help > would be appreciated. XPathEntityProcessor does not support delta imports. It might be possible to enhance it to accept an xpath condition for joining child to parent but it seems point-less because we'd need to parse the whole XML anyway for each changed child row (Joel Spolsky's words echo in my mind!). If the XML data is small, we can also have a cached implementation like the CachedSqlEntityProcessor. The easiest workaround here is to reverse the parent-child. Make the DB as the parent and join on the child which will let you do delta imports, however full imports may be expensive. Depending on the size of XML, you may be better off doing a full import always. Another thing I noticed from your logs: the ModifiedRowKey count is 0. Are you sure the timestamp column is getting updated? IIRC, you need a stored proc to do this for postgres. INFO: Completed ModifiedRowKey for Entity: rating rows obtained : 0 -- Regards, Shalin Shekhar Mangar.
