Open apowers313 opened 6 years ago
I have the same issue with 3.1
I actually had to modify the data for elasticsearch to be populated. a SET a.b=a.b
query is not enough for elasticsearch to be notified.
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?
Are there any updates on this ? Unchanged existing data isn't sent to elasticsearch
@jexp would it overload that many records if one were to use apoc.periodic.commit
with smaller batch sizes (since it's executeAsync
anyway)?
Hi @jexp, is there any update on whether a procedure will be implemented to trigger initial indexing? The problem still seems to be happening.
Assuming #42 isn't the source of my problems, I'm not seeing any data being written to elasticsearch and I don't get any errors that would indicate why.
I have 6538642 nodes of type BibliographicResource which look like:
And my configuration looks like:
I can see that the plugin loads in the log file:
I attempt to populate the data:
But the elasticsearch index is never created / no data is populated in elasticsearch:
There aren't any errors in neo4j's debug.log or elasticsearch's elasticsearch.log. Any ideas of how to fix and / or debug this problem?