[annotator-dev] Annotator store flask
nick at whiteink.com
Wed Apr 18 16:46:22 BST 2012
How quickly are you starting and quitting ElasticSearch? There shouldn't be
anything special needed to get ES to serialise to disk, but given it
flushes to the index asynchronously I suspect you might be able to cause
loss of data if you kill it fast enough and sufficiently aggressively
(SIGKILL or similar).
If you're still seeing this, it sounds like ES is misconfigured -- perhaps
it doesn't have appropriate permissions on its data directory?
On 11 Apr 2012, at 12:26, johnny jiang <johnny.nan.jiang at gmail.com> wrote:
Thanks Nick, that is fair enough.
Actually I tried annotator-store first, and got it up and running. I
noticed that I lost all my annotations after I shut down the store and
ElasticSearch. Is there a way to get the store permanent?
On Wed, Apr 11, 2012 at 6:53 PM, Nick Stenning <nick at whiteink.com> wrote:
> Hi Johnny,
> That's the backend that later turned into
> I have no plans to bring it up to date, and I can't really provide
> support for it, either. Sorry!
> Do note that it has no support for authentication or authorisation of any
> On Tue, Apr 10, 2012 at 22:35, johnny jiang <johnny.nan.jiang at gmail.com>
> > Hi Nick,
> > I'm looking through all the annotator backends, and found this one really
> > simple and easy to use.
> > https://github.com/nickstenning/annotator-store-flask/
> > However it seems to be a bit old, as I got Content-Type is not allowed in
> > the header when submitting annotations to it. Is there a plan to bring
> it up
> > to date? Or could you give me some hints so that I can implement it
> > Thanks
> > Kind regards,
> > Johnny
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the annotator-dev