[annotator-dev] setting up with js to use annotate store

Rufus Pollock rufus.pollock at okfn.org
Fri Jun 22 14:29:41 UTC 2012

On 22 June 2012 15:25, Nick Stenning <nick at whiteink.com> wrote:
> On 2012-06-21 12:19, Ewald Zietsman wrote:
>> Actually, they do show. There seems to be a bit of time required for
>> them to show.
> This is the problem.
> So, I think I know why this is happening, and it *is* our problem.
> The problem is that objects indexed by ElasticSearch are not made
> available via the API immediately. The delay varies depending on machine
> load, but is usually less than a minute.
> Now, obviously this isn't great. There are a number of solutions
> available to us which I'm investigating:
> 1) trigger an ElasticSearch refresh after every annotation create event.

This seems easiest and simplest.

> 2) use an actual database to back the annotator store (e.g. Mongo)
> 3) use some horrible front-end caching hack to temporarily store
> recently indexed annotations until ElasticSearch reindexes. My feeling
> is that this can't possibly beat solution 2) and is unlikely to beat
> solution 1), so we probably won't do this.
> I've created an issue to track this problem:
>    https://github.com/okfn/annotator-store/issues/43

I'm big +1 on option (1) and have used it in the past.


> N
> _______________________________________________
> annotator-dev mailing list
> annotator-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/annotator-dev

Co-Founder, Open Knowledge Foundation
Promoting Open Knowledge in a Digital Age
http://www.okfn.org/ - http://blog.okfn.org/

More information about the annotator-dev mailing list