I'm trying to understand where `Elasticsearch for Hadoop` fits in the big data landscape and why someone would use it.
1) If you wan't all the data in Haddop searchable, doesn't that mean everything needs all the data duplicated in Elasticsearch (via `es-hadoop`)? 2) Can you push all data from Elasticsearch into Hadoop whit es-hadoop, instead of the reverse? Here's my idea: Short-term (1 week) real-time searchable (kibana) data is kept in Elasticsearch Long-term (1 year+) high-latency searchable (hbase,pig et al.) data kept in Hadoop At a high level, does this make sense? -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/73c55fe9-08ae-4c74-93be-98107aff4954%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
