Linkurious allow you to search your graph using natural full-text search.
In order to offer the search feature out-of-the-box, Linkurious ships with an embedded Elasticsearch server. The option allow for zero-configuration deployment in many cases.
By default, Linkurious uses Elasticsearch for search. This options requires Linkurious to index your graph database, which technically means that Linkurious will feed the whole content of the graph database to Elasticsearch to make it searchable. The time required to index the graph database increases with the size of the graph and this solution has limits in its scalability.
Indexation typically happens at speeds between 2000 and 20000 nodes or edges per second, depending on the number of properties for nodes and edges, and hardware performances.
By default, Linkurious ships with an embedded Elasticsearch server (version 1.4.5).
This server only listens for local connections on a non-default port (it binds to
for security reasons and to avoid collisions with existing servers.
It is possible to use your own Elasticsearch cluster for performances reasons. Linkurious supports Elasticsearch v1.x as well as v2.x. See details about Elasticsearch configuration options.
Using Elasticsearch is convenient but may not fit cases where the graph database is big (more a a couple million nodes and edges) and is regularly modified from outside Linkurious, which required to re-index the whole database.
In order to offer a scalable search feature on big graphs, Linkurious offers alternatives search solution:
- With Neo4j: using the neo4j-to-elasticsearch Neo4j plugin to synchronize Neo4j and Elasticsearch incrementally
- With DataStax Enterprise Graph: using Linkurious' DSE Search connector to use DSE's built-in full-text search capability
- With AllegroGraph: using Linkurious' AllegroGraph Search connector to use AllegroGraph built-in full-text search capability
index configuration can be changed from the administration interface.
Using an administrator account, access the Admin > Data menu to edit the current data-source configuration:
Edit the data-source index configuration:
Submit the changes by hitting the Save configuration button
Edit the configuration file located at
See details for each supported search connector: