search

graphaware / neo4j-to-elasticsearch

GraphAware Framework Module for Integrating Neo4j with Elasticsearch
261 stars 57 forks source link

null value in elasticsearch and sparsity issue #126

Closed Hadjerkhd closed 6 years ago

Hadjerkhd commented 6 years ago

I'm integrating a neo4j database with elasticsearch using Grapheaware.

I have one field that I'm splitting into two elasticsearch fields.

The problem is that one of those fields doesn't always contain a value, so the mapping file assigns a null value to it.

I want to know if this null values may alter the performance of indexation and search in ES, and if it may make worst the sparsity issue of ES ?

ikwattro commented 6 years ago

Hi @Hadjer13

It really depends on the type of queries you are making to ES, ending up with a lot of OR is generally not suitable for any database/search engine. I am sure that you can refactor the split to be better suited to your use case.

ikwattro commented 6 years ago

That said, as it is not an issue with our plugin, please post general questions on StackOverflow with the corresponding tags.