# External datasets in ES

**URL:** <https://discuss.elastic.co/t/external-datasets-in-es/17298>\
**Category:** Elasticsearch\
**Created:** [May 1, 2014, 1:19pm UTC](https://discuss.elastic.co/t/external-datasets-in-es/17298 "2014-05-01T13:19:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mobcdi](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@mobcdi](https://discuss.elastic.co/u/mobcdi)\
**Post date:** [May 1, 2014, 1:19pm UTC](https://discuss.elastic.co/t/external-datasets-in-es/17298/1 "2014-05-01T13:19:24Z")

</div>

From  
reading [http://www.elasticsearch.org/blog/enriching-searches-open-geo-data/](http://www.elasticsearch.org/blog/enriching-searches-open-geo-data/)  
I have a few questions I hope the community might be able to answer

The post uses an open dataset in a static csv to map German cities meeting  
certain conditions in Kibana as an example

I was wondering if its possible to take that idea and

1. Combine an static csv dataset with other ES data so sticking with the  
Cities example I would be able to live map the visitors to my german  
website from cities with populations \> 100k from the same ES cluster and  
ideally the same kibana interface
2. If it is possible how do I then update the population details when a  
newer version of the dataset is available without ending up with 2 of every  
German city with possibly conflicting population values

Any ideas?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [May 5, 2014, 11:17am UTC](https://discuss.elastic.co/t/external-datasets-in-es/17298/2 "2014-05-05T11:17:10Z")

</div>

Hey,

this would be a bit more tricky, as it requires you to merge two events  
(the external dataset and your live visitor stats) into a single event as a  
sort of preprocessing step. I think I would start with the geoip support  
from logstash and use your apache logs, which at least allows you to filter  
by city.

Need to think about this a bit more, how to merge this kind of information.

--Alex

On Thu, May 1, 2014 at 3:19 PM, [michael.obrien@ul.ie](mailto:michael.obrien@ul.ie) wrote:

> From reading  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/enriching-searches-open-geo-data/) I  
> have a few questions I hope the community might be able to answer
> 
> The post uses an open dataset in a static csv to map German cities meeting  
> certain conditions in Kibana as an example
> 
> I was wondering if its possible to take that idea and
> 
> 1. Combine an static csv dataset with other ES data so sticking with  
> the Cities example I would be able to live map the visitors to my german  
> website from cities with populations \> 100k from the same ES cluster and  
> ideally the same kibana interface
> 2. If it is possible how do I then update the population details when  
> a newer version of the dataset is available without ending up with 2 of  
> every German city with possibly conflicting population values
> 
> Any ideas?
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![mobcdi](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@mobcdi](https://discuss.elastic.co/u/mobcdi)\
**Post date:** [May 6, 2014, 9:16am UTC](https://discuss.elastic.co/t/external-datasets-in-es/17298/3 "2014-05-06T09:16:05Z")

</div>

I was wondering if you thought tribe nodes and a separate cluster for the open-geo data and another for the logstash would be a way to go ?

> **[Tribe Node
	  	 | Elastic](https://www.elastic.co/blog/tribe-node)**
>
> At Elasticsearch, we like to think different about data and how to manage it. We know that companies can innovate only if they truly understand all aspects of their business through their data. We see...

It would from my reading of the post above add a small bit more to the configuration but would allow separation of data updates or have I misunderstood the concept of tribes?  
From: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) [[mailto:elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)] On Behalf Of Alexander Reelsen  
Sent: 05 May 2014 12:17  
To: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)  
Subject: Re: External datasets in ES

Hey,

this would be a bit more tricky, as it requires you to merge two events (the external dataset and your live visitor stats) into a single event as a sort of preprocessing step. I think I would start with the geoip support from logstash and use your apache logs, which at least allows you to filter by city.

Need to think about this a bit more, how to merge this kind of information.

--Alex

On Thu, May 1, 2014 at 3:19 PM, \<michael.obrien@ul.ie[mailto:michael.obrien@ul.ie](mailto:michael.obrien@ul.ie)\> wrote:  
From reading [http://www.elasticsearch.org/blog/enriching-searches-open-geo-data/](http://www.elasticsearch.org/blog/enriching-searches-open-geo-data/) I have a few questions I hope the community might be able to answer

The post uses an open dataset in a static csv to map German cities meeting certain conditions in Kibana as an example

I was wondering if its possible to take that idea and

1. Combine an static csv dataset with other ES data so sticking with the Cities example I would be able to live map the visitors to my german website from cities with populations \> 100k from the same ES cluster and ideally the same kibana interface
2. If it is possible how do I then update the population details when a newer version of the dataset is available without ending up with 2 of every German city with possibly conflicting population values  
Any ideas?  
--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com)[mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com?utm_medium=email&utm_source=footer).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.  
To unsubscribe from this topic, visit [https://groups.google.com/d/topic/elasticsearch/8gPxfa9qENM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/8gPxfa9qENM/unsubscribe).  
To unsubscribe from this group and all its topics, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com)[mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com?utm_medium=email&utm_source=footer).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/36667CDCAAF70140AE7738BB93CA8C9606555A%40ExMbx1.ul.campus](https://groups.google.com/d/msgid/elasticsearch/36667CDCAAF70140AE7738BB93CA8C9606555A%40ExMbx1.ul.campus).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [May 9, 2014, 7:33pm UTC](https://discuss.elastic.co/t/external-datasets-in-es/17298/4 "2014-05-09T19:33:24Z")

</div>

Hey,

the tribe node (or federated search) is intended to join different clusters  
as one in order to execute operations against both. This is however only  
useful, if you do not have control over those two clusters (for example if  
they are managed by two different departments) or their data. In your case  
this does not give you a lot of advantages, at least how I understood your  
setup. Read more about it at [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/tribe-node/)

--Alex

On Tue, May 6, 2014 at 11:16 AM, Michael.OBrien [Michael.OBrien@ul.ie](mailto:Michael.OBrien@ul.ie)wrote:

> I was wondering if you thought tribe nodes and a separate cluster for  
> the open-geo data and another for the logstash would be a way to go ?
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/tribe-node/)
> 
> It would from my reading of the post above add a small bit more to the  
> configuration but would allow separation of data updates or have I  
> misunderstood the concept of tribes?
> 
> _From:_ [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) [mailto:  
> [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)] \*On Behalf Of \*Alexander Reelsen  
> _Sent:_ 05 May 2014 12:17  
> _To:_ [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)  
> _Subject:_ Re: External datasets in ES
> 
> Hey,
> 
> this would be a bit more tricky, as it requires you to merge two events  
> (the external dataset and your live visitor stats) into a single event as a  
> sort of preprocessing step. I think I would start with the geoip support  
> from logstash and use your apache logs, which at least allows you to filter  
> by city.
> 
> Need to think about this a bit more, how to merge this kind of information.
> 
> --Alex
> 
> On Thu, May 1, 2014 at 3:19 PM, [michael.obrien@ul.ie](mailto:michael.obrien@ul.ie) wrote:
> 
> From reading  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/enriching-searches-open-geo-data/) I  
> have a few questions I hope the community might be able to answer
> 
> The post uses an open dataset in a static csv to map German cities meeting  
> certain conditions in Kibana as an example
> 
> I was wondering if its possible to take that idea and
> 
> 1. Combine an static csv dataset with other ES data so sticking with  
> the Cities example I would be able to live map the visitors to my german  
> website from cities with populations \> 100k from the same ES cluster and  
> ideally the same kibana interface
> 2. If it is possible how do I then update the population details when  
> a newer version of the dataset is available without ending up with 2 of  
> every German city with possibly conflicting population values
> 
> Any ideas?
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/76a076dd-d839-4b30-bed6-f11c2577550d%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> You received this message because you are subscribed to a topic in the  
> Google Groups "elasticsearch" group.  
> To unsubscribe from this topic, visit  
> [https://groups.google.com/d/topic/elasticsearch/8gPxfa9qENM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/8gPxfa9qENM/unsubscribe).  
> To unsubscribe from this group and all its topics, send an email to  
> [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9niCM-EJ0oYUjv9siUtUB0d2EikJOvwiOAndL7ZZyLUg%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> .
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/36667CDCAAF70140AE7738BB93CA8C9606555A%40ExMbx1.ul.campus](https://groups.google.com/d/msgid/elasticsearch/36667CDCAAF70140AE7738BB93CA8C9606555A%40ExMbx1.ul.campus)[https://groups.google.com/d/msgid/elasticsearch/36667CDCAAF70140AE7738BB93CA8C9606555A%40ExMbx1.ul.campus?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/36667CDCAAF70140AE7738BB93CA8C9606555A%40ExMbx1.ul.campus?utm_medium=email&utm_source=footer)  
> .
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9nevauARi5533nLQpGbOQfb0BMBan15ufhz%3D8HJ44iOg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9nevauARi5533nLQpGbOQfb0BMBan15ufhz%3D8HJ44iOg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:30am UTC](https://discuss.elastic.co/t/external-datasets-in-es/17298/5 "2017-07-06T01:30:27Z")

</div>

Closed on July 6, 2017, 1:30am UTC


