Michael Hunger
Michael Hunger
I had it here: http://graphgist.neo4j.com/#!/gists/26406a0e4c8e924958c2ebeea6f36455/summary (via this: http://graphgist.neo4j.com/#!/gists/manage/26406a0e4c8e924958c2ebeea6f36455) and here http://graphgist.neo4j.com/#!/gists/eab6dca75f701444987d709f4b0217e1/summary
Which required fields do we not need? I was just speaking about the UI, not the endpoint creating stuff. Actually one could separate that out into nice, separate queries. That...
On neo4j.org it was no issue, we can also easily compute how much the pure text of asciidoc gists costs in memory but I don't think it is a problem.
- see neo4j.org's rendering, which does a server-side rendering with asciidoctor.js Current implementation, which should be fixed - load metainfo/item from database - load graphgist content from api endpoint (server-side,...
aka "page-source" button
There are some old things left, like in the header (pointing to the old repository)
Yes, neo4j doesn't write properties that haven't changed. We could add some means (e.g. a procedure to actually trigger initial indexing).
btw. updating all 13M entries at once might also overload the plugin. Can you try to update e.g. a subset of 100k, let's say with a timestamp?
Is your ES running on localhost? if you look at this it doesn't seem to find it: ``` INFO - 2018-12-21 13:57:16.501; io.searchbox.client.AbstractJestClient; Setting server pool to a list of...