On 15 Jul 2014, at 5:37 am, Matt Magoffin <[email protected]> wrote:
> If the "whenGathered" date was set to the epoch or null, or perhaps the > RepositoryScanner.FRESH_SCAN constant (with a value of 0), that would > indicate to my consumer that a "full" scan were being performed. But when > I do initiate the Directory Scan from the UI, the "whenGathered" is set to > the current time. Right - that was what I found as well (though it wasn't what I recalled). > >> We could probably add some more hooks into the overall process if you > wanted to propose such >> a change? >> >> Or is processing updates and deletions sufficient to maintain the > metadata, without having >> to start from scratch? > > If I could process updates and deletions, and know they were such, I could > maintain the metadata appropriately, yes. The reason I want to re-create > the metadata is for the case when something is deleted. I don't see how I > get informed of deletions in the RepositoryContentConsumer API, however. > Is there a way to get notified of them? In 1.3.x, there's a DatabaseCleanupConsumer that you can implement, which will get called when an artifact is deleted. In 2.0.x, there's a different event class that it'll need to be ported to. Which are you targeting? - Brett > > Cheers, > m@ >
